Re: my system is sluggish and I don't why?

are you sure it's the 400 thats slow, and not a network problem after the
power failure. if you have a know batch job and how long it takes to
process it, try job again and see if any real difference from before power
problem. This could be congested hubs & switches.
On as400, check system service tools (strsst) and Product Activity Log
and Analyze Log (all logs) and look for unusual problems.
jim

----- Original Message -----
From: "DeLong, Eric" <EDeLong@Sallybeauty.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, April 02, 2002 6:06 PM
Subject: RE: my system is sluggish and I don't why?


> What about devices being recovered by OS400.  We had a AS400 (cisc) slow
to
> a crawl for most of a day while os400 was trying to recover all the failed
> twinax devices.  The 400 was protected by UPS, the terminals were not.
> Regardless, we still got screwed.
>
> Did you look to see if SMAPP was rebuilding indices?  Check EDTRCYAP to
see
> if the system is rebuilding indices.
>
> Eric DeLong
> Sally Beauty Company
> MIS-Sr. Programmer/Analyst
> 940-898-7863 or ext. 1863
>
>
>
> -----Original Message-----
> From: Andy Nolen-Parkhouse [mailto:aparkhouse@attbi.com]
> Sent: Tuesday, April 02, 2002 11:41 AM
> To: midrange-l@midrange.com
> Subject: RE: my system is sluggish and I don't why?
>
>
> > wrkdsksts shows no 1 disk unit greater than 10%. is 35% a cumulative
> > number?
> > I do not see anything in wrksysact abnormal...what would show there?
> high
> > cpu util? page fault? Even if the machine automatically ipl'ed (how
> can I
> > tell?), would that cause this problem? Is temp address % of .051 too
> high?
> > Yikes!!!!!!!!!!!
>
> Rick,
>
> Having each disk below 10% is good, that's not your problem then.
>
> You've said that you have a performance problem.  I assume by 'sluggish'
> that you mean interactive response times are higher than normal and
> batch jobs take longer to run.  Is this the case?
>
> The most common cause of an overall sluggish system is that some job or
> task is consuming CPU resources, thus making them unavailable to other
> jobs.  This would show up most obviously in the WRKSYSACT display.  If
> you are showing no jobs with very high CPU utilization and your overall
> utilization is less then 100%, then you'll need to look elsewhere.
>
> Usually the three systemic resources that affect overall performance are
> CPU utilization at 99+ percent, disk activity around 40%, or heavy
> swapping/paging in your memory pools (thrashing).  From what you have
> described, you have eliminated all three.  Double-check your readings
> for these three factors and make sure that you have a realist sample
> interval.  Use F10 to reset your counters and then wait 15 seconds and
> use F5.
>
> Temp addresses used of .051 is fine.
>
> You would find out if you IPLed by checking your history for the time in
> question.  Prompt the DSPLOG command, fill in the relevant dates and
> times, and then look through the entries for relevant information.  It
> is possible that your machine had been tuned by hand and that an IPL set
> it back to its defaults.
>
> Can you define 'sluggish' with a little more precision?
>
> Regards,
> Andy Nolen-Parkhouse
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>