× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: System abusers
  • From: pytel@xxxxxxxxxx
  • Date: Thu, 25 Feb 1999 15:14:03 -0600

WRKSYSACT shows CPU users (tasks and job threads), which actually used CPU
from previous refresh.
>From the screen you may see some statistics for a task/job - CPU used, I/O
operations (sync and async).
>From this screen you may WRKJOB on a selected job thread.
Basic differences from WRKACTJOB - shows both tasks and job threads, shows
only those jobs, which used CPU since last refresh (therefor works much
faster).
This command is part of Performance Tools LPP (5769-PT1), which costs $$$.

Best regards
    Alexey Pytel



"Kevin Watkins" <kevinw@hurtcompanies.com> on 02/25/99 09:38:34 AM

Please respond to MIDRANGE-L@midrange.com

To:   MIDRANGE-L@midrange.com
cc:    (bcc: Alexei Pytel/Rochester/IBM)
Subject:  Re: System abusers





OK -- what does it do and how do i get it?


-----Original Message-----
From: pytel@us.ibm.com <pytel@us.ibm.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Wednesday, February 24, 1999 7:02 PM
Subject: Re: System abusers


>Handy tool is WRKSYSACT, but it is part of Performance Tools LPP...
>
>Best regards
>    Alexey Pytel
>
>
>
>Roger Boucher <RBoucher@stanpac.com> on 02/24/99 03:33:03 PM
>
>Please respond to MIDRANGE-L@midrange.com
>
>To:   "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
>cc:    (bcc: Alexei Pytel/Rochester/IBM)
>Subject:  System abusers
>
>
>
>
>
>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.
>+---
>| 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
>+---
>
>
>
>+---
>| 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
>+---

+---
| 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
+---



+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.