Posted: Mon Oct 18, 2004 8:18 pm Post subject: Aggregate nodes internal working
Disciple
Joined: 10 Feb 2004 Posts: 160
(win 2k, wibimb 5.0 with csd 4 and mq 5.3 with csd 07)
Hi,
I am using aggregate nodes to coordinate my requests.
I save the original message in a queue locally and send other message to mainframe in the fan out flow.
so in the fanin flow i aggregate 2 messages.
1. The flows works perfectly fine but I wanted to know how the messages are aggregated internally by the broker.I dont see any kind of information attached to the message that has come from the mainframes. I read somewhere that the messages are aggregated using correlid. Since I am using the MQ CICS bridge i had to set the msg id of the original message to NONE and CORRELID to NEW_SESSION. Where is the information stored? How are the messages aggregated?
2. I used the multiple instances on the flows within a single execution group and it works fine. Could anyone be able to explain how the messages are aggregated in this case? How does the broker know that this particular message is related to this particular thread?
3. Just for Fun I disabled the get on the control queue connected to the control terminal of the aggreate reply but the flow worked perfectly fine. So does it mean that we dont need the control information?
Thanks, Appreciate your replies..
Joined: 17 Oct 2003 Posts: 344 Location: IBM Hursley
The internals of aggregation are a whole subject on their own. To try and answer your questions:
1) Yes the MQ correlid is used to match the messages.
2) Threads are not related to messages.
3) The control->reply connection is only used if a timeout pops.
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