Re: WRKACTJOB?

["David Nettles" <dnettl@xxxxxxx>]

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

ah maybe as in 15:27:15 to 15:27:35 is 20 seconds? what's collecting about
that?
well maybe a data area or file somewhere in QSOMETHINGOROTHER

do a wrkactjob on one screen then start another on a different workstation
.. is the 
first workstation using any resources? do an F5 and watch the processor
zoom.. there's your resources.... 

why sweat the simple stuff?  
+---
| 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
+---