DFS3494E OTMA HAS TIMED OUT FOR TMEMBER/TPIPE xxxx/yyyy
or
or
Explanation
OTMA timed out waiting for an ACK or NAK from the OTMA target member (tmember or client) xxxx with the transaction pipe (tpipe) yyyy has initiated a CM0 timeout action for a missing ACK or NAK.
If the OTMA tpipe supports multiple active RESUME TPIPE requests, the hexadecimal token number, rt_token, that identifies the RESUME TPIPE call is also displayed.
If the zzzz field is present, the CM0 output message has been rerouted to the output tpipe zzzz. If the member supports the hold queue, the message is moved to the hold queue of the tpipe zzzz.
For an IMS callout message through ICAL, the IMS application that issues the synchronous callout request receives a return code of X'100' and a reason code of X'104'. The message is discarded.
- rt_token
- The identifying hexadecimal token number of the RESUME TPIPE call.
- xxxx
- The name of the OTMA client.
- yyyy
- The name of the TPIPE on which the time out occurred.
- zzzz
- The TPIPE name to which the output was rerouted.
System action
Processing continues.Operator response
Identify the cause of the missing ACK or NAK for this timeout condition. It could be an application program or a failure in the network component.
Programmer response
Make sure that your program issues an ACK or NAK to IMS for the received CM0 output message. Also, it is possible that there is a network failure so that the ACK or NAK cannot arrive at IMS OTMA.
If the OTMA client is IMS Connect, you can issue the IMS command QUERY IMSCON TYPE(CLIENT) RTTOKEN(rt_token) to identify the IMS Connect client.
Problem determination
Examine the network trace to identify which component in the network did not forward the ACK or NAK to IMS. Make sure that your program issues an ACK or NAK to IMS for the received CM0 output message or synchronous callout message.A possible cause of this problem is that there is a network failure so that the ACK or NAK cannot arrive at IMS OTMA.