Hi Mohan, Jeff...
 
(I'm coming in late on this, sorry)
 
Has anyone mentioned Workgroups yet?
 
I'd suggest that we don't need yet another wildcard/membership/etc set
of rules, in addition to the Workgroup Manager's.
 
How about:
 
   1) promoting Workgroups to queues:
 
      1.1) implies ability to specify a LIMIT on the number of jobs/sessions
           currently active for a given Workgroup.
 
      1.2) may want to add a workgroup option like "can only be specified
           by user request at job/session STREAM/logon time",
           and/or "cannot be manually requested" (so you can have a workgroup
           that isn't associated with QUEUING, but only processor usage
           control)
 
   2) or, if we get new classes/queues anyway, there probably should be
      a default workgroup specification for each class/queue.  Indeed, you
     might want to have a forced workgroup as well as a default workgroup.
 
In short, I'd suggest being inspired by the Workgroup command names, semantics,
philosophy, etc., whereever possible.
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html