Administering the CICS-MQ adapter

You can use the control functions of the CICS®-MQ adapter to initiate, manage, and view the connection between CICS and IBM® MQ. You can use CICS-MQ monitors to control the CICS-MQ trigger monitor, CKTI.

To set up the CICS-MQ adapter, see Setting up the CICS-MQ adapter.

You can manage the CICS-MQ adapter using any of the following methods:

Using the control functions of the CICS-MQ adapter
Access the control functions by using the CKQC transaction, EXEC CICS SPI and CEMT commands, CICSPlex® SM, or CICS Explorer®.
  • You can use the CKQC transaction through the CICS-MQ adapter control panels, or from the command line, or from an application program.
  • You can use the CEMT transaction to issue commands in the CICS environment, or use the EXEC CICS system programming interface (SPI) commands in an application program.
  • If your CICS region is managed by CICSPlex SM, you can control the connection in several ways such as CICSPlex SM web user interface, using the EXEC CPSM application programming interface in an application program, or using the CMCI programming interface. These methods effectively use the EXEC CICS system programming interface (SPI) commands to update the available CICSPlex SM resource tables.
  • CICS Explorer includes SM Operations and SM Administration views for the CICS-MQ connection and MQ monitors, which provide the same functionality as the EXEC CICS SPI commands. For information about working with CICS resources using CICS Explorer, see the Help information that is provided with CICS Explorer.
Using CICS-MQ monitors to control instances of the CICS-MQ trigger monitor, CKTI
The MQMONITOR resource is the recommended method of controlling CKTI. The benefits are as follows:
  • You can set up multiple instances of CKTI to monitor an MQ initiation queue.
  • CKTI can be started automatically when the connection to the MQ queue manager is established.
  • MQMONITOR allows the CKTI or a message consuming transaction to run under a preset user ID.
CAUTION:
You can still use CKQC to start or stop instances of CKTI. However, if the region has installed MQ monitors and has multiple instances of CKTI running, using CKQC to stop CKTI could cause unpredictable results.

Summary of operator actions for the CICS-MQ connection

The following table summarizes the operator actions that you can perform for the CICS-MQ connection.
Table 1. Operator actions for CICS-MQ connection
Operator action EXEC CICS, CEMT CKQC CICS Explorer or CICSPlex SM
Start CICS-MQ connection Yes, using SET MQCONN, but you cannot specify the default initiation queue name Yes Yes
Stop CICS-MQ connection Yes, using SET MQCONN Yes Yes
Display connection status and settings Yes, using INQUIRE MQCONN Yes Yes
Display connect and disconnect time Yes, using CICS statistics commands No Yes
Display and reset detailed connection statistics including call types Yes, using CICS statistics commands (resets all statistics) Yes (resets CICS-MQ connection statistics only) No
Display tasks that are using the CICS-MQ connection Yes, but only the number of tasks, using INQUIRE MQCONN Yes, full listing of tasks No
Purge individual tasks that are using the CICS-MQ connection Yes, using SET TASK FORCEPURGE No Yes
Enable or disable CICS-MQ API-crossing exit No Yes No
Start instances of CKTI (CICS-MQ trigger monitor or task initiator) No Yes, but it is recommended to use MQMONITOR to control CKTI No
Stop instances of CKTI No Yes, but it is recommended to use MQMONITOR to control CKTI No
Start MQ monitors (MQMONITOR resources) Yes No Yes
Stop MQ monitors (MQMONITOR resources) Yes No Yes
Display and reset detailed MQMONITOR statistics including call types Yes No Yes

CICSPlex SM returns CICS statistics in the MQMONITOR record. You can reset statistics using the CICSRGN resource table.