Re: Trigger problem
The values for the target of the trigger is handled in the Process object. One trigger monitor can handle two queues. The process defination is based in the triggering queue, not the INITIATION queue. bobbee From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 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
Re: Trigger problem
2 init queues would need 2 TMs, but you can get by with a single init queue in most cases. We have dozens of queues use the same init queue. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: Anderson, Lizette T. (RyTull) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 10:20 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem But we are also using a different init queue. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Doesn't matter, it's the process definition which controls what gets triggered. One trigger monitor is all you need. Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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
Re: Trigger problem
The obvious question would be: why? ;-) You really only need one INITQ in most cases, unless - as Dennis pointed out - you have different trigger monitors; or a very high triggering volume and you want to workload-balance trigger message processing. I haven't come across an installation where two trigmons were needed (or used) for a given queue manager (whatever that means). but, if you do have two INITQ's, you might need two trigger monitors. I would save myself the hassle and additional overhead and just use one. If you odon't want to change all your triggered queue definitions you might already have, you can always create an alias for the 'second' INITQ pointing to the 'first' and do the cleanup one-by-one. HTH, Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Tue, 19 Nov 2002 09:19:55 -0600 But we are also using a different init queue. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Doesn't matter, it's the process definition which controls what gets triggered. One trigger monitor is all you need. Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received
Re: Trigger problem
Bobbee thanks so much for your help, but I am still confused. Here is how I have it setup: -The local queue points to the initiation queue and the process queue. -The initiation queue points to the process queue -The process queue points to the path. in this case d:\apps\srvapps\sales\batch\emailRCrReport.cmd test -My trigger monitor: I put the name of the initation queue in the QUEUE NAME field. Are you saying that I can leave this field blank? -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 8:10 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem The values for the target of the trigger is handled in the Process object. One trigger monitor can handle two queues. The process defination is based in the triggering queue, not the INITIATION queue. bobbee From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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
Re: Trigger problem
I am lucky. I only have two. I will change this to use just one trigger monitor. Maybe that will correct my problem. Thanks. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 12:42 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem The obvious question would be: why? ;-) You really only need one INITQ in most cases, unless - as Dennis pointed out - you have different trigger monitors; or a very high triggering volume and you want to workload-balance trigger message processing. I haven't come across an installation where two trigmons were needed (or used) for a given queue manager (whatever that means). but, if you do have two INITQ's, you might need two trigger monitors. I would save myself the hassle and additional overhead and just use one. If you odon't want to change all your triggered queue definitions you might already have, you can always create an alias for the 'second' INITQ pointing to the 'first' and do the cleanup one-by-one. HTH, Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Tue, 19 Nov 2002 09:19:55 -0600 But we are also using a different init queue. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Doesn't matter, it's the process definition which controls what gets triggered. One trigger monitor is all you need. Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail 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 --- Legal Disclaimer: The information
Re: Trigger problem
My initiation queue definition points to a process name. Should I leave this blank? I thought I had to point to a process name and therefore have two process names and two trigger monitors. The process name is on the Trigger panel of the process definition. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 12:42 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem The obvious question would be: why? ;-) You really only need one INITQ in most cases, unless - as Dennis pointed out - you have different trigger monitors; or a very high triggering volume and you want to workload-balance trigger message processing. I haven't come across an installation where two trigmons were needed (or used) for a given queue manager (whatever that means). but, if you do have two INITQ's, you might need two trigger monitors. I would save myself the hassle and additional overhead and just use one. If you odon't want to change all your triggered queue definitions you might already have, you can always create an alias for the 'second' INITQ pointing to the 'first' and do the cleanup one-by-one. HTH, Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Tue, 19 Nov 2002 09:19:55 -0600 But we are also using a different init queue. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Doesn't matter, it's the process definition which controls what gets triggered. One trigger monitor is all you need. Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide
Re: Trigger problem
Application queues (and transmission queues on distributed platforms) can use triggering, so they would have an entry in the INITQ and PROCESS fields, and TRIGGERING is ON. The initiation queue itself does not have entries in the INITQ or PROCESS fields, and it has TRIGGERING OFF. This is off because the trigger monitor is always watching the initq, so you don't need anything else to kick off. Each application queue can point to its own process, so that they can kick off their own program. The initq is just a place to put a little event marker that says run this app, or run that app. The trigger monitor reads the event marker (trigger message) in the initq and kicks off this or that program. From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] on 11/19/2002 01:53 PM Please respond to MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Trigger problem Bobbee thanks so much for your help, but I am still confused. Here is how I have it setup: -The local queue points to the initiation queue and the process queue. -The initiation queue points to the process queue -The process queue points to the path. in this case d:\apps\srvapps\sales\batch\emailRCrReport.cmd test -My trigger monitor: I put the name of the initation queue in the QUEUE NAME field. Are you saying that I can leave this field blank? -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 8:10 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem The values for the target of the trigger is handled in the Process object. One trigger monitor can handle two queues. The process defination is based in the triggering queue, not the INITIATION queue. bobbee From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 Instructions for managing your mailing list subscription are provided in the Listserv General Users
Re: Trigger problem
Thanks. -Original Message- From: Peter Heggie [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 1:57 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Application queues (and transmission queues on distributed platforms) can use triggering, so they would have an entry in the INITQ and PROCESS fields, and TRIGGERING is ON. The initiation queue itself does not have entries in the INITQ or PROCESS fields, and it has TRIGGERING OFF. This is off because the trigger monitor is always watching the initq, so you don't need anything else to kick off. Each application queue can point to its own process, so that they can kick off their own program. The initq is just a place to put a little event marker that says run this app, or run that app. The trigger monitor reads the event marker (trigger message) in the initq and kicks off this or that program. From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] on 11/19/2002 01:53 PM Please respond to MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Trigger problem Bobbee thanks so much for your help, but I am still confused. Here is how I have it setup: -The local queue points to the initiation queue and the process queue. -The initiation queue points to the process queue -The process queue points to the path. in this case d:\apps\srvapps\sales\batch\emailRCrReport.cmd test -My trigger monitor: I put the name of the initation queue in the QUEUE NAME field. Are you saying that I can leave this field blank? -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 8:10 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem The values for the target of the trigger is handled in the Process object. One trigger monitor can handle two queues. The process defination is based in the triggering queue, not the INITIATION queue. bobbee From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ Protect your PC - get McAfee.com
Re: Trigger problem
One INITQ should do it, unless of course you are working with a Client Trigger monitor in addition to the regular trigger monitor. bobbee From: Stefan Sievert [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Tue, 19 Nov 2002 10:41:40 -0800 The obvious question would be: why? ;-) You really only need one INITQ in most cases, unless - as Dennis pointed out - you have different trigger monitors; or a very high triggering volume and you want to workload-balance trigger message processing. I haven't come across an installation where two trigmons were needed (or used) for a given queue manager (whatever that means). but, if you do have two INITQ's, you might need two trigger monitors. I would save myself the hassle and additional overhead and just use one. If you odon't want to change all your triggered queue definitions you might already have, you can always create an alias for the 'second' INITQ pointing to the 'first' and do the cleanup one-by-one. HTH, Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Tue, 19 Nov 2002 09:19:55 -0600 But we are also using a different init queue. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Doesn't matter, it's the process definition which controls what gets triggered. One trigger monitor is all you need. Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail 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 --- Legal Disclaimer: The information contained in this communication may be confidential
Re: Trigger problem
You certainly need a trigger monitor for each initq. But that begs the question, why do you have another initq? -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 7:20 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem But we are also using a different init queue. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Doesn't matter, it's the process definition which controls what gets triggered. One trigger monitor is all you need. Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive
Re: Trigger problem
The LOCAL queue you are putting to has the name of the INITQ and the process name. The INITQ is just the queue that is being serviced by some (one) TRIGGER MONITOR. When the Queue MAnager decides it's time to trigger (and we will not go into that can of worms right now) it will extract information from the PROCESS Object and use that information to write a message to the INITQ. When the Triggermonitor servicing that queue reads the message it has all the information it needs to start the application no matter what queue forced a trigger message to that INITQ. You see every queue that wants to trigger a process nedds a different PROCESS Defination ONLY. if the triggered process changes OR the information you want to pass to it changes (sub fields in the PROCESS Defination). So you see, the trigger monitor is a DUMB program. It only receives data and starts processes. It knows who to start and what to pass from the data it gets from the trigger message on the INITQ and this is put there by the Queue Manager who get it from the Process Defination. One Trigger Monitor, One INITQ, One or many Process definations!! Hope this helps. From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Tue, 19 Nov 2002 12:53:39 -0600 Bobbee thanks so much for your help, but I am still confused. Here is how I have it setup: -The local queue points to the initiation queue and the process queue. -The initiation queue points to the process queue -The process queue points to the path. in this case d:\apps\srvapps\sales\batch\emailRCrReport.cmd test -My trigger monitor: I put the name of the initation queue in the QUEUE NAME field. Are you saying that I can leave this field blank? -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 8:10 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem The values for the target of the trigger is handled in the Process object. One trigger monitor can handle two queues. The process defination is based in the triggering queue, not the INITIATION queue. bobbee From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- Instructions for managing your
Re: Trigger problem
ACK!!! How about default services? You guys know I love WIN2Kservers. In all seriousness though the default services trigger monitor works fine. Is that 2cents worth? Dave -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 3:35 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem One INITQ should do it, unless of course you are working with a Client Trigger monitor in addition to the regular trigger monitor. bobbee From: Stefan Sievert [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Tue, 19 Nov 2002 10:41:40 -0800 The obvious question would be: why? ;-) You really only need one INITQ in most cases, unless - as Dennis pointed out - you have different trigger monitors; or a very high triggering volume and you want to workload-balance trigger message processing. I haven't come across an installation where two trigmons were needed (or used) for a given queue manager (whatever that means). but, if you do have two INITQ's, you might need two trigger monitors. I would save myself the hassle and additional overhead and just use one. If you odon't want to change all your triggered queue definitions you might already have, you can always create an alias for the 'second' INITQ pointing to the 'first' and do the cleanup one-by-one. HTH, Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Tue, 19 Nov 2002 09:19:55 -0600 But we are also using a different init queue. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Doesn't matter, it's the process definition which controls what gets triggered. One trigger monitor is all you need. Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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
Re: Trigger problem
Not anymore. I only have one now and thus one trigger monitor. My test still does not work. The application will not trigger and IBM still has not figured it out. Thanks for the info. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 2:41 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem You certainly need a trigger monitor for each initq. But that begs the question, why do you have another initq? -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 7:20 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem But we are also using a different init queue. -Original Message- From: Stefan Sievert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 4:20 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Doesn't matter, it's the process definition which controls what gets triggered. One trigger monitor is all you need. Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system
Re: Trigger problem
Thanks for the explanation. -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 2:43 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem The LOCAL queue you are putting to has the name of the INITQ and the process name. The INITQ is just the queue that is being serviced by some (one) TRIGGER MONITOR. When the Queue MAnager decides it's time to trigger (and we will not go into that can of worms right now) it will extract information from the PROCESS Object and use that information to write a message to the INITQ. When the Triggermonitor servicing that queue reads the message it has all the information it needs to start the application no matter what queue forced a trigger message to that INITQ. You see every queue that wants to trigger a process nedds a different PROCESS Defination ONLY. if the triggered process changes OR the information you want to pass to it changes (sub fields in the PROCESS Defination). So you see, the trigger monitor is a DUMB program. It only receives data and starts processes. It knows who to start and what to pass from the data it gets from the trigger message on the INITQ and this is put there by the Queue Manager who get it from the Process Defination. One Trigger Monitor, One INITQ, One or many Process definations!! Hope this helps. From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Tue, 19 Nov 2002 12:53:39 -0600 Bobbee thanks so much for your help, but I am still confused. Here is how I have it setup: -The local queue points to the initiation queue and the process queue. -The initiation queue points to the process queue -The process queue points to the path. in this case d:\apps\srvapps\sales\batch\emailRCrReport.cmd test -My trigger monitor: I put the name of the initation queue in the QUEUE NAME field. Are you saying that I can leave this field blank? -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 8:10 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem The values for the target of the trigger is handled in the Process object. One trigger monitor can handle two queues. The process defination is based in the triggering queue, not the INITIATION queue. bobbee From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any
Re: Trigger problem
Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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
Re: Trigger problem
It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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
Re: Trigger problem
Doesn't matter, it's the process definition which controls what gets triggered. One trigger monitor is all you need. Stefan From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Trigger problem Date: Mon, 18 Nov 2002 14:57:30 -0600 It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail 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
Re: Trigger problem
Not a problem. One trigger monitor can trigger lots of different programs in different dirrectories. Ordinarily, the only reason for multiple trigger monitors on the same qmgr is if you need DIFFERENT trigger monitors. If you are running two instances of the same trigger monitor, chances are good your train has more engines that boxcars. regards, Dennis -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 12:58 PM To: [EMAIL PROTECTED] Subject: Re: Trigger problem It triggers a different program in a different directory. -Original Message- From: Miller, Dennis [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Trigger problem Unless you have extenuating circumstances, one trigger monitor should work for both applications. -Original Message- From: Anderson, Lizette T. (RyTull) [SMTP:[EMAIL PROTECTED]] Sent: Friday, November 15, 2002 8:13 AM To: [EMAIL PROTECTED] Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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 --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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
Re: Trigger problem
I think V5.2 under Windows sets up a trigger monitor for you when you create your queue manager via the GUI. If you remove one of the trigger monitors, it should be ok. - Original Message - From: Anderson, Lizette T. (RyTull) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 15, 2002 11:13 AM Subject: Trigger problem I am having problems triggering a program on a Windows 2000 server. The triggering works fine with the runmqtrm command from the command line, but when I set the trigger monitor up using MQservices, it does not trigger. I already have one(successfully running trigger monitor) setup under services, so the new monitor is showing up as TRIGGER MONITOR(2). Any ideas? We only have two programs that need to be triggered on the server. We are running MQ 5.2. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 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
