When triggering does not work

 

A program is not triggered if the trigger monitor cannot start the program or the queue manager cannot deliver the trigger message. For example, the ApplId in the process object must specify that the program is to be started in the background; if this is not done, the trigger monitor cannot start the program.

If a trigger message is created but cannot be put on the initiation queue (for example, because the queue is full or the length of the trigger message is greater than the maximum message length specified for the initiation queue), the trigger message is put instead on the dead-letter (undelivered message) queue.

If the put operation to the dead-letter queue cannot complete successfully, the trigger message is discarded and a warning message is sent to the console (z/OS) or to the system operator (i5/OS), or put on the error log.

Putting the trigger message on the dead-letter queue might generate a trigger message for that queue. This second trigger message is discarded if it adds a message to the dead-letter queue.

If the program is triggered successfully but abends before it gets the message from the queue, use a trace utility (for example, CICS AUXTRACE if the program is running under CICS) to find the cause of the failure.

• How CKTI detects errors
  

• How CSQQTRMN detects errors
  

• How RUNMQTRM detects errors
  Describes the actions taken by the RUNMQTRM trigger monitor when it detects certain errors.

 

Parent topic:

Starting WebSphere MQ applications using triggers

fg14050_