If your Java™ client application issues a SYNC_SEND interaction, the IMS resource adapter sends the request to IMS™ through IMS Connect and does not expect a response from IMS. Because the IMS resource adapter performs a "send only" interaction with IMS, a SYNC_SEND interaction is typically used with a non-response mode transaction.
To use a SYNC_SEND interation to run a transaction, your application must provide a value of SYNC_SEND for the interactionVerb property and a value of 0 for the commitMode property of the IMSInteractionSpec object used by the execute method. SYNC_SEND interaction processing varies depending on the type of pesistent socket used (shareable or dedicated) and the type of IMS transaction that is run.
An IMS application program associated with a transaction defined to IMS as non-response mode typically does not require an output message to the I/O PCB, therefore no output message is created and nothing is queued on the TPIPE.
The IMS application program associated with a transaction defined to IMS as non-response mode typically will insert an output message to the I/O PCB. Because the IMS resource adapter does not expect a response from a SYNC_SEND interaction, the output message, if inserted, is queued on the TPIPE with the name of the generated clientID. However, interactions SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT or SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT can be used to retrieve the response, if performed following the SYNC_SEND interaction and in the same application and on the same connection.
The IMS application program associated with a transaction defined to IMS as non-response mode typically does not insert an output message to the I/O PCB, therefore no output message is created and nothing is queued on a TPIPE.
The IMS application program associated with a transaction defined to IMS as non-response mode typically will insert an output message to the I/O PCB. Because the IMS resource adapter does not expect a response from a SYNC_SEND interaction, the output message, if inserted, is queued on the TPIPE with the name provided for the clientID of the interaction. Messages queued to this type of TPIPE can be retrieved by issuing a SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT or SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions. The TPIPE name is the clientID specified for the SYNC_SEND interaction. clientID is required for interactions that use a dedicated persistent socket connection.