Anatomy of a DP Application › Communications and Middleware › Behavior Differences

Behavior Differences

Differences exist in the communication processing CA Gen can use to support a DPC to DPS cooperative flow. These differences are typically a result of capabilities that are provided as part of a given communications protocol and not available in others. Here are some illustrations.

• CA Gen uses a conversational protocol as provided by LU6.2. This protocol provides synchronization processing that CICS DPS and IMS DPS applications use to confirm deallocation status. The CA Gen TCP/IP implementation does not provide a conversational protocol and as such does not provide a comparable synchronization process.
• MQSeries provides a timeout capability for both send and receive processing. The CA Gen TCP/IP runtime does not provide a timeout capability.
• Some communication runtimes integrate security into their execution environments by the use of a User ID and Password as part of their communications protocol. Others use user exits to provide similar capability.
• Not all communication and middleware components support the use of asynchronous cooperative flows.
• The z/OS CICS TCP/IP product includes two connection implementations:
  • CICS Socket Listener—This implementation uses the CICS Socket Listener program TISRVLIS. TISRVLIS passes the connection socket to the CA Gen server application. The application server manages the socket and closes the socket when execution completes. This is known as a non-persistent socket connection as the socket connection is not maintained from one client request to the next.
  • Direct Connect for CICS—This implementation uses a persistent socket connection where the single socket connection is maintained throughout the life of the application.

  Note: Direct Connect for CICS support is no longer supported. Earlier versions of this implementation are supported as long as the software release in which it was delivered is supported.