Purging NAKed output

For OTMA clients that are hold-queue capable, OTMA can purge commit-then-send (CM0) I/O PCB output when OTMA receives a NAK response from the client.

If a NAK message turns on the purge request flag in the OTMA state data prefix, OTMA dequeues the commit-then-send I/O PCB output.

If neither a purge request nor a reroute request is specified on a NAK message, OTMA requeues the I/O PCB output to the asynchronous hold queue of the inputting tpipe. Messages stored in the asynchronous hold queue of a tpipe can be retrieved by a RESUME TPIPE call at a later time.

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

When a purge 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 purges the output.

OTMA does not support the purging of asynchronous output from hold queues.