Specifying a destination for rerouted output

You can define the reroute destination by specifying a reroute request name. Output can only be rerouted to tpipes associated with the same tmember. Specifying a destination for rerouted output is optional.

If a client application requests that output be rerouted, but does not identify a reroute destination by specifying a tpipe name, the default reroute destination is tpipe HWS$DEF.

You can define the reroute destination by specifying a reroute request name in one or more of the following places:

  • The RRNAME= keyword in the IMS Connect DATASTORE configuration file
  • An IMS Connect user message exit
  • The IRM_REROUT_NM in the fixed IRM format of an input message associated with a SEND/RECEIVE request from a client application
  • The IRM_REROUT_NM in the fixed IRM format of a NAK message from a client application

You can specify a different reroute destination in a NAK response message than is specified by an initial input message; however, doing so can cause problems for transactions that generate multiple output messages. If a different reroute destination is specified in a NAK response message and multiple output messages are generated by the initial input message, OTMA reroutes only the message that triggered the NAK response to the destination specified in the NAK response message. After receiving the NAK response, OTMA automatically reroutes any subsequent output messages for the same transaction to the destination that was specified on the initial input message.

For more information about:
  • The RRNAME= keyword of the IMS Connect DATASTORE configuration file, see IMS Version 15.4 System Definition.
  • Coding IMS Connect user message exits, see IMS Version 15.4 Exit Routines.