Implementing parallel RESUME TPIPE requests

To retrieve output from an OTMA tpipe that supports multiple active RESUME TPIPE requests, each IMS Connect client that issues a RESUME TPIPE request specifies the name of the tpipe as an alternate client ID.

How you specify an alternate client ID differs depending on the type of IMS Connect client that you are using.

To retrieve output from an OTMA tpipe that supports parallel RESUME TPIPE requests:

For user-provided IMS Connect clients, issue the RESUME TPIPE request with the following values specified in the IRM message header:
- X'01' in the IRM_ARCH field of the fixed IRM section
- The name of the target tpipe in the IRM_RT_ALTCID field of the user-defined section of the IRM. The name of the target tpipe is typically defined in IMS by the TPIPE parameter in an OTMA destination descriptor.
For IMS TM resource adapter client applications, the client application uses the altClientID property of the IMSInteractionSpec object in either of the following programming models:
- Asynchronous output programming model
- Asynchronous callout programming model
- Synchronous callout programming model

Until the maximum number of active RESUME TPIPE requests for the tpipe is reached, each RESUME TPIPE request that connects to the tpipe is active and can receive output. The maximum number of active RESUME TPIPE requests for a tpipe is defined by the LIMITRTP parameter in the OTMA client descriptor for the client.