| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| UTF 16 Chinese Characters |
« View previous topic :: View next topic » |
| Author |
Message
|
| stallin |
 Posted: Thu Nov 26, 2009 12:31 pm Post subject: UTF 16 Chinese Characters |
 |
|
Novice
Joined: 11 Jan 2009
Posts: 21
|
Hi,
We are trying to parse an XML which is encoded in UTF-16 having Chinese characters. CCSID 1200 / Encoding 273 was able to successfully convert itin MQ Input node but we have ASBITSTREAM statement after that to convert into BLOB where we use input root properties for ENCODING & CCSID, it is failing there.
The reason is since encoding is 273 it tries to parse with CCSID 819 and it fails for invalid XML exactly at the first Chinese Char.
I know 273/1200 may not be the correct pair to be used, can you please suggest any valid CCSID/Encoding to parse this message or any pointers to the same.
Thanks,
Stallin Vinoth |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Nov 26, 2009 1:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The encoding has nothing to do with CCSID 819. What is suspect is that the translation flag on the MQInput node is the culprit.
Also you should not set the MQInput node to translate as it will give you the text formated message in the CCSID of the qmgr (819?). This will drive you to content loss as there is no character representation in CCSID 819 for Chinese character coded in CCSID 1200.
Let the broker do any translation as needed and make sure you do not downgrade to a CCSID that does not map the chars you need.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mrch1 |
| Posted: Sun Nov 29, 2009 6:37 pm Post subject: |
|
|
Newbie
Joined: 29 Nov 2009
Posts: 5
|
 Hi!
I think you can try set the CCSID to 1381 or 1386 |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Mon Nov 30, 2009 11:36 am Post subject: Re: UTF 16 Chinese Characters |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| stallin wrote: |
| We are trying to parse an XML which is encoded in UTF-16 having Chinese characters. CCSID 1200 / Encoding 273 was able to successfully convert it in MQ Input node |
Why convert it at all? If it's already UTF-16, why not just leave it that way? Uncheck the convert box in the MQInput node.
The Encoding and CCSID fields are not related. Consult the documentation to understand what they are for, before attempting to write any code that uses them.
| stallin wrote: |
| ... but we have ASBITSTREAM statement after that to convert into BLOB where we use input root properties for ENCODING & CCSID, it is failing there. |
Details? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
