On Fri, 12 Jan 1996, Mohan Das wrote:
 
> Hi,
>
> Judging from the responses so far, it is obvious that customer  interest in
> this feature is considerable.  We are really glad to note that.
>
...
>    The heirarchy will be:
>
>    1. ;JOBQ= specified in :STREAM command, if any
>    2. else ;JOBQ= specified in !JOB command, if any
>    3. else a default job Q based on some membership criteria, if any specified
There are some famous resource-consuming programs. If the command
interpreter finds the 'RUN CPUEATER' then the right place of the job is
the SLOWQ.
>    1. Default job queue based on user.acct
>
>       Not sure whether it should be user.acct specified in !JOB or
>       that of the user who :STREAMed the job.
>
>    2. Some respondents  feel they need more  granularity in determining the
>       default  queue and they are of the opinion that it should be based on
>       "jobname,user.acct,group".
>
>    While option 1 can be achieved by adding a new parameter ;QUEUE= to
>    :NEWUSER and :ALTUSER commands, if we choose option 2, we need to
>    either have a file to decide membership or it should be part of
>    commands which create and alter job queues. Like,
>
>        :NEWJOBQ queuename;members="payroll,mohan.admin",@.sys
>        :ALTJOBQ usersq;members=+newbie.users,-oldie.users
>        etc.
I do not think that detailed 'members=' subparameter is nececcary. I
prefer distrintion of queues on user capabilities, e. g.
"NEWJOBQ MAINT ;cap=SM,OP",
"NEWJOBQ DONKEY;CAP=IA".
>
> 3. Some people have asked for  properties  like jobfence and input priority
>    (default and  maximum) to be different  for each queue  instead of being
>    same across all the queues.
The above "CAP=SM" should imply a high default priority or a "DEFPRI="
parameter should specify it.
>
> 4. Should  there be any  relative  priority  across  the queues in terms of
>    selcting the next job to run ?  Consider this scenario:
>
>    JOBFENCE=8, JLIMIT=10; 10 EXEC; 2 WAIT
>
>    JOBQ1: LIMIT = 5, 1 WAIT (#J11, INPRI=12)
>    JOBQ2: LIMIT = 3, 1 WAIT (#J12, INPRI=13)
Take care to avoid queues of never executed jobs.
>
>    :ALTJOB #J12;QUEUE=JOBQ1
>
>    Some of you have mentioned it, but I just want to know if it is
>    really essential.
Better than abort and re-stream.
                                         Best regards
                                              Frank
 
  |\  /~ ~~|~~~ Family : NAGY; first name : FERENC; title : Ph. D.
  | \ |   -+-   Institute of Isotopes of the Hungarian Academy of Sciences
  |  \|    |    1121 BUDAPEST Konkoly-Thege M. ut 29, HUNGARY (1525 Bp. POB 77)
`-'   '  `-'    E-mails : [log in to unmask]; [log in to unmask]
 
Fax: (36)-1-156-5045, work phone: (36)-1-275-4351, home phone: (36)-1-277-4229.
Home address: H-1214 BUDAPEST Raketa u. 29. I. 3.
 
There are 3 kinds of programming errors:  syntactical, semantical and mystical.
The programmers have to suck up the users just as much as absolutely necessary.