The topics in this section describe some of the different processing models
that a Java™ client
can use with the IMS™ resource adapter. The topics included are:
Overview of commit mode processing
Commit mode refers to the type of commit processing performed by IMS.
The Java client
specifies the commit mode protocol to be used when it submits a transaction
request to IMS.
SYNC_SEND programming model
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.
SYNC_SEND_RECEIVE programming model
To run a transaction in IMS, your Java application executes a SYNC_SEND_RECEIVE
interaction. Your application provides a value of SYNC_SEND_RECEIVE for the
interactionVerb property and a value of 0 or 1 for the commitMode property
of the IMSInteractionSpec object used by the execute method. However, the
SYNC_SEND_RECEIVE interaction processing is different for shareable and dedicated
persistent sockets.
Retrieving asynchronous output
There are two socket connections, shareable persistent socket and dedicated persistent socket, that can be used to retrieve asynchronous output. The way to retrieve asynchronous output messages is different depending on the socket connection used. The interactionVerb properties that can retrieve asynchronous output are: SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT, and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT.
Displaying output message counts
Using IMS Connect commands, you can choose to display output message counts. This topic describes how to display those message counts.