truax @ usaor.net wrote on 09/232/97 at 03:38:22 pm


>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?
---------------------------------------------------------------------------
----------------------------------------------------------------------
          You have to explore all of the parameters of the WRKACTJOB
Command.                           the same applies to the WRKSYSSTS and
WRKDSKSTS .                                        Say you have 700 jobs in
your AS/400 Interactive, Batch, Communications, DDM, Pashthru, TCP/IP,
Printers, Fax Save/Restore Jobs, and there is a couple of SQL jobs running,
(OPNQRYF ..) Querys and the creation of Logical Files in batch mode over
files that have 15 million records.  and,,,, your in-house developers run
the WRKACTJOB at the same time ... Well you better start thinking how to
run / secure / these commands. There are some basic guidelines. Ask your
software developers to   run the command against a subset of the system
(Subsystem/.. etc) . If possible run the command in batch mode to *PRINT,
if you run these commands look into the RESET(*YES/*NO) options. Signoff
your session(s) once or twice a day (Good set of practices) Make life for
everyone easier. If you know that you have a runnaway job that is chewing
up CPU Utilization, well have a Never Ending Program monitoring  for this .
And I am going to stop here because if Chuck Yagger  from IBM reads this He
may want to start telling you how expensive this commands are. ..  Ah the
answer is YES !  .. Bye and Good Luck.


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


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].