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.
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact