OTMA transaction orchestration enhancement
In IMS 15.5, the OTMA transaction orchestration enhancement provides a way for OTMA to identify and correctly route an external service response from IMS to a waiting IMS Connect client.
After an IMS Connect client submits a CM0 send-receive transaction request to IMS, the IMS Connect client waits for a response from IMS. IMS transaction A processes the request and performs an asynchronous callout via ALTPCB to an external processing system for a response. When the external processing system sends a response back to IMS via an OTMA client, IMS cannot route that response back to the waiting IMS Connect client because IMS OTMA has no way of identifying that the response from the external service is what the original IMS Connect client is looking for.
This transaction orchestration enhancement provides a remedy. If the new transaction orchestration function is activated for the original CM0 send-receive message, the response from the external processing system can be routed back to the waiting IMS Connect client.
On IMS 15.3 or later, the OTMA client descriptor can activate the OTMA transaction orchestration function after you apply PTFs UI96091 and UI96138 for APAR PH51897. To activate the OTMA transaction orchestration function, specify TRANORCH=YES in the OTMA client descriptor. To learn more, see OTMA transaction orchestration using asynchronous callout.
IMS Connect can also activate or deactivate this function. To enable this option for IMS Connect, apply PTF UI98354 for APAR PH57295 on IMS 15.3 or later.
On IMS 15.3 or later, make sure to apply PTF UO04689 for APAR PH65775 to support the multiple callout scenario when you want IMS to send multiple asynchronous callout messages with callout correlator token to the external systems.
Log record changes
There are no new or changed log records related to this enhancement.
Requirements
This enhancement has requirements. To learn more, see OTMA transaction orchestration using asynchronous callout.
Restrictions
This enhancement has restrictions. To learn more, see OTMA transaction orchestration using asynchronous callout.
Changes to installing and defining IMS
Changes to administering IMS
To learn about IMS administration changes for this enhancement, see OTMA transaction orchestration using asynchronous callout.
Changes to programming for IMS
This enhancement updates INQY call MSGINFO data output. To learn more, see INQY call.
Changes to troubleshooting for IMS
For a complete list of new, changed, and deleted messages and abend codes in IMS 15.5, see Message and code changes in IMS 15.5.
Changes to commands
Changes to exit routines
This enhancement includes changes to the OTMA User Data Formatting exit routine (DFSYDRU0). To learn more, see OTMA User Data Formatting exit routine (DFSYDRU0).
Changes to utilities
There are no changes to utilities related to this enhancement.
Documentation changes
The following table lists the publications that contain new or changed topics for the OTMA transaction orchestration enhancement.
| Publication | New or changed topics |
|---|---|
| Release planning |
|
| System definition | |
| Communications and connections | |
| Application programming APIs | |
| IMS messages and codes | DFS messages |
| IMS commands | Command changes relevant to PH51897 Command changes relevant to PH57295 |
| Exit routines |