Rerouting asynchronous output for send-only transactions

For send-only transactions from OTMA clients that are hold queue capable OTMA can reroute commit-then-send (CM0) messages on the I/O PCB output queue.

To specify a reroute request for asynchronous commit-then-send output in a send-only transaction message, specify the tpipe name of the alternate asynchronous hold queue to which you want the output rerouted in the user data section of the OTMA message prefix. For IMS Connect users, see the OMUSR_REROUT_NM field documented in OTMA user data fields used by IMS Connect.

When reroute is specified, OTMA reroute the output to the reroute tpipe instead of the input tpipe for the send-only message.

OTMA also reroutes to the alternate tpipe any IMS DFS messages generated by the send-only transaction.

However, if a send-only transaction requests an ACK or NAK for the input message, OTMA sends back an ACK after the input transaction is enqueued. If the input send-only transaction cannot be enqueued, OTMA sends back a NAK without a DFS message.