Different factors determine how the jobs are selected from a job
queue and started.
- Maximum active jobs for subsystems
- This represents the maximum number of jobs that can be running in a subsystem.
After this limit is reached, no more jobs can start in the subsystem.
- Maximum active jobs for job queues
- This represents the maximum number of jobs from the job queue that can
be running in a subsystem at the same time. After this limit is reached, no
more jobs can start from that job queue.
- Priority on job queue
- Jobs that are waiting to run are selected based on the job queue priority.
The subsystem attempts to run higher priority jobs first (job queue priority
ranges from 0 through 9 where 0 is the higher priority), but if the number
of jobs running from a priority level reaches the Maximum Active Jobs value
per priority level, the next priority level is processed. (If jobs with the
same priority enter the job queue, the first job submitted will run first,
then the second, and so on.)
- Sequence
- You specify the sequence in the job queue entry of the subsystem description.
The sequence number defines the order in which the subsystem will process
the job queues. The subsystem takes jobs from the job queue with the lowest
sequence number first. If there are no more jobs on the job queue, or if one
of the maximum values associated with the job queue is reached, the subsystem
will process the job queue with the next highest sequence number.