Chapter 21: WebSphere MQSeries Trigger Monitoring

reUZE Server provides functionality for WebSphere MQSeries Trigger Monitoring for IMS, allowing IMS MPP programs to be scheduled when WebSphere MQ messages arrive on a designated WebSphere MQ queue.

To enable trigger monitoring, IBM WebSphere MQSeries Server or IBM WebSphere MQSeries Client must be installed on the machine where Enterprise Server is running.

WebSphere MQ objects required for triggering must be defined. These are:

The Application queue with:
- The trigger control set on
- A recommended trigger type of 'First'
- An initiation queue and process definition specified
The Process definition with:
- The application type set to IMS
- An application id set to the IMS transaction to be started
An Initiation queue

The objects need to be defined from the WebSphere MQ command line or IDE. See IBM WebSphere MQ Queue Parameters for details on how to do this.

Enterprise Server Configuration

The Enterprise Server region must be configured for both IMS and JES. For JES, you must define a batch initiator to process “class A” jobs. You need to ensure that enough initiators are defined for the job class to run all instances of the trigger monitor plus any other submitted jobs that will run under that class. See To define a batch initiator or printer SEP for details on how to do this.

You also need to generate a PSB for the trigger monitor and create an XA resource to allow MPP applications to interface with IBM WebSphere MQ.

Security

If security is enabled, the trigger monitor will run under the userid that submitted the JCL to start the trigger monitor.

Error Handling

The trigger monitor will put messages in the WebSphere MQ dead-letter queue (if specified) under the following conditions:

There is an error starting the desired IMS transaction
The length of the message on the Initiation Queue is incorrect
The version (MQTMC-VERSION) of the trigger message is not 1
The application type specified in the trigger message is not IMS

What You Can Do

Depending on your user granted permissions, you can do all or some of the following:

Start and stop the trigger monitor
Generate the PSB for the trigger monitor
Create the required XA resource

How to...