Starting an instance of CKTI
You can start an instance of CKTI (the CICS®-WebSphere® MQ trigger monitor or task
initiator) in several ways. Using the MQMONITOR resource is the recommended method of
controlling instances of CKTI.
About this task
- User IDs for CKTI
- If an instance of CKTI is started by an MQMONITOR, the user ID associated with the CKTI transaction is obtained as follows:
- If security checking is active (that is, the SEC system initialization parameter is set to YES), the user ID is obtained from the MONUSERID attribute of the MQMONITOR resource.
- If security checking is disabled (that is, SEC is set to NO), the user ID is the user ID of the transaction that set the MQMONITOR state to started.
If CKTI is started from a terminal from the CKQC transaction or a user-written program that links to DFHMQSSQ (or CSQCSSQ, which is retained for compatibility), the user ID that CKTI uses is the same as the user ID of the terminal that started CKTI.
If CKTI starts other CICS transactions, such as user-written CICS applications, the user ID of CKTI is propagated to these applications. For example, if CKTI is running under user ID CIC1 and a trigger event occurs that requires the sender MCA transaction, CKSG, to be started, the CKSG transaction also runs under user ID CIC1. Therefore user ID CIC1 must have access to the required transmission queue.
Procedure
Using a CICS-WebSphere MQ monitorThe 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.

- Using the CICS-WebSphere MQ adapter control panel
You can run the CICS-MQ Adapter control transaction, CKQC, and then start instances of the CKTI transaction from the CICS-WebSphere MQ adapter control panel.
- Issuing CKQC STARTCKTI from the CICS command line
You can issue the CKQC STARTCKTI command to start an instance of CKTI that serves the default initiation queue or an initiation queue that you specify.
- Using a CICS application
program
To start an instance of CKTI from a CICS application program, the application program must link to the adapter
task initiation program, DFHMQSSQ (or CSQCSSQ, which is retained for compatibility). If you are
using an MQMONITOR to control CKTI, you can start the MQMONITOR from an application program that
issues EXEC CICS SET MQMONITOR (name) STARTED.
- Using an automation product
To automate the starting of trigger monitors under a specific user ID, you can use an automation product, for example, NetView. You can use it to sign on to a CICS console and issue the STARTCKTI command.