Triggering in the client environment

Messages sent by IBM MQ applications running on IBM MQ MQI clients contribute to triggering in exactly the same way as any other messages, and they can be used to trigger programs on both the server and the client.

Triggering is explained in detail in the Triggering channels.

The trigger monitor and the application to be started must be on the same system.

The default characteristics of the triggered queue are the same as those in the server environment. In particular, if no MQPMO sync point control options are specified in a client application putting messages to a triggered queue that is local to a z/OS queue manager, the messages are put within a unit of work. If the triggering condition is then met, the trigger message is put on the initiation queue within the same unit of work and cannot be retrieved by the trigger monitor until the unit of work ends. The process that is to be triggered is not started until the unit of work ends.

• Process definition
  We must define the process definition on the server, because this is associated with the queue that has triggering set on.
• Trigger monitor
  The trigger monitor provided by non-z/OS IBM MQ products runs in the client environments for IBM i, UNIX, Linux, and Windows systems.
• CICS applications (non-z/OS)
  A non-z/OS CICS application program that issues an MQCONN or MQCONNX call must be defined to CEDA as RESIDENT. If you relink a CICS server application as a client, you risk losing sync point support.

Parent topic: Running applications in the IBM MQ MQI client environment