Greg,

In our site I've implemented 'multiple queues' almost as soon as they were
introduced.  One needs to keep in mind that the 'non-system' queues do not
survive 'reboots' and must be recreated.  In sysgen I've left the settings
for sessions and jobs to 100 and 60 respectively and have relied on the
'limit' command to control the job activity.  The following commands are
executed every morning:

#
setvar SYS_SysJobs_limit  8
setvar SYS_JobQue_limit   ![SYS_SysJobs_limit + 8]
setvar ARS_JobQue_limit   2
setvar ARS_ExecJob_limit  1
#
LIMIT !SYS_JobQue_limit,![HpUserLimit-1]
LIMIT !SYS_JobQue_limit;jobq=HpSysJq
continue
newjobq arsjobq;limit=!ARS_JobQue_limit
#
LIMIT ![HpJobLimit + ARS_ExecJob_limit]
#
deletevar @_limit > $null

The above allows for 8 system jobs (Jinetd, Sendmail, Sleeper...) and 8
non system jobs that can be submitted by the users to run in the system
queue.  It also creates a queue for the ARS account that can have a
maximum of 2 jobs running concurrently IF the other 8 slots are not
already taken, if they are then the ARS queue will only be able to execute
1 job.

Regards
Paul Christidis

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *