Adapter components

Figure 15 shows the relationship between CICS, the CICS adapter, and WebSphere MQ. CICS and the adapter share the same address space; the queue manager executes in its own address space.

Part of the adapter is a CICS task-related user exit that communicates with the WebSphere MQ message manager. CICS management modules call the exit directly; application programs call it through the supplied API stub program (CSQCSTUB). Task-related user exits and stub programs are described in the CICS Customization Guide.

Each CKTI transaction is normally in an MQGET WAIT state, ready to respond to any trigger messages that are placed on its initiation queue.

The adapter management interface provides the operation and control functions described in the WebSphere MQ for z/OS System Administration Guide.

Figure 15. How CICS, the CICS adapter, and a WebSphere MQ queue manager are related

adapter, and the WebSphere MQ subsystem. The CICS task initiation transaction flows through the CICS task-related user exit, and on to the WebSphere MQ subsystem's message manager, as do CICS application programs, CICS syncpoint manager, CICS task manager and CICS termination flows. There is also a communication flow between the task-related user exit and the Subtask TCB. In a separate flow, the CICS PLT startup program sends a CKQC transaction through the CICS Adapter and onto the WebSphere MQ subsystem's connection manager." />