RESUME TPIPE error scenarios

If the IMS Connect client issues a RESUME TPIPE call for synchronous callout messages with the IRM_F0 field set to either IRM_F0_SYNONLY or IRM_F0_SYNASYN, but IRM_ARCH is not greater than or equal to IRM_ARCH3, IMS connect returns the following return and reason codes to the IMS Connect client in the RSM structure:

If IMS Connect retrieves a message on a tpipe that is used for synchronous callout message, but cannot deliver the message to the IMS Connect client, IMS Connect replies to OTMA with a NAK message. How OTMA handles the message after receiving the NAK message depends on the status of the IMS Connect client and whether the undeliverable message is a synchronous callout message or an asynchronous output message.

For asynchronous output messages, OTMA returns the asynchronous output message to the tpipe hold queue.

For synchronous callout messages:
  • If IMS Connect could not deliver the synchronous callout message because the client either timed out or otherwise became disconnected, OTMA keeps the synchronous callout message on the queue for retrieval by another RESUME TPIPE call or until the timeout interval specified on the ICAL call expires.
  • If IMS Connect could not deliver the synchronous callout message for a reason other than timeout or disconnection, such as TCP/IP errors, OTMA discards the synchronous callout message.