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 IndexWebSphere Message Broker (ACE) SupportOutputDestinationList--RouterList configuration

Post new topicReply to topic
OutputDestinationList--RouterList configuration View previous topic :: View next topic
Author Message
newpie
PostPosted: Sun Sep 30, 2012 9:38 am Post subject: OutputDestinationList--RouterList configuration Reply with quote

Novice

Joined: 21 Jun 2012
Posts: 16

Hello All,
While setting up the Routerlist,it has been configured as mentioned below,...

SET OutputDestinationList.Destination.RouterList.DestinaionData.labelname =


Surprisingly, it worked. If you notice, the DestinationData has been spelt wrongly.
I have tried the same in MB 6 and MB7, to check if its a bug in earlier versions and fixed in MB 7,..and its the same,..

Though its not an issue, would like to know your views and comments,,...Is this a bug in the product that helped to ignore the bug in the code ?



Regards,
Allen
“When you really want something to happen, the whole world conspires to help you achieve it.”-- Paulo Cohelo
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Sun Sep 30, 2012 11:32 am Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Take a user trace and make sure it's not being 'fixed' somewhere.
Back to top
View user's profile Send private message
newpie
PostPosted: Mon Oct 01, 2012 8:19 am Post subject: Reply with quote

Novice

Joined: 21 Jun 2012
Posts: 16

Dear mqjeff,
I have tried to put a trace and could see the same from trace logs,..it worked the same way and the logs conveyed that the variable was used with the wrong spell,..and it worked,..

trace log :
-----------
Executing statement ''SET OutputDestinationList.Destination.RouterList.DestinaionData.labelname = Environment.Variables.msglabelname;'' at ('.Mainflow_Rqst_SetLabel.main', '9.3').
Assigning value ''inquiry'' to field / variable ''OutputDestinationList.Destination.RouterList.DestinaionData.labelname''.

Let me know ur views,...

_________________
Regards,
Allen
-------------------------
“When you really want something to happen, the whole world conspires to help you achieve it.”-- Paulo Cohelo
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Mon Oct 01, 2012 8:21 am Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

newpie wrote:
Dear mqjeff,
I have tried to put a trace and could see the same from trace logs,..it worked the same way and the logs conveyed that the variable was used with the wrong spell,..and it worked,..

trace log :
-----------
Executing statement ''SET OutputDestinationList.Destination.RouterList.DestinaionData.labelname = Environment.Variables.msglabelname;'' at ('.Mainflow_Rqst_SetLabel.main', '9.3').
Assigning value ''inquiry'' to field / variable ''OutputDestinationList.Destination.RouterList.DestinaionData.labelname''.

Let me know ur views,...


Spell check..... 'DestinationData', yet it still works? Wow.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Mon Oct 01, 2012 8:22 am Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

lancelotlinc wrote:
Spell check..... 'DestinationData'


That's the point of this thread.

The incorrect spelling functions properly.

I've no idea why.
Back to top
View user's profile Send private message
newpie
PostPosted: Mon Oct 01, 2012 8:36 am Post subject: Reply with quote

Novice

Joined: 21 Jun 2012
Posts: 16

@mqjeff & lancelotlinc,... you are right ,...


wondering,.!,....can we expect someone from the IBM Labs to check their code and unveil the mystery here,...


Thanks for ur replies so far,...
_________________
Regards,
Allen
-------------------------
“When you really want something to happen, the whole world conspires to help you achieve it.”-- Paulo Cohelo
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Mon Oct 01, 2012 9:33 am Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

My guess is: the SELECT used inside the node uses wildcard on the internal reference structure. et al ... OutputDestinationList.Destination.RouterList.*.labelName or some such.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
rekarm01
PostPosted: Mon Oct 01, 2012 10:22 am Post subject: Re: OutputDestinationList--RouterList configuration Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1415

newpie wrote:
Surprisingly, it worked. If you notice, the DestinationData has been spelt wrongly.

Please be more specific about what "it worked" means. Does that mean that the message flow can create the misspelled elements in the OutputLocalEnvironment tree, or that a RouteToLabel is actually using them?

newpie wrote:
Executing statement ''SET OutputDestinationList.Destination.RouterList.DestinaionData.labelname = Environment.Variables.msglabelname;'' at ('.Mainflow_Rqst_SetLabel.main', '9.3').
Assigning value ''inquiry'' to field / variable ''OutputDestinationList.Destination.RouterList.DestinaionData.labelname''.

The message flow won't issue a warning for simply creating the element.

Put a Trace node before the RouteToLabel node to display the LocalEnvironment, and check the usertrace to see what the RouteToLabel node is actually doing.
Back to top
View user's profile Send private message
newpie
PostPosted: Tue Oct 02, 2012 5:53 am Post subject: Re: OutputDestinationList--RouterList configuration Reply with quote

Novice

Joined: 21 Jun 2012
Posts: 16

rekarm01 wrote:
newpie wrote:
Surprisingly, it worked. If you notice, the DestinationData has been spelt wrongly.

Please be more specific about what "it worked" means. Does that mean that the message flow can create the misspelled elements in the OutputLocalEnvironment tree, or that a RouteToLabel is actually using them?


Yes u r right,.. the messageflow created misspelt elements, and the RouteToLabel could use them,...the messages are being routed to the appropriate label,..



rekarm01 wrote:

newpie wrote:
Executing statement ''SETA OutputDestinationList.Destination.RouterList.DestinaionData.labelname = Environment.Variables.msglabelname;'' at ('.Mainflow_Rqst_SetLabel.main', '9.3').
Assigning value ''inquiry'' to field / variable ''OutputDestinationList.Destination.RouterList.DestinaionData.labelname''.

The message flow won't issue a warning for simply creating the element.

Put a Trace node before the RouteToLabel node to display the LocalEnvironment, and check the usertrace to see what the RouteToLabel node is actually doing.


I'm not referring to the toolkit throwing an error/warning error when this element is created,.. yes, it wont throw any error/warning...

The text provided above is from the user trace log and could find that the messages are being routed,...


_________________
Regards,
Allen
-------------------------
“When you really want something to happen, the whole world conspires to help you achieve it.”-- Paulo Cohelo
Back to top
View user's profile Send private message Send e-mail
rekarm01
PostPosted: Wed Oct 03, 2012 10:09 pm Post subject: Re: OutputDestinationList--RouterList configuration Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1415

newpie wrote:
The text provided above is from the user trace log and could find that the messages are being routed,...

But it's from the wrong part of the usertrace log, so it doesn't provide any useful information about what the RouteToLabel node is doing.

rekarm01 wrote:
Put a Trace node before the RouteToLabel node to display the LocalEnvironment, and check the usertrace to see what the RouteToLabel node is actually doing.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker (ACE) SupportOutputDestinationList--RouterList configuration
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.