RE: Filled up the DASD! Now can't run a specific query...

I was able to do a RGZPFM on the problem file, which rebuilds the indexes. That corrected this problem, query works once again.

Thanks
Bob

-----Original Message-----
From: Eric Lehti
Sent: Saturday, September 12, 2015 1:40 PM

Suggestion: copy both tables to a backup. Delete both tables and their logicals. Create both tables and logicals. Repopulate both table from the backups. Delete backups. Run World Writer. If still not fixed, create new World Writer from scratch. EricL



On Sep 10, 2015, at 14:13, Bob Cagle <bcagle@xxxxxxxxxxx> wrote:

So I set Fix Central to download the latest CUME, Group, and TR PTFs directly to my system and left it to run for the evening, just to have it fill our remaining disk and crash the system.

I've since recovered from that fiasco and gotten the system back up and the utilization back down around 78% - it's a small 520, only 175gb total available. Will need to figure out how to get those PTFs loaded eventually.

After getting back to normal operations this morning, we discovered a specific report that just won't run. This is a JD Edwards World Writer - for those that don't know, it's very similar to Query, just specific to the JDE environment.

This report does a join on two specific PFs - simple report: join the files, then print the records where the price in one doesn't match the other. It's been running multiple times a day, every day, for years.

But now after the DASD issue, the job runs, but isn't doing anything I can see. It shows as active on WRKACTJOB, but no activity in the file I/O, call stack, or job log - it just sits there with no movement.

I thought I had it tracked down to a damaged join LF. I wasn't able to pull up this LF using DBU - just got a continual loading message, but could pull up each of its base PFs. So I recreated the join LF. No change.

Just now I've tried recreating this report with SQL in the iSeries Navigator Run SQL Scripts. Same thing - it's just sitting and spinning. Again, this isn't a fancy report and should only take a couple of minutes to run on our system with the data we have.

Any ideas on what's going on here? Is there an index that's been damaged/needs rebuilt?

I should note that as part of recovering space yesterday, I did a RCLSTG and an IPL. Now not sure if that was a help or a hindrance.

Thanks for any input,

Bob Cagle
IT Manager
Lynk