Rerouting commit-then-send output

You can configure IMS to reroute commit-then-send (commit mode 0) IOPCB output to an alternate OTMA tpipe hold queue for retrieval.

Normally, if IMS cannot return commit mode 0 (CM0) output to the application client, the output is routed to the tpipe hold queue associated with the client application that submitted the original message; however, if you request the reroute function, IMS reroutes the output to either a user-specified tpipe hold queue or the default tpipe hold queue HWS$DEF. Whether the reroute tpipe is a user-specified tpipe or the default tpipe, the reroute tpipe is always associated with the tmember of the original tpipe.

The reroute function can be used for managing output generated by send-only transactions and for managing output that cannot be delivered to the original client because the connection timed out or failed.

The reroute function is also useful when IMS TM Resource Adapter (formerly known as IMS Connector for Java™) is used with shareable persistent sockets. The IMS TM Resource Adapter automatically generates the client ID when connecting to IMS Connect. Consequently, the client ID is unknown to the client applications, which need the client ID to retrieve the CM0 output.

You can specify the reroute function in either CM0 or CM1 input messages. However, in the case of CM1, IMS can only reroute the CM0 output, such as might be generated by a program to program switch.

Both user-written applications and IMS TM Resource Adapter applications on either persistent sockets or transaction sockets can request the reroute function.