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 » Problem with storing MQMD.CorrelId within actual data.

Post new topic  Reply to topic
 Problem with storing MQMD.CorrelId within actual data. « View previous topic :: View next topic » 
Author Message
DELLIPIZ
PostPosted: Wed Jan 26, 2005 2:58 pm    Post subject: Problem with storing MQMD.CorrelId within actual data. Reply with quote

Acolyte

Joined: 08 Oct 2003
Posts: 70

Hi,

What I am trying to do is to save the MQMD.CORRELD within my actual data, either XML or MRM data. So I have three WMQI flows.

In this example, the MQMD.CORRELID is set to LORIANN

1) The first flow (XML_ROUTER) takes XML data and stores the 'wmq:' + MQMD.CORRELID within an XML tag.

The ESQL looks like this:
SET OutputRoot.XML."soapenv:Envelope"."soapenv:Header"."wsa:MessageId" = 'wmq:' || TRIM(CAST(InputRoot.MQMD.CorrelId as CHAR CCSID InputRoot.Properties.CodedCharSetId));

The output looks like this:
<wsa:MessageId>wmq:LORIANN</wsa:MessageId>

So I was happy with that.

2) The next WMQI flow translates the XML to MRM.

So the MESSAGEID field in the MRM output looks like this:
wmq:LORIANN

So far so good.

3) The last flow (MRM_ROUTER) takes the MQMD.CORRELID (LORIANN) and puts it in an MRM field.

So this is my ESQL statement:
SET OutputRoot.MRM.MESSAGEID = 'wmq:' || TRIM(CAST(InputRoot.MQMD.CorrelId as CHAR CCSID InputRoot.Properties.CodedCharSetId));

BUT, now my output MRM field is this:
wmq:<!...++

And I'm not sure why.

(In general I should point out that most times my data has to do through both routers and depending on what the data is, will go through either the XML or MRM router first. However, in some cases, it will only need to go through one router, so I do need the same logic in both XML and MRM routers.)

Please help! Thanks!

-Lori
Back to top
View user's profile Send private message
JT
PostPosted: Wed Jan 26, 2005 3:21 pm    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

What is the Properties.CodedCharSetId value and does it differ from your first scenario?
Back to top
View user's profile Send private message
kirani
PostPosted: Wed Jan 26, 2005 3:26 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Please check your MQOutput node properties. By any chance are you creating a new CorrelId in Flow 1 or Flow 2?
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
DELLIPIZ
PostPosted: Wed Jan 26, 2005 3:30 pm    Post subject: Reply with quote

Acolyte

Joined: 08 Oct 2003
Posts: 70

Hi,

The input to the XML router is in Code page 437. The input to the MRM router is in Code Page 500.

Is that what you mean?

-Lori
Back to top
View user's profile Send private message
kirani
PostPosted: Wed Jan 26, 2005 3:33 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

No, I was asking whether you have "New Correl ID" box checked in any of the MQOutput node.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
kirani
PostPosted: Wed Jan 26, 2005 4:42 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

I think this is caused by your CCSID value change as you mentioned in your earlier post. Your original CCSID is 437, so your CorrelID's binary string will be created using this CCSID. IF you want to "decode" this binary data then you should use the original CCSID.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
DELLIPIZ
PostPosted: Wed Jan 26, 2005 5:59 pm    Post subject: Reply with quote

Acolyte

Joined: 08 Oct 2003
Posts: 70

Hi,

Do you have suggestions on how best to handle this situation????

Thanks!

-Lori
Back to top
View user's profile Send private message
kirani
PostPosted: Wed Jan 26, 2005 11:43 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Store your token into CHAR field, which will be converted automatically by WMQ. For example, you can store the token in MQMD.ApplIdentityData.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
DELLIPIZ
PostPosted: Thu Jan 27, 2005 7:07 am    Post subject: Reply with quote

Acolyte

Joined: 08 Oct 2003
Posts: 70

I'm confused.... I am storing the MQMD.CorrelId in a CHAR field already.

But how can I store that field properly within my actual data when the code page can change... depending on whether my input is from MVS or AIX.

Thanks!

-Lori
Back to top
View user's profile Send private message
kirani
PostPosted: Fri Jan 28, 2005 12:17 am    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Well, MQMD.CorrelId field is of BINARY type, this data does not get converted when a message is moved from one platform to another. CHAR type fields in MQMD headers are converted automatically by WMQ to the native format. MQMD.ApplIdentityData is a CHAR field, so the contents will get converted automatically.
Another option would be to store your original CCSID in some field (either in MQMD header or data portion) and use this value when you use CAST statement.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Problem with storing MQMD.CorrelId within actual data.
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.