Re: System abusers

[Buck Calabro/commsoft<mcalabro@xxxxxxxxxxxx>]

On 02/24/99 04:33:03 PM Roger Boucher  wrote:

>Is there a good way to find out (on the fly) which user/process is
>hogging up CPU?  I use WRKACTJOB and the screen takes so long to pull up
>that most of the time whatever was taking up the resources is no longer
>doing so.  Any suggestions?  Thank you very much for any help.

If the process is happening so quickly that you can't catch it that way, 
you probably need performance tools (or whatever it's called nowadays)  If 
you use WRKACTJOB CPUPCTLMT(5) you can shorten the time it takes to find 
the hog bye one display's worth of delay time. 

As a rule, you should have your shop avoid doing ANY interactive work that 
doesn't require an interactive display panel.  Programmers and power users 
very often do things like queries or compiles interactively because they 
hate waiting for their turn in the JOBQ.  Large CPYF's, RSTLIB/RSTOBJ that 
cause index rebuilds, program compiles and queries should all be submitted 
to batch.

Buck Calabro
CommSoft, Albany, NY
mailto:mcalabro@commsoft.net
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@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
+---