At 10:18 PM 12/9/97 -0500, you wrote:
>Hi everybody,
>I was thinking: when we have a performance problem on the AS/400 for a
>certain period of time, one way to see what is going on is to start the
>Performance Monitor program. Running the results through some other
>programs, we will, 'maybe', see where the problems are.This is not a
>foolproof method since the problems may (and will, most of the time)
>come up 'in between' the sample periods (the minimum length of a period
>is 5 minutes).  Our chances to really figure out where the problem(s)
>is(are) are minimal.
>Has anybody seen a program that would basically 'wake up' ONLY when the
>situation is critical (ie the system is bugged down) and gather
>information to save for later evaluation. If the system never gets into
>trouble, no data is recorded. If the system is constantly bugged down, a
>lot of data is collected.  Today, when we think we have a problem, we do
>a 'WRKACTJOB' (if we can get a terminal that has a reasonable response
>time and if we are on location at the time of the problem).
>Think about it.
>Maybe I gave some ideas to some people!

If you have Performance Tools installed, you can run WRKSYSACT with output
to an outfile. This can be evoked with various sampling intervals. But it
isn't something that wakes up when there's a problem.

The 3rd-party tool, AutoTune, can be configured to gather statistics while
it runs. It is typically set up to monitor and possibly change pool
settings every 5-10 seconds, and that's the sampling interval, too. Since
it's running all the time, anyway, this might be a solution.

OTOH, you could create a never-ending-program that wakes up every so many
seconds (use DLYJOB in a loop). It would use a Work Management API to
ascertain the CPU% and, if beyond some threshold, would start Performance
Monitor or WRKSYSACT.


Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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 [javascript protected email address].