Re: subsystem.

[rob@xxxxxxxxx]

Let me pretty this up.
8           QTEST     QGPL       1
10          QBATCH    QGPL       1
20          QSXVKOVE  QGPL  *NOMAX
30          KIW       QGPL       1

So if you do this
SBMJOB CMD(DLYJOB DLY(600)) JOB(DLYJOB) JOBQ(QBATCH)
and then you immediately do this
SBMJOB CMD(DSPJOB OUTPUT(*PRINT)) JOB(printout) JOBQ(QBATCH)
and you do WRKACTJOB SBS(QBATCH) you'll only see DLYJOB running.  PRINTOUT 
will only be shown with WRKJOBQ QBATCH.
Then,
- if you need job PRINTOUT right away, and
- it doesn't need to wait on DLYJOB to finish first,
then instead of 
SBMJOB CMD(DSPJOB OUTPUT(*PRINT)) JOB(printout) JOBQ(QBATCH)
I would use
SBMJOB CMD(DSPJOB OUTPUT(*PRINT)) JOB(printout) JOBQ(QSXVKOVE)
and that would put it in the job queue QSXVKOVE.  Which, since this 
subsystem says that job queue is *NOMAX, go ahead and run it right away.

A job queue with 1 at a time capability is great for jobs that have to run 
in a certain order.  For example if I submitted four jobs:
BUILDFILE
LOADFILE
PROCESSFILE
DELETEFILE
they may have to run in just that order so I would submit them to job 
queue (not subsystem) qbatch.  But if they were not dependent on each 
other then I may submit them to job queue QSXVKOVE.
Therefore I would NOT go changing job queue qbatch to allow more than one 
job to run at a time.  Otherwise, any jobs that use that job queue that 
require them to run sequentially will blow all to hell.

Another reason a job queue may allow something between 1 and *NOMAX (I've 
seen 3) is for performance reasons, but that's a whole different 
discussion.


Rob Berendt