Without using alternate client ID, a client application can retrieve only non-rerouted asynchronous output messages from an interaction on a shareable persistent socket connection by executing a SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT or SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interaction. This interaction must be on the same shareable persistent socket connection where the interaction from the same application led to the asynchronous output being queued.
| Interaction | Socket | Client ID | Reroute name | Alternate client ID | Comments |
|---|---|---|---|---|---|
| resume tpipe, without specifying alternate client ID | Shareable | null | null | null | Asynchronous output must be retrieved on the same connection as the previous interaction. Otherwise, the asynchronous output cannot be retrieved. If the retrieval failed, the message is lost. |
| resume tpipe, without specifying alternate client ID | Shareable | null | myRR | null | Asynchronous messages must be retrieved on the same connection as the previous interaction. If the retrieval failed, the message is rerouted to myRR. |
| resume tpipe, specifying alternate client ID | Shareable | null | N/A | myTpipe | Asynchronous messages are retrieved from tpipe myTpipe. the reRouteName and altClientID properties are mutually exclusive and cannot be used at the same time. |
| resume tpipe | Dedicated | myCID | N/A | N/A | Asynchronous messages must be retrieved by using the client ID myCID. |
For shareable persistent socket connections, the commit mode for a SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT or SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT interaction is automatically set to 0 by the IMS™ TM resource adapter, regardless of the value that is set in the IMSInteractionSpec object for that interaction. This behavior is different from the behavior for SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT or SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT interactions on dedicated persistent socket connections. For dedicated socket connections, the commit mode must be explicitly set to 0.