Rerouting NAKed output

For OTMA clients that are hold queue capable, OTMA can reroute commit-then-send (CM0) messages on either the I/O PCB tpipe queue or the hold queue when OTMA receives a NAK response from the client.

If a NAK message turns on the reroute flag and specifies a reroute tpipe name in the reroute TPIPE field of the state data prefix, OTMA reroutes any commit-then-send messages on the I/O PCB output queue by requeuing it to the asynchronous output hold queue specified in the reroute TPIPE field.

If both a purge request and a reroute request are specified on a NAK message, OTMA issues an error message to the system console and requeues the output to the asynchronous hold queue of the tpipe used by the original input message.

When a reroute request is specified on an initial input message, if OTMA cannot deliver the commit-then-send I/O PCB output to the hold-queue capable client due to the z/OS® cross-system coupling facility failure or a client outage, OTMA reroutes the output to the asynchronous hold queue of the inputting tpipe.

To request in a NAK message that OTMA reroute asynchronous commit-then-send output, set X'20' in byte 5 in the transaction-related state data of the OTMA header and specify the tpipe name of the alternate asynchronous hold queue to which you want the output rerouted at byte 62 of the state data.