Starting CKTI using a CICS-MQ monitor

The MQMONITOR resource, if set up properly, enables the CKTI transaction to start automatically when the connection to the MQ queue manager is established. If the MQMONITOR that controls CKTI is not automatically started, you can manually start the MQ monitor in several ways.

Before you begin

  • If you want to use MQMONITOR to control instances of CKTI in a CICS region, you must define and install such MQMONITOR resources. Table 1 lists some important attributes that you should specify for an MQMONITOR that controls CKTI.

    Note that attributes AUTOSTART(YES) and STATUS(ENABLED) should be defined for an MQMONITOR that is to automatically restart when the MQ connection is established. If you want to disable automatic restart and prefer to manually start the MQ monitor, define the MQMONITOR resource with AUTOSTART(NO) or without the AUTOSTART attribute.

    Table 1. MQMONITOR resource attributes for monitoring initiation queue
    Attribute Required / Optional Default Description
    AUTOSTART Optional YES This attribute controls auto-restart of the MQ monitor:
    AUTOSTART(YES)
    Enables CKTI to restart automatically when the connection to the MQ queue manager is established.
    AUTOSTART(NO)
    The MQ monitor is not started automatically. After the connection to the MQ queue manager is established, you have to manually start the MQ monitor.
    MONUSERID Required - Specify the user ID to be associated with CKTI.

    This attribute is only effective when security checking is active (that is, the SEC system initialization parameter is set to YES).
    QNAME Optional If omitted, the default is &APPLID..INITIATION.QUEUE where &APPLID. is the applid of the CICS region Specify the name of the MQ initiation queue to be monitored.
    STATUS Optional ENABLED This attribute makes the resource available for use in the region.
    TRANSACTION Optional CKTI Specifies the 4-character ID of the CICS®-supplied trigger monitor (or task initiator) transaction.
    Note: If you are using your own MQ trigger monitor, specify the name of this transaction. For considerations about using your own MQ trigger monitors in your CICS® environment, see The CICS-MQ trigger monitor.
  • If security checking is active (that is, the SEC system initialization parameter is set to YES), ensure that the user ID associated with the transaction that attempts to set the MQ monitor state to started is a surrogate of the user ID defined in MONUSERID and is authorized to start transactions associated with the MONUSERID. In the case of setting the MQ monitor state through a CICSPlex® SM API interface such as the CICS Explorer®, the user ID to be associated with the MQ monitor transaction is either the region user ID or the PLTPIUSR user ID (if specified).

Procedure

  • To automatically start an MQ monitor that controls CKTI, check that the MQMONITOR resource has the attributes AUTOSTART(YES) and STATUS(ENABLED).
    When the connection between CICS and MQ has been established, CICS will start MQ monitors that have been installed with attributes AUTOSTART(YES) and STATUS(ENABLED) if the user ID associated with the task that set the MQCONN resource to CONNECTED has sufficient authority to start the associated transactions. Then, an instance of CKTI will be running.
  • To manually start an MQ monitor that controls CKTI, you can use any of the methods as described in Starting a CICS-MQ monitor.