In all of this great discussion on Multiple Job Queues, I have not
seen specific reference to one special type of job.  It may be obvious
and it may not have any special requirements, but I thought I'd
mention it, just for the sake of completeness.
 
Every system seems to have some number of jobs that are supposed to be
running ALL of the time.  These are equivalent to what UNIX might call
"daemons".  For example, ARPA services contain an FTP job that must be
runnning for the machine to respond as an FTP server.  Many spooler
products also have them.  If your machine is a WWW server, you have
another job, unless you use Stan's thing to turn it into a true
(hidden) background process.
 
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.
 
/Steve