Performance Monitoring

[Leo Lefebvre <leo@xxxxxxxxx>]

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!

TIA.

--

Leo Lefebvre
leo@tug.on.ca
Toronto Users Group for Midrange Systems
Ph: (416) 606-5960   ---   Fx: (416) 495-0100

begin:          vcard
fn:             Leo Lefebvre
n:              Lefebvre;Leo
org:            MBL 3 Software Services
adr:            20 Bead Fernway;;;North York;ON;M2J 4L3;Canada
email;internet: leo@tug.on.ca
title:          President
tel;work:       (416) 606-5960
tel;fax:        (416) 495-0100
x-mozilla-cpt:  ;0
x-mozilla-html: FALSE
version:        2.1
end:            vcard