ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Unexpected correlId behaviour after MQOutput

Post new topic  Reply to topic
 Unexpected correlId behaviour after MQOutput « View previous topic :: View next topic » 
Author Message
vmcgloin
PostPosted: Tue Jun 23, 2009 6:42 am    Post subject: Unexpected correlId behaviour after MQOutput Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Hi,

My apologies if this is a silly question... my excuse is that it is very hot in my lovely heated greenhouse of an office here at the height of mid-summer, and I need a fridge to sit in to get my brain functioning again.

I have a reply message flow that is putting a message using the 'Reply To Queue' destination mode on an MQOutput node. No other boxes are checked to indicate that Correl id should change. In fact the server code has already moved MsgId to CorrelId.

So why is the MQOutput node moving MsgId to CorrelId? If it was an MQReply node I would understand. Should it be doing this? How can I prevent it?
Toolkit is 6.1.0.4, Broker is 6.1.0.3

Thanks,
Vicky
Back to top
View user's profile Send private message
WMBDEV1
PostPosted: Tue Jun 23, 2009 7:11 am    Post subject: Re: Unexpected correlId behaviour after MQOutput Reply with quote

Sentinel

Joined: 05 Mar 2009
Posts: 888
Location: UK

Elements in your post seem contradictory....

vmcgloin wrote:
it is very hot in my lovely heated greenhouse of an office


and

Quote:
location: Scotland



but seriously, previously ive managed to repeat this behaviour and it does kind of make sense to me. I guess its just a feature in this mode of the MQOutput node
Back to top
View user's profile Send private message
vmcgloin
PostPosted: Tue Jun 23, 2009 7:20 am    Post subject: Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Thanks for the response. Is it a feature or a defect? Or am I doing something wrong? I can't find this feature in the documentation (yet).

Being in Scotland just means I am not used to the heat and can't cope when the air-conditioning fails.
Back to top
View user's profile Send private message
WMBDEV1
PostPosted: Tue Jun 23, 2009 7:23 am    Post subject: Reply with quote

Sentinel

Joined: 05 Mar 2009
Posts: 888
Location: UK

My take is that its an undocumented feature.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Jun 23, 2009 7:47 am    Post subject: Re: Unexpected correlId behaviour after MQOutput Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

WMBDEV1 wrote:
Elements in your post seem contradictory....

vmcgloin wrote:
it is very hot in my lovely heated greenhouse of an office


and

vmcgloin wrote:
location: Scotland



It may seem to be illogical, but there is a logic. A New Logic.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
vmcgloin
PostPosted: Tue Jun 23, 2009 8:22 am    Post subject: Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Absolutely - do I know you?
Back to top
View user's profile Send private message
vmcgloin
PostPosted: Tue Jun 23, 2009 8:35 am    Post subject: Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

I take it all back. It was a silly question as it is in fact a documented feature (albeit in an in an indirect way).

In the 6.1 help documentation -> MQOutput node -> Contents of the WebSphere MQ reply message:

Quote:
Following values in MQMD are set conditionally, based on values in the MQOutput node and the Root.MQMD folder:
IF MsgTree.MQMD.MsgType = MQMT_REQUEST THEN
MQMD.MsgType = MQMT_REPLY;
IF Nodes Message Context is Default, PassAll or PassIdentity THEN
MQMD.UserIdentifer = MsgTree.MQMD.UserIdentifier;
IF MsgTree.MQMD.Report contains MQRO_PASS_CORREL_ID THEN
MQMD.CorrelId = MsgTree.MQMD.CorrelId;
ELSE
MQMD.CorrelId = MsgTree.MQMD.MsgId;

IF MsgTree.MQMD.Report contains MQRO_PASS_MSG_ID THEN
MQMD.MsgId = MsgTree.MQMD.MsgId;
ELSE
MQMD.MsgId = MQMI_NONE;


So I just need to set MsgTree.MQMD.Report to MQRO_PASS_CORREL_ID to get the behaviour I want for replies (assuming it is compatible with what we need to do with report messages).

Thanks,
Vicky
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Jun 23, 2009 1:59 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

vmcgloin wrote:
Absolutely - do I know you?



_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Unexpected correlId behaviour after MQOutput
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.