| Author |
Message
|
| NickB |
 Posted: Wed Jun 06, 2001 6:20 am Post subject: |
 |
|
Centurion
Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services
|
I'm using MQSI v2 under AIX and I'm trying to use the MQReply node. I'm developing some request/reply processing and unfortunately the reply node always generates a new correlation id and there doesn't appear to be an option to disable this feature. This is a serious flaw as I am generating a correlid and don't want the reply node overwriting this.
Has anybody else noticed this problem?
|
|
| Back to top |
|
 |
| kolban |
| Posted: Wed Jun 06, 2001 4:17 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
Nick,
On first reading I was sure that you had made an error. I created a message flow (using MQSI V2.0.2) and, exactly as you stated, a brand new Correlation ID was generated. Again, to be precise, prior to my MQReply node I explicitly set the MQMD.CorrelId field to be
Set OutputRoot.MQMD.CorrelId = X'123456781234567812345678123456781234567812345678';
In the resulting output message, the CorrelId was NOT that value ...
I will investigate internally within IBM but suggest that you also raise a formal report via IBM Support.
Neil |
|
| Back to top |
|
|
| kolban |
| Posted: Mon Jun 11, 2001 5:14 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
Okay, I need a head slap for this one. The MQReply node honors the settings of the MQMD.Report options. Specifically, setting this to the value MQRO_COPY_MSG_ID_TO_CORREL_ID or alternative, will cause the MQReply node to perform the correct task. This is fact the correct design (opinion) as it is the requestor which should explicitly claim what correlation (if any) it is expecting and not the server (MQSI in this case) that forces a client to behave in a certain fashion.
See the MQSeries Application Programming Reference in the MQMD section on Report for more details.
Neil |
|
| Back to top |
|
|
| NickB |
| Posted: Fri Jun 15, 2001 4:40 am Post subject: |
|
|
Centurion
Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services
|
Neil
Thanks for looking in to this. I decided to give up on the MQReply node and use a destination list to do my routing.
Thanks for your help. |
|
| Back to top |
|
|
| lee.michael |
| Posted: Tue Jan 29, 2008 6:42 pm Post subject: |
|
|
Novice
Joined: 29 Jan 2008
Posts: 10
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jan 30, 2008 3:39 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| NickB wrote: |
Neil
Thanks for looking in to this. I decided to give up on the MQReply node and use a destination list to do my routing.
Thanks for your help. |
By default the msgId gets copied to the CorrelationId.
So your setting of the correlationId without setting the Report option copy correlationId to correlationId would have caused the default behavior to happen.
Note: in our flow we first check if correlationId != MQCI_NONE.
We then move the correlationId to the messageId just before the MQReply node as the Report options are not being set by the requester.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 30, 2008 3:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
FJ - check the posting dates before encouraging the dolt who posts on 7 year old threads by following suit...... 
lee.michael - can we keep the irrelevant posts on very old threads to a minimum please? Zero is a good number to aim for!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
