Job queues

A job queue contains an ordered list of jobs waiting to be processed by a subsystem. The job queue is the first place that a submitted batch job goes before becoming active in a subsystem. The job is held here until a number of factors are met.

In order for jobs on a job queue to be processed, there must be an active subsystem that is accepting work from that job queue. When a subsystem starts, it attempts to allocate the job queues that it is configured to accept work from, and it must successfully allocate a job queue in order to process jobs from that job queue. Therefore, while one subsystem can process jobs from multiple job queues, only one subsystem can process jobs from a particular job queue at a time.

Subsystems select jobs from job queues in priority order, within limits that can be configured for each priority. Each job has a job queue priority that can be managed when the job is on the job queue through job properties. A base set of job queues is provided with your system. In addition, you can create additional job queues that you need.

Job queues can be created in the system disk pool or in an independent disk pool. Jobs placed on a job queue in an independent disk pool are ended when the independent disk pool is varied off or when an IPL of the system occurs. Jobs on a job queue do not switch to a new system with an independent disk pool.

Note: APIs, such as Open List of Job Queues (QSPOLJBQ) and Retrieve Job Queue Information (QSPRJOBQ), can be called to get information about job queues.