Use OTMA exits in IMS
Use this topic if you want to use IMS Open Transaction Manager Access exits with IBM MQ for z/OS®.
If you want to send output from an IMS transaction to IBM MQ, and that transaction did not originate in IBM MQ, you need to code one or more IMS OTMA exits.
Similarly if you want to send output to a non-OTMA destination, and the transaction did originate in IBM MQ, you also need to code one or more IMS OTMA exits.
The following exits are available in IMS to enable you to customize processing between IMS and IBM MQ:
- An OTMA pre-routing exit
- A destination resolution user (DRU) exit
OTMA exit names
You must name the pre-routing exit DFSYPRX0. We can name the DRU exit anything, as long as it does not conflict with a module name already in IMS.
- Specifying the destination resolution user exit name
We can use the Druexit parameter of the OTMACON keyword of the CSQ6SYSP macro to specify the name of the OTMA DRU exit to be run by IMS.
To simplify object identification, consider adopting a naming convention of DRU0xxxx, where xxxx is the name of your IBM MQ queue manager.
If we do not specify the name of a DRU exit in the OTMACON parameter, the default is DFSYDRU0. A sample of this module is supplied by IMS. See the IMS/ESA® Customization Guide for information about this.
- Naming convention for IMS destination
You need a naming convention for the destination to which you send the output from your IMS program. This is the destination that is set in the CHNG call of your IMS application, or that is preset in the IMS PSB.
A sample scenario for an OTMA exit
Use the following topics for an example of a pre-routing exit and a destination routing exit for IMS:To simplify identification, make the OTMA destination name similar to the IBM MQ queue manager name, for example the IBM MQ queue manager name repeated. In this case, if the IBM MQ queue manager name is " VCPE ", the destination set by the CHNG call is " VCPEVCPE ".