Execution time out during RESUME TPIPE call processing with auto message control option

If the auto option is selected on the RESUME TPIPE call and a timeout occurs, to get the timeout notification and send transactions again, you must change the auto option processing mode to noauto. To get out of the auto option processing mode, you can choose one of the following options:

• Issue a RESUME TPIPE call with the auto option and set a large IRM_TIMER value to ensure that the client application will NAK the output. When the output is NAK, OTMA will change the asynchronous mode from auto to noauto to stop the sending of asynchronous output. The client application then issues READ to retrieve the timeout notification. Upon receiving the timeout notification, the client can begin sending transactions to IMS Connect.
• Issue a RESUME TPIPE call with the noauto option and set any value in the IRM_TIMER field. After receiving ACK output, repeat READ of asynch output and SEND of ACK until a timeout notification is received. (Issuing a RESUME TPIPE call with noauto changed the processing mode from auto to noauto. This also reset the asynchronous mode in OTMA to noauto where OTMA no longer supports the automatic sending of asynch output when the IMS Message Queue is empty.) The client application then issues READ to retrieve the timeout notification. Upon receiving the timeout notification, the client can begin sending transactions to IMS Connect.
• Issue a RESUME TPIPE call with noauto option and set any value in the IRM_TIMER field. If you receive NAK output, the processing mode and OTMA Asynch mode is reset to noauto. Resetting the OTMA Asynch mode to noauto stops the sending of asynch output and the NAK output terminates the process. The client application then issues READ to retrieve the timeout notification. Upon receiving the timeout notification, the client can begin sending transactions to IMS Connect.
• Issue a RESUME TPIPE call with single option and set any value in the IRM_TIMER field. The OTMA Asynch mode is reset from auto to single and no more asynchronous messages are sent. After you receive ACK or NAK output with an IRM_TIMER setting that is anything other than NO_WAIT, the single option has been completed and the client application can issue a READ to get the timeout notification. Upon receiving the timeout notification, the client can begin sending transactions to IMS Connect.
• Issue a RESUME TPIPE call with single option and set any value in the IRM_TIMER field. The OTMA Asynch mode is reset from auto to single and no more asynchronous messages are sent. After you receive ACK or NAK output with an IRM_TIMER setting of NO_WAIT, the single option has been completed and the client application does not have to issue a READ to get timeout notification. The client application can start sending transactions to IMS Connect.