|
>>> "Jeffrey M. Carey" wrote>>> I have heard that WRKACTJOB does continue to run in the background <<Snip>> Do a WRKACTJOB, F3, wait a few minutes and do another WRKACTJOB. The "Elapsed time" will show the total time since the first WRKACTJOB - so something must be collecting information during that time. -------------- This is not necessarily indicative of continuous information gathering - the process could just go to sleep (e.g. do nothing, use 0 CPU cycles, etc.) until you press F5. The process knows when it started and what the current time is - coming up with an elapsed time is a simple calculation. In point of fact, I know I've seen several posts on this thread that indicate that's exactly what happens. 'Course, each time you do press F5 it does resample the entire system, which does take CPU - but nothing is necessarily happening between screen refreshes Scott Cornell Mercy Information Systems +--- | 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 MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | 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.