A trigger monitor is simply a program with an outstanding MQGET on an initiation queue - that runs another program as needed.
First of all TRIGGERING IS VASTLY OVERRATED and in many respects old-fashioned for when MQ was a heavyweight asynchronous protocol.
In many cases it is much better to code your application as a long running task, which has an outstanding MQGET on your queue. You don't have to trigger (which causes an extra MQPUT and MQGET of the trigger message and is therefore INEFFICIENT for higher volume applications which are mainly active).
For mainly INACTIVE applications, triggering can be useful. We use the NT SERVICE trigger monitor (support Pac MA7K) which works with MQ client installations.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum