Re: RUNPTY

Kenneth,

It is true that certain jobs are more important than others, but it
certainly can't be a user that decides that his jobs would be more important
than anything else on the machine (give such a guy priority 90).

It's the system manager  that, with input from the users, and in discussion
and agreement with them, sets on a priority logic, that can be approved by
the different services in the entrerprise (and that can be modified after
general consensus).

Create different classes with different priority  (say BATCH40, BATCH60,
aside of the default at pty 50).
Add Routingentries in your batch subsystem for these additional classes
(again Batch40, Batch60).
You can create more classes, playing with runpty, purge, timeslice...

That routingdata can than be used in a sbmjob, or at Jobd level.

Important jobs can be launched with routingdata BATCH40, low priority jobs
use BATCH60.
Normal jobs won't change.
A normal user may not have jobctl accesses.

Regards
Luc

-----Oorspronkelijk bericht-----
Van: DAsmussen@aol.com <DAsmussen@aol.com>
Aan: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Datum: zaterdag 24 oktober 1998 22:34
Onderwerp: Re: RUNPTY


>Kenneth,
>
>In a message dated 98-10-23 13:06:50 EDT, you write:
>
><<snip>>
>> I've always believed that raising the priority of one job in the
>>  pool/subsystem is poor system management....
>>
>>  Would anyone care to comment on this?
>>
>>  I want to discuss this practice with our users, but if lowering RUNPTY's
>>  isn't a big deal then I won't pursue it..
>
>It is _VERY_ poor systems' management.

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