How CKTI detects errors

 

If the CKTI trigger monitor in WebSphere MQ for z/OS detects an error in the structure of a trigger message, or if it cannot start a program, it puts the trigger message on the dead-letter (undelivered message) queue. CKTI adds a dead-letter header structure (MQDLH) to the trigger message. It uses a feedback code in the Reason field of this structure to explain why it put the message on the dead-letter queue.

An instance of CKTI stops serving an initiation queue if it attempts to get a trigger message from the queue and finds that the attributes of the queue have changed since it last accessed that queue. The attributes could have been changed by another program, or by an operator using the commands or operations and control panels of WebSphere MQ. CKTI produces an error message, which includes a reason code, explaining the action it has taken.

 

Parent topic:

When triggering does not work

fg14060_