| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CICSPlex and Triggering |
« View previous topic :: View next topic » |
| Author |
Message
|
| lenburt |
 Posted: Thu Mar 12, 2009 11:48 am Post subject: CICSPlex and Triggering |
 |
|
Novice
Joined: 24 Sep 2004
Posts: 15
|
I have recently deployed a new transaction to a CICSPlex environment (2 regions) and my transaction is configured to trigger on the 1st message on a shared queue. What i am observing, is that the transaction is started in BOTH regions when a single message hits the queue. The transaction is coded to handle that and just exit on a 2033, but i did not expect that behavior. I thought some mechanism might use a round robin or other algorithm to determine which region to start the transaction.
Any thoughts? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Mar 12, 2009 1:04 pm Post subject: Re: CICSPlex and Triggering |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lenburt wrote: |
| I thought some mechanism might use a round robin or other algorithm to determine which region to start the transaction. |
You thought wrong I'm afraid 
| Quote: |
A triggered shared queue can generate more than one trigger message for a satisfied trigger condition. There is one trigger message generated for each local initiation queue defined on a queue manager in the queue-sharing group associated with the triggered shared queue.
|
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzae.doc/ic15390_.htm
If you want message distribution you need a cluster.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 12, 2009 2:36 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I thought some mechanism might use a round robin or other algorithm to determine which region to start the transaction. |
As the prior post point out, a trigger message is created for each initiation queue/trigger monitor currently active. This allows for the fastest image to get the triggered application running to consume the message.
This is refered to as pull-based workload management or something like that. This method is simple, yet elegant.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
