Author |
Message
|
coolparsi21 |
Posted: Thu Nov 03, 2016 9:20 am Post subject: French characters failing : Help required |
|
|
Newbie
Joined: 07 Mar 2014 Posts: 9
|
hi guys , i m running a weird issue . My input message is in XML with french characters on mainframe
I am converting it into BLOB --> CCSID 819 , after that i am converting into XML -->CCSID 1252 (failing with 1208) and then i am converting into MRM with CCSID 819 encoding 0 . When i check the logged message it shows eg RAJ� boxes instead of french characters
I am using WMB7 on ZOS with ESQL
What i m doing wrong . Any help appreciated |
|
Back to top |
|
 |
Vitor |
Posted: Thu Nov 03, 2016 9:32 am Post subject: Re: French characters failing : Help required |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
coolparsi21 wrote: |
What i m doing wrong |
- you're using BLOB for XML
- you're using CCSID 819
- you're using WMBv7 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
coolparsi21 |
Posted: Thu Nov 03, 2016 10:16 am Post subject: Re: French characters failing : Help required |
|
|
Newbie
Joined: 07 Mar 2014 Posts: 9
|
Vitor wrote: |
coolparsi21 wrote: |
What i m doing wrong |
- you're using BLOB for XML
- you're using CCSID 819
- you're using WMBv7 |
Should 1252 be ok ZOS to use ? |
|
Back to top |
|
 |
Vitor |
Posted: Thu Nov 03, 2016 10:39 am Post subject: Re: French characters failing : Help required |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
coolparsi21 wrote: |
Vitor wrote: |
coolparsi21 wrote: |
What i m doing wrong |
- you're using BLOB for XML
- you're using CCSID 819
- you're using WMBv7 |
Should 1252 be ok ZOS to use ? |
Why are you doing any of this? No part of your described process makes sense.
- _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Nov 03, 2016 10:59 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Why aren't you leaving XML as is? _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Nov 03, 2016 11:05 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
bruce2359 wrote: |
Why aren't you leaving XML as is? |
Exactly _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Nov 04, 2016 4:39 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Why are you bothering with so many CCSIDs?
You should only be concerned with 2 CCSIDs:
The CCSID of the incoming message (mainframe CCSID?) and UTF-8 = CCSID 1208.
Anything in between will just get you in trouble and is not worth exploring.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Nov 04, 2016 4:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
XML supports only a very small set of CCSIDs. UTF-8 is very common.
Once you have read and parsed your INPUT XML, it is a logical message tree. It doesn't have an overall CCSID, although individual fields are actually in an internall CCSID (1200? 1202? I've forgotten).
But you don't need to worry about that.
When you are outputting XML, you should not be trying to change the CCSID on it. If the mainrame can't handle the very few CCSIDs that XML is allowed to use, then the mainframe is broken.
If you really need to change the CCSID of the XML (and this will likely also break it), you need to set the desired CCSID on an ASBITSTREAM and send that out.
But.
You should not be using MRM. At all.
You should not be using MBv7. At all.
You should not be changing the CCSID of the XML string to match what you think can represent French characters. Unicode can handle *all* French characters, and Unicode includes 1200 and 1208. XML can use... is it 1208? I've forgotten.
If the mainframe can't parse the XML if it is not in one of the few CCSIDs that XML is allowed to use, then the mainframe parser is broken.
So there are a lot of things that are very very questionable about the whole solution you are trying to build. And you are better off finding a new job or a new client, then trying to solve this questionable problem. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Nov 04, 2016 4:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Also.
Mods, please move this to the Broker forum... _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Nov 04, 2016 5:12 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Moved to Broker forum. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
timber |
Posted: Fri Nov 04, 2016 3:33 pm Post subject: |
|
|
 Grand Master
Joined: 25 Aug 2015 Posts: 1292
|
Actually, XML can use any CCSID, and XMLNSC will happily parse XML in any valid CCSID ( provided that the text is properly encoded in the declared CCSID, of course). Here's what the XML specification says on the subject:
Quote: |
Although an XML processor is required to read only entities in the UTF-8 and UTF-16 encodings, it is recognized that other encodings are used around the world, and it may be desired for XML processors to read entities that use them. In the absence of external character encoding information (such as MIME headers), parsed entities which are stored in an encoding other than UTF-8 or UTF-16 MUST begin with a text declaration (see 4.3.1 The Text Declaration) containing an encoding declaration |
I agree with the previous responses though;the OP needs to explain why they are messing about with CCSIDs in this way. That will help the conversation considerably. |
|
Back to top |
|
 |
|