Steve wrote;
 
[....SNIP....]
>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 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.
 
Will do a quick "second this motion".  Right now on our
system we should always see:
 
NP92JOB,BATCH.MINISOFT
INPFIG,MGR.MK50
DOCIPC,REPORTS.MK50
INVIPC,MGR.MK50
UPDHOT,REPORTS.MK50
SKEDLR,REPORTS.MK50
PCJOB,REPORTS.MK50
FTPMON,FTP.SYS
 
If all of these jobs are not running all the time in production,
something went wrong (we use all the  .MK50
jobs to do "semi-online", slightly delayed processing,
for a lot of the stuff that doesn't need to be done instantly,
thereby improving user response time).
 
A  QUEUE=$BACKGROUND  sounds like a real good idea.
....  or how about just   QUEUE=$BACK   or etc.....  Shades of
MPEXL_SYSTEM_VOLUME_SET .........
 
Ken Sletten