Rerouting commit-then-send asynchronous output

OTMA clients that support OTMA hold queues can have OTMA reroute I/O PCB output to an alternate hold queue when the output cannot be delivered to the OTMA client.

The OTMA client can specify the reroute function on the following types of messages input to OTMA:

  • Input messages for commit-then-send transactions
  • Input messages for send-only transactions
  • NAK response to commit-then-send output

If a maximum number of tpipes has been defined for an OTMA client (tmember) and the number of tpipes associated with the tmember has reached the maximum, a new tpipe cannot be created to reroute a message. In this case, if a message cannot be rerouted because the maximum number of tpipes has been reached, OTMA deletes the message.

The maximum number of tpipes for a tmember is specified on the MAXTP parameter of the OTMA client descriptor in the DFSYDTx PROCLIB member.