RE: WRKACTJOB

> Ken Graaap:
>Can any of you provide reasons why it 
>might be a good idea to restrict the
>use of the WRKACTJOB command to Sys 
>Admin and Operator users?

>I'm trying to convince our large team 
>of programmers that WRKUSRJOB is a
>better command to use...

You'll never convince them.  WRKACTJOB is so much cooler than WRKUSRJOB.
I'm not sure if the system resources demanded by WRKACTJOB are, by
themselves, significant.  The system abuse generated by WRKACTJOB becomes
significant because programmers will look at things they don't need to see.
I've watched programmers hit F5 or F10 dozens of times, or set up dedicated
sessions on auto-refresh, or sort by CPU repeatedly.

Back in the good old days of slow, single CPU System/38's we'd have lockups
from ten programmers racing to DSPACTJOB to find the culprit any time anyone
asked, "Is the system slow?"

Consensus is gonna be tough.  I'd go with guilty until proven innocent.
Take away WRKACTJOB.  Tell everyone to use WRKSBSJOB and WRKUSRJOB until
they can prove they need WRKACTJOB for productivity.  I've seen programmers
who become less productive because they're tooling around on WRKACTJOB
unnecessarily.

(Gee, what a cranky old man I've become).

-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@xxxxxxxxxxxxxxxxx>