Re: WRKACTJOB leaving part of itself running?

> I'd like to prove or disprove a persistent "AS/400 legend":
>
> If you WRKACTJOB, then exit the function but remain signed
> on, are any system resources used? Is there any part of
> WRKACTJOB
> that remains running even though you are no longer in the
> command?

if you wrkactjob, and then key something else from the bottom, (without ending 
it
first), it's still in your stack, and taking up resources.  in the early days,
this was a preached no-no.

i suspect that's where the rumor came from.

nj

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