Hi Peter - Option 3 is your answer. Q1 and Q2 will trigger independent of each other. The fact that they use the same process definition, and therefore trigger the same transaction is immaterial. As far as processing the transaction is concerned, if the tran is defined to multiple message regions, then you can have 2 instances of your tran going at the same time, one for Q1 the other for Q2. Even without multiple regions, you should at least be able to take advantage of quick-reschedule, so the second tran will process without having to unload/reload the PSB in the region.
- Steve Gies -----Original Message----- From: Potkay, Peter M (PLC, IT) [mailto:Peter.Potkay@;THEHARTFORD.COM] Sent: Thursday, October 17, 2002 9:56 AM To: [EMAIL PROTECTED] Subject: Triggered queues on IMS - Many queues to one process definition What happens if you have 2 queues (different names) on the same queue manager that both refer to the same process definition? Let's say Q1 starts the day off with the first message and triggers TCODE ABC. Before this TCODE has a chance to process the message and end another message lands on Q2. What happens? This second message will not trigger anything, because the TCODE is already running. -Or- This second message will cause the QM to generate a trigger message to the INIT queue, where it will sit until the TCODE ends, at which point the Trigger monitor will read the INIT queue and create the IMS message to start the TCODE again. -Or- The message landing on Q2 triggers normally (assuming Q2 is closed) regardless of what Q1 may have started. The QM generates the trigger message, the trigger monitor immediately reads it and generates the IMS message to the IMS queue, where IMS will automatically restart the TCODE when it ends from the Q1 trigger. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 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 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
