On Mon, 15 Jan 1996, <Elbert E Silbaugh> wrote:
> Here is my typical list of jobs that run all day long. None of which
> I have access to the original job file without hunting around and
> without tweeking everytime I get a new FOS or 3rd party tape.
> All of these jobs are launched by MANAGER.SYS.
>
> JOBNUM  STATE IPRI JIN  JLIST    INTRODUCED  JOB NAME
>
> #J5     EXEC        10S LP       TUE  7:56P  CALLBACK,MGR.JMS3000
> #J1132  EXEC        10S LP       SAT  5:31A  JMS,MGR.JMS3000
> #J1138  EXEC        10S LP       SAT  5:33A  HPDARPA,MANAGER.SYS
> #J1139  EXEC QUIET  10S LP       SAT  5:33A  IDLEXL01,MANAGER.SYS
> #J1140  EXEC        10S LP       SAT  5:35A  FTPMON,FTP.SYS
> #J1142  EXEC        10S LP       SAT  5:36A  SCOPEJOB,MANAGER.SYS
> #J1145  EXEC        10S LP       SAT  5:40A  NBSPOOL,MANAGER.SYS
> #J1146  EXEC        10S LP       SAT  5:40A  VISTAPLS,MANAGER.SYS
> #J1169  EXEC        10S LP       SAT 10:02A  SUPRVISR,MGR.HPOFFICE
> #J1171  EXEC        10S LP       SAT 10:07A  MTRUCK0,MAILTRCK.HPOFFICE
>
> So, in reviewing this thread...how would I implement the new multi-job Q
> feature the easiest way? It looks like I would have to:
>
> :ALTUSER MANAGER.SYS;QUEUE=$BACKGROUND
> :ALTACCT @.HPOFFICE;QUEUE=$BACKGROUND
 
This is exactly why I have requested the JSNAME and LOGON_GROUP to be
part of the queue definition.  In this case, all you need to do is
 
   :ALTJQ $BACKGROUND;MEMBERS="CALLBACK,MGR.JMS3000+..."
 
That brings up the question of what a reasonable number of elements
is for the member parm.
 
Regards,
 
--- John Joerger  ([log in to unmask])  ---  Press-Telegram (Long Beach)