CICS-WebSphere MQ adapter components
CICS® and the CICS-WebSphere MQ adapter share the same address space. The WebSphere® MQ queue manager runs in its own address space.
Figure 1 shows the relationship between CICS, the CICS-WebSphere MQ adapter, and WebSphere MQ.
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). For more information about task-related user exits and stub programs, see Task-related user exit programs.
Each CKTI transaction is usually in an MQGET WAIT state, ready to respond to any trigger messages that are placed on its initiation queue.

The CICS-WebSphere MQ adapter display function uses two main temporary storage queues for each calling task to store the output data for browsing. The names of the queues are ttttCKRT and ttttCKDP, where tttt is the terminal identifier of the terminal from which the display function is requested. Do not try to access these queues.
The CICS-WebSphere MQ adapter uses the name DFH.genericapplid(8).QMGR to issue CICS ENQ and CICS DEQ calls during processing; for example, starting and stopping the connection. Do not use similar names for CICS ENQ or DEQ purposes.