On Mon, 15 Jan 1996, Dr. Ferenc Nagy wrote:
> >    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".
 
Hmmm, yet another interesting application.  Most of the thoughts
expressed so far have implied that users have the SAME capability.
 
I respectfully disagree with the comment about the "member" parm.  It
may be of little value to the above queue setup, but it is the ONLY
way queue membership can be defined without a config file.
 
Job queues become more useful as our ability to define the queues
increases.  To that end, multi member lists with additive and
subtractive ( +/- ) capability is desirable.
 
Regards,
 
--- John Joerger  ([log in to unmask])  ---  Press-Telegram (Long Beach)