Steve Cooper ([log in to unmask]) wrote:
: Part of me would prefer NOT to have these jobs count in my overall job
: count.  In other words, if I want to allow 3 concurrent real batch
: jobs, I must first check to see how many background daemons are
: running, then add 3 to it, and set the job limit to that value.  If I
: could define a QUEUE=DAEMON or use a built-in QUEUE=$BACKGROUND that
: did not count against my overall joblimit, this could be useful.
 
I think Steve makes a good case (as someone said ealier, as well) that
the LIMIT command should NOT set a limit on the total number of jobs
allowed on the system.  That is, "LIMIT 20" would set the LIMIT for the
default system job queue rather than set a limit of 20 on all job queues
combined.  For a user that doesn't use mulitple job queues, this is
backwards compatible.  For a user that wants multiple job queues, it
relieves them of the burden of always having to tinker with a global
limit as they adjust the other queues.
 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Mike Paivinen
[log in to unmask]
 
Hewlett-Packard
CSY - Mailstop 47UP
19447 Pruneridge Avenue
Cupertino, CA   95014