RE: WRKACTJOB?

[Robert Dobrowolski <RDobrowolski@xxxxxxx>]

The elapsed time could just be a calculation of the time between the
current time and a stored value (in QTEMP?) of the last time the
WRKACTJOB values were retrieved for this session.  I always thought that
WRKACTJOB only had an effect on the system while the values were being
refreshed or reset.  During this time, it is a BIG user of resources,
but otherwise is dormant, much like any other interactive job.

JMHO, Bob Dobrowolski

>----------
>From:  Jeffrey M. Carey[SMTP:jeffreycarey@usa.net]
>Sent:  Friday, September 26, 1997 12:25 PM
>To:    MIDRANGE-L@midrange.com
>Subject:       Re: WRKACTJOB?
>
>I have heard that WRKACTJOB does continue to run in the background as
>long as the job that called it is active - even if you exit the
>command.  The best evidence for this is the "Elapsed time" field.  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 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
>+---
>
+---
| 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
+---