RE: WRKACTJOB

[rob@xxxxxxxxx]

And I've seen people get burnt by using WRKACTJOB (and forgetting to use 
F14).  When WRKSBSJOB told them the job was still running and the previous 
case did not.  And that was just a regular 5250 job.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





Jim Damato <jdamato@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/26/2003 03:48 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "'Midrange Systems Technical Discussion'" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        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>
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.