Managing job queues

 

As you manage the work on your system, you might find it necessary to manipulate jobs that are waiting in a job queue. Perhaps someone needs a job run immediately and the job is sitting in a queue at a low priority. Or maybe you need to perform some maintenance on a subsystem and want to move all of the jobs to a queue that is not associated with that particular subsystem.

The following information describes how to accomplish these types of management tasks.

• Assigning the job queue to the subsystem
  To assign a job queue entry to a subsystem description, use the character-based interface.

• Changing the number of jobs running simultaneously in a job queue
  The QBASE subsystem is shipped with a job queue entry for the QBATCH job queue. This entry only allows one batch job to run at a time. If you want more than one batch job from that job queue to run simultaneously then you need to change the job queue entry.

• Clearing a job queue
  When you clear a job queue, every job on the queue is deleted. This includes any jobs that are in the hold state. You can use iSeries™ Navigator or the character-based interface to clear a job queue. Jobs that are running are not affected because they are considered active jobs and are no longer on the queue.

• Creating job queues
  To create a job queue, use the character-based interface.

• Deleting a job queue
  To delete a job queue, use the character-based interface.

• Determining which subsystem has a job queue allocated
  You can determine which subsystem has allocated the job queue using the iSeries Navigator interface or the character-based interface. This is useful when you find it necessary to delete the job queue since you cannot delete a job queue to which a subsystem is active.

• Holding a job queue
  When you place a job queue on hold you prevent the processing of all of the jobs that are currently waiting on the job queue. Placing a job queue on hold has no effect on jobs that are running. Additional jobs can be placed on the job queue while it is held, but they are not processed.

• Releasing a job queue
  When you release a job queue, all of the jobs that were placed on hold as a result of placing the job queue on hold are also released. If an individual job was placed on hold before the job queue was held, then the job is not released.

• Moving a job to a different job queue
  There are many reasons why you might want to move a job to another queue. For example, sometimes jobs become backlogged in the queue because of a long running job. Perhaps the job's scheduled run time conflicts with a new job that has a higher priority. One way to manage this situation is to move the waiting jobs to another queue that is not as busy.

• Placing a job on the job queue
  Jobs are placed on the job queue by either moving an existing job from one queue to another, or by submitting a new job. Use iSeries Navigator to move jobs between queues. Use the character-based interface to submit a new job.

• Searching all job queues for a specific job
  You can use either the iSeries Navigator or the character-based interface to search job queues for a specific job.

• Specifying the priority for the job queue
  To specify the order in which the job queues are processed by the subsystem, use the character-based interface.

 

Parent topic:

Managing work

Related concepts
Job queues