DFS0809E IMS region region-id (in IMS back-end aaaaaaaa) has timed out for OTMA client yyyyyyyy tpipe xxxxxxxx for nn seconds.
Explanation
OTMA detected a timeout for a transaction running
in a dependent region for a CM1 message. The information in the message
is as follows:
- aaaaaaaa
- IMS name
- yyyyyyyy
- OTMA client name
- xxxxxxxx
- The transaction pipe name
- nn
- Time in seconds that the region has been in a wait state
System action
For MPP regions, IMS terminates the transaction abnormally and issues an abend 0119.
For IFP regions, the action depends on
the shared queue environment.
- Without shared queues, or with shared queues but when processing a local transaction (originating on processing IMS), no abend is issued. IMS backs out the updates and sends a deallocate abnormal flow to the end-client.
- For IFP regions, operating in a shared queue environment and processing as a back-end (message origin is not the processing IMS), an abend 0119 is issued.
Programmer response
Check the OTMA client application to determine why the required ACK or NAK response is not sent to IMS OTMA.