Don't know what exactly is causing your problem, but you may want to consider using the MA7K support pac to run your Trigger Monitor as a robust service. MA7K is widely known for its use with client trigger monitors, but it will also work with local trigger monitors.
This guy had a similar problem, http://www.mqseries.net/phpBB2/viewtopic.php?t=15772&highlight=ma7k but no resolution as of yet. Maybe reading the discussion will give you some ideas? -----Original Message----- From: Benjamin F. Zhou [mailto:[EMAIL PROTECTED] Sent: Monday, June 28, 2004 3:32 PM To: [EMAIL PROTECTED] Subject: trigger monitor as Windows service not working. I experienced the same problem two years back with version 5.1. Eventually, I resort to using runmqtrm at comnand line to trigger applications. But now, with 5.3 CSD07, it is still not working. I defined queue, setup trigger, defined process, and specified initq. It works fine with runmqtrm at command line, but with trigger monitor service, nothing happens when a msg arrives at the queue. Would anyone mind sharing some insight? thanks, Benjamin F. Zhou Mercedes-Benz USA x.2474 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
