Re: Poor Performance after Abnormal System End

[Al Mac <macwheel99@xxxxxxxxxxx>]

Usual suspects (for me) first places to look

DSPSYSSTS ... do you have some huge joblogs eating up disk space?  You 
better have no more than 75% or so of your disk space eaten, because the 
"unused" 25% or whatever is "used" as a work area when manipulating that 
which is "used"

WRKPRB
DSPMSG QSYSMSG (assuming you have created that message queue)

DSPJOBTBL ... do you have inadequate work areas for jobs on the system?

WRKDSKSTS ... in fact GO STATUS and GO CMSSTS and GO CMDSYS & review 
several status areas for reasonable values

WRKSYSVAL F4 to *PRINT ... it shows which are other than what came from 
IBM, to help accelerate what to review ... all of them are explained in the 
WORK MANAGEMENT manual, or in a PDF file that Al Barsa offered people a 
while back from his presentation at COMMON

Has GO CLEANUP run since your crisis?

Are the JOBQ tasks getting to an Ok conclusion?  Sometimes when something 
was running when the system went down, it can mess up the ability of that 
same task to run next time, depending on application software.

Have you resolved whatever was the UPS problem so it not gonna happen again?

> Has anyone encountered poor system performance after an iSeries has come
> down abnormally?  We lost power this weekend and the UPS didn't hold up.
> After IPL'ing and running a RCLSTG I am still experiencing significantly
> long run times on my batch jobs.  I have not gotten any report of errors
> from the system that it has an issue.
>
>
>
> Thanks,
> Patricia Reeves
> Senior Analyst/Programmer
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.