Re: WRKACTJOB?

>Hi all,
>Someone told me that using WRKACTJOB is a system killer; I agree that
>this is true as it is a pretty intensive information-gathering command.
>However, this person went on to say that once you do WRKACTJOB from your
>session that it remains "invisibly active" and continues to drain
>resources, and will only be stopped when you sign off your session.  Is
>this possibly true?
>--
>''''''''''''''''''''
>' Tim & Dana Truax '
>....................


I don't know what the overhead is, but if you use WRKACTJOB now, then check
on it 4 hours from now, the elapsed time at the top of the screen shows
4:00:00.  It's been doing something all that time.

For us, the biggest problem is having the machine go into one of those
'unexplained mid-afternoon slowdowns,' and having 6 or 7 programmers, 1
operator, 1 operations manager, 2 technical support gurus and the data
processing manager all bring up WRKACTJOB to see what's slowing things
down.

--Paul E Musselman
PaulMmn@ix.netcom.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
+---