Planning for correlation of asynchronous callout responses

If a callout request generates a response, the response is treated as a new transaction that runs independently from the original transaction that generated the callout request. Consequently, you must correlate the response to the appropriate IMS transaction.

Planning for correlation involves deciding what data to use for correlation and whether or not to store any correlation data in an IMS database until the callout response returns.

You also need to ensure that the tpipe name used by the IMS application in the ISRT alternate_pcb call and the tpipe name used by either the EJB or the IMS Enterprise Suite SOAP Gateway connection bundle for the RESUME TPIPE call both point to the same OTMA asynchronous hold queue either by using the same name for each or by coding the appropriate logic in the OTMA destination routing exit routines. The tpipe name is based on the alternate client ID provided by the external application through IMS Connect. The application program issuing the callout request must specify the tpipe name of the asynchronous hold queue in an ISRT alternate_pcb call.