IMS Connect conversational support

A conversational program is a message processing program (MPP) that processes transactions made up of several steps. The MPP does not process the entire transaction at once.

The conversational support for IMS Connect includes having conversational transactions that let you retain uninterrupted connection (continuity) for messages coming from a given client. Typically, a conversation is terminated when the message is sent and dequeued and the application program has placed blanks in the SPA, or the conversation is terminated when a COMMIT CONFIRMED messaged is received from the client. For conversational support for IMS Connect, conversations require a send-then-commit mode and are nonrecoverable.

Requirement: IMS support for SOA composite business applications requires that all iterations of a given IMS conversation be processed by the same IMS Connect and same IMS. More specifically, all iterations of a given IMS conversation must use the same conversational ID, port number, IMS Connect, and data store. This can be accomplished by using the same connection factory for every iteration of a conversation. Using the same connection factory for each iteration ensures that the same host name, port number, and data store will be used. The IMS TM Resource Adapter client must also save and reuse the same IMSInteractionSpec convID property to ensure that the same Conversational ID is used for each iteration of that conversation.

In addition, different physical socket connections, represented by IMSTCPIPManagedConnection instances, can be used for each iteration of an IMS conversation, as long as these socket connections meet the above criteria. Having originated from the same connection factory, these connections would be members of the same managed connection pool.

These requirements preclude the use of Sysplex Distributor or the SHAREPORT keyword on the PORT statement of the z/OS® TCP/IP profile when you use the IMS support for SOA composite business applications.