How RUNMQTRM detects errors

 

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

In WebSphere MQ on UNIX systems, if the RUNMQTRM trigger monitor detects any of the following errors:

• Trigger message structure not valid

• Application type unsupported

• Program cannot start

• Data-conversion error

it puts the trigger message on the dead-letter queue, having added a dead-letter header structure (MQDLH) to the 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.

In WebSphere MQ on Windows systems, the RUNMQTRM trigger monitor fails if the APPLTYPE in the process definition is a non-default application for Windows systems. For example, if an APPLTYPE of NOTESAGENT, which represents a Lotus Notes agent, is specified in the process definition, the RUNMQTRM fails. To successfully trigger a non-default application type, write your own trigger monitor application.

 

Parent topic:

When triggering does not work

fg14080_