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 » Code page conversion and MRM

Post new topic  Reply to topic
 Code page conversion and MRM « View previous topic :: View next topic » 
Author Message
RAJESHRAMAKRISHNAN
PostPosted: Wed Apr 05, 2006 4:25 pm    Post subject: Code page conversion and MRM Reply with quote

Voyager

Joined: 01 May 2004
Posts: 96

Hi All,

We are receiving Message from Mainframe. To parse this message we are using an MRM message set(CWF). If we don't set the convert option as Yes in the MQInput node, the parsing fails.

My understanding is that if we use Message Sets, MRM does an implicit conversion to parse the message. Is this correct?

Is there any documentation for this?

We are using WBIMB 5.0 on AIX.

Thanks for all your help.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Apr 05, 2006 6:11 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

No the conversion is not implicit.
You have to check the conversion flag on the MQInput node.
You can as well do an explicit conversion by doing a CAST.

See a few messages back .... this was addressed Yesterday...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
RAJESHRAMAKRISHNAN
PostPosted: Tue Apr 11, 2006 9:48 pm    Post subject: Reply with quote

Voyager

Joined: 01 May 2004
Posts: 96

Thanks very much. Is it true even in MQSI 2.1?
Back to top
View user's profile Send private message
shalabh1976
PostPosted: Tue Apr 11, 2006 10:25 pm    Post subject: Reply with quote

Partisan

Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India

Yes, I think it is.
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
shanson
PostPosted: Wed Apr 12, 2006 5:50 am    Post subject: Reply with quote

Partisan

Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley

Quote:
See a few messages back .... this was addressed Yesterday

Please can you point me at this, I looked quickly but couldn't find it?

Quote:
No the conversion is not implicit.
You have to check the conversion flag on the MQInput node.

Normally you don't have to check the conversion flag on the MQ input node. The broker (in this case the MRM parser) will automatically convert the incoming data, from the ccsid stated in the last MQ header in the message into unicode (1200), when the data is parsed and added to the message tree.

If you check the conversion flag, WMQ will data convert the data to the ccsid you specify on the MQ input node, then the broker will convert again from that ccsid into 1200 when parsing. So you end up doing two conversions (unless you specify 1200 as the ccsid of course). Also, if your data is mixed text and binary, you will need to write an MQ conversion exit.

I think we need to understand what your flow is doing a bit more, to work out why you are getting a parser failure. Are you sure that the ccsid in the MQMD and other MQ headers are correct? How are you accessing the fields in the message? What is the exact failure you are getting? How did you create your MRM CWF message model - by import or by hand - if by hand are you sure it correctly matches the data?
Back to top
View user's profile Send private message
jcv
PostPosted: Fri Aug 24, 2007 5:09 am    Post subject: Reply with quote

Chevalier

Joined: 07 May 2007
Posts: 411
Location: Zagreb

I have set conversion in MQInput node to ccsid 1208. Input MQMD ccsid is 1250.
I have connected MQOutput node and HTTPRequest node as the output nodes for the flow.
When I dump hex content of a message buffer in the output queue, I see that convert flag on MQInput node affects the result in the way I expected.
When I dump hex content of a HTTP request, that's not the case.
Trace node placed after MQInput node, which also has an TDS parser configured, shows also the same result for $Root in a trace file, same as HTTP request body dump, which is not affected by convert flag of MQInput node.
I generate default HTTP headers from input, so that I pass default content type: text/xml; charset=utf-8.
How shall I configure flow, so that HTTP request body is converted to 1208, without writing ESQL or Java? Do I have to avoid somehow internal conversion to 1200? Thanks.
Back to top
View user's profile Send private message Visit poster's website
fjb_saper
PostPosted: Fri Aug 24, 2007 6:12 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Did you set the OutputRoot.Properties.CodedCharSetId to 1208? (UTF-8 )
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
jcv
PostPosted: Fri Aug 24, 2007 7:02 am    Post subject: Reply with quote

Chevalier

Joined: 07 May 2007
Posts: 411
Location: Zagreb

It seems that would be sufficient. Meaning, I don't have to check the conversion flag on the MQ input node at all. Thanks a lot.
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 » Code page conversion and MRM
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.