Work management

 

This chapter describes the way in which WebSphere MQ handles work requests, and details the options available for prioritizing and controlling the jobs associated with WebSphere MQ.

Warning

Do not alter WebSphere MQ work management objects unless you fully understand the concepts of OS/400 and WebSphere MQ work management. Additional information regarding subsystems and job descriptions can be found in OS/400 Work Management. Pay particular attention to the sections on "Job Starting and Routing" and "Batch Jobs".

WebSphere MQ for iSeries incorporates the OS/400 UNIX environment and OS/400 threads. Do not make any changes to the objects in the Integrated File System (IFS).

During normal operations, a WebSphere MQ queue manager starts a number of batch jobs to perform different tasks. By default these batch jobs run in the QMQM subsystem that is created when WebSphere MQ is installed.

Work management refers to the process of tailoring WebSphere MQ tasks to obtain the optimum performance from your system, or to make administration simpler.

For example, we can:

• Change the run-priority of jobs to make one queue manager more responsive than another.

• Redirect the output of a number of jobs to a particular output queue.

• Make all jobs of a certain type run in a specific subsystem.

• Isolate errors to a subsystem.

Work management is carried out by creating or changing the job descriptions associated with the WebSphere MQ jobs. We can configure work management for:

• An entire WebSphere MQ installation

• Individual queue managers

• Individual jobs for individual queue managers