Specification of transaction pipe, client ID, and interaction verb

You must specify an interaction verb regardless of the commit mode that you use. Specification of the transaction pipe (tpipe) and client ID depends on the commit mode or the type of socket connection that you sue.

In IMS™ and OTMA terminology, a transaction pipe (tpipe) is a logical connection between a client (IMS Connect) and the server (IMS OTMA). The IMSConnectionSpec class has a clientID property that identifies the connection associated with that IMSConnectionSpec. The name of the IMS OTMA asynchronous output queue or tpipe where recoverable output messages are placed during an interaction is determined in one of two ways, depending on the commit mode that is used for that interaction:

  • For commit mode 0 interactions, the tpipe is identified by the client ID that is used for the interaction. Each client ID that is used for a commit mode 0 transaction has its own tpipe.
    • The client ID is automatically generated for interactions on shareable socket connections.
    • The client ID must be set by the user for interactions on dedicated socket connections.
    In general, use shareable socket connections rather than dedicated socket connections. Sharable socket connections allow for more efficient use of connections. Shareable socket connections also are less prone to problems in Sysplex Distributor and WebSphere® Application Server for z/OS® clone environments. In these environments, multiple instances of the WebSphere Application Server might communicate with the same IMS Connect and try to use the same client ID for their connections.
  • For commit mode 1 interactions, the tpipe is identified by the IMS Connect port number used for the interaction. Therefore, each port has a tpipe that is used for all clients that run commit mode 1 interactions on that port.

Whether your Java™ client is running an IMS transaction with commit mode 1 or commit mode 0, the Java client specifies a value for the interactionVerb property for the interaction. If a commit mode 0 interaction is specified and a dedicated socket connection is used by the Java client, the Java client also must provide a value for the client ID for the connection.