Administering the CICS-WebSphere MQ adapter
You can use the control functions of the CICS®-WebSphere® MQ adapter to initiate, manage, and view the
connection between CICS and WebSphere MQ.
You can use CICS-WebSphere MQ monitors to control the CICS-WebSphere MQ
trigger monitor, CKTI.
Before you begin
Before you can operate the CICS-WebSphere MQ adapter, you must configure your CICS region appropriately and install an MQCONN resource definition.
When you install an MQCONN resource that specifies a value in the INITQNAME attribute, CICS also dynamically creates and installs an MQMONITOR resource with the reserved name of DFHMQINI representing the default initiation queue.
DFHMQINI automatically starts when the MQ connection is established.
Optionally, you can install more MQMONITOR resources to define attributes for WebSphere MQ message consumers, such as the trigger monitor
transaction CKTI.
For detailed instructions, see Setting up the CICS-WebSphere MQ adapter.
About this task
You can manage the CICS-WebSphere MQ adapter using any of the following methods:
- Using the control functions of the CICS-WebSphere MQ adapter
- You can access the control functions using the CKQC transaction, EXEC CICS
SPI and CEMT commands, CICSPlex® SM, or the CICS Explorer®.
- 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.
- You can use the CKQC transaction through the CICS-WebSphere MQ adapter control panels, or from the command line, or from 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 CICS system programming interface (SPI) commands to update the available CICSPlex SM resource tables.
The CICS Explorer includes SM
Operations and SM Administration views for the CICS-WebSphere MQ connection and MQ monitors, which provide the
same functionality as the EXEC CICS SPI commands. For information about working
with CICS resources using the CICS Explorer, see the Help information that is provided with the CICS Explorer.
Using CICS-WebSphere MQ monitors to control instances of the CICS-WebSphere 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
- The following table summarizes the operator actions that you can perform for the CICS-WebSphere MQ
connection, and whether you can perform these actions using EXEC CICS and CEMT
commands, the CKQC transaction, the CICS Explorer,
or CICSPlex SM.
Table 1. Operator actions for CICS-WebSphere MQ connection Operator action EXEC CICS, CEMT CKQC CICS Explorer or CICSPlex SM Start CICS-WebSphere MQ connection Yes, using SET MQCONN, but you cannot specify the default initiation queue name Yes Yes Stop CICS-WebSphere 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-WebSphere MQ connection statistics only) No Display tasks that are using the CICS-WebSphere 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-WebSphere MQ connection Yes, using SET TASK FORCEPURGE No Yes Enable or disable CICS-WebSphere MQ API-crossing exit No Yes No Start instances of CKTI (CICS-WebSphere 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
YesCICSPlex SM returns CICS statistics in the MQMONITOR record. You can reset statistics using the CICSRGN resource table.
