| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Triggered queues on IMS - Many queues to 1 process definitio |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Thu Oct 17, 2002 11:56 am Post subject: Triggered queues on IMS - Many queues to 1 process definitio |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
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
Keep Calm and MQ On |
|
| Back to top |
|
 |
| oz1ccg |
| Posted: Fri Oct 18, 2002 3:38 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
Dear Peter,
You can have as many queues refering the same process as you want....
I'm assuming that we're dealing with trigger type first. and there are triggermonitor running (open input count of the initqueue > 0)
MQSeries will generate a trigger message when the queue depth changes from 0 to 1, when the open input counter is 0. (there are generated extra triggers under other circumstances... as staed in the manual)
The generated trigger message is holding information about which local queue(QL) caused the trigger. This means that you can have the same program handling more queues, just by obtaining the queue name from the trigger message as shown in some of the documentation and samples.
How TCODE is executed depends on the operating system, and how it's configured, maning how many concurent instances of the same TCODE is allowed.
Just my $0.02 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
