How WebSphere MQ uses the work management objects

Warning

Do not alter the job queue entry settings in the QMQM subsytem to limit the number of jobs allowed in the subsystem by priority. If you attempt to do this, we can stop essential WebSphere MQ jobs from running after they are submitted and cause the queue manager startup to fail.

To understand how to configure work management, first understand how WebSphere MQ uses job descriptions.

The job description used to start the job controls many attributes of the job. For example:

• The job queue on which the job is queued and on which subsystem the job runs.

• The routing data used to start the job and class that the job uses for its run-time parameters.

• The output queue that the job uses for print files.

The process of starting a WebSphere MQ job can be considered in three steps:

1. WebSphere MQ selects a job description.

   WebSphere MQ uses the following technique to determine which job description to use for a batch job:

   1. Look in the queue manager library for a job description with the same name as the job. See Understanding WebSphere MQ queue manager library names for further details about the queue manager library.

   2. Look in the queue manager library for the default job description QMQMJOBD.

   3. Look in the QMQM library for a job description with the same name as the job.

   4. Use the default job description, QMQMJOBD, in the QMQM library.

2. The job is submitted to the job queue.

   Job descriptions supplied with WebSphere MQ have been set up, by default, to put jobs on to job queue QMQM in library QMQM. The QMQM job queue is attached to the supplied QMQM subsystem, so by default the jobs start running in the QMQM subsystem.

3. The job enters the subsystem and goes through the routing steps.

   When the job enters the subsystem, the routing data specified on the job description is used to find routing entries for the job.

   The routing data must match one of the routing entries defined in the QMQM subsystem, and this defines which of the supplied classes (QMQMRUN20, QMQMRUN35, or QMQMRUN50) is used by the job.

Note:

If WebSphere MQ jobs do not appear to be starting, make sure that the subsystem is running and the job queue is not held,

If you have modified the WebSphere MQ work management objects, make sure everything is associated correctly. For example, if you specify a job queue other than QMQM/QMQM on the job description, make sure that an ADDJOBQE is performed for the subsystem, that is, QMQM.

We can create a job description for each job documented in Table 1 using the following worksheet as an example:

What is the queue manager library name? ___________ 
Does job description AMQZXMA0 exist in the queue manager library? Yes      No 
Does job description QMQMJOBD exist in the queue manager library? Yes      No 
Does job description AMQZXMA0 exist in the QMQM library?          Yes      No   
Does job description QMQMJOBD exist in the QMQM library?          Yes      No

If you answer No to all these questions, create a global job description QMQMJOBD in the QMQM library.