Task initiator or trigger monitor (CKTI)

CKTI starts a CICS® transaction when a WebSphere® MQ trigger message is read; for example, when a message is put onto a specific queue.

When a message is put onto an application message queue, a trigger is generated if the trigger conditions are met. The queue manager then writes a message, containing user-defined data, known as a trigger message, to the initiation queue that has been specified for that message queue. In a CICS environment, you can set up an instance of CKTI to monitor an initiation queue and to retrieve the trigger messages from it as they arrive. CKTI starts another CICS transaction, specified using the DEFINE PROCESS command, which typically reads the message from the application message queue and then processes it. The process must be named on the application queue definition, not the initiation queue.

Each copy of CKTI services a single initiation queue. To start or stop a copy of CKTI, you must supply the name of the queue that this CKTI is to serve or is now serving. You cannot start more than one instance of CKTI against the same initiation queue from a single CICS subsystem.

If you issue a CKQC STARTCKTI or a CKQC STOPCKTI command without specifying an initiation queue, these commands are automatically interpreted as referring to the default initiation queue for the CICS region. You can specify the name of the default initiation queue in the MQCONN resource definition for the CICS region. When you install the MQCONN resource definition, CICS creates and installs an implicit MQINI resource definition to represent the default initiation queue. You can change the name of the default initiation queue by changing and reinstalling the MQCONN resource definition to create a new MQINI resource definition. You can also name an alternative default initiation queue if you start the CICS-WebSphere MQ connection manually.