|
Thanks to everyone who responded. Both the WRKSYSACT and the CPUPCTLMT parameter on the WRKACTJOB screen are proving helpful. I caught a program just now that I didn't know was so CPU intensive. Thanks again. >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. Roger Boucher Standard Pacific Corp. rboucher@stanpac.com 714-668-4326 +--- | 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 mailing list archive is Copyright 1997-2025 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.