Posted: Fri Jun 02, 2006 1:45 am Post subject: CCSID Problems
Centurion
Joined: 07 Jul 2005 Posts: 138 Location: Ireland
Hello,
I've had a read of a few other peoples posts and I think I might have (some sort of) a solution to a problem we're having at the moment. The issue is relation to XML messages not containing the correct characters for unicode.
We have an application in Websphere AS that is using unicode to encode XML messages that it's creating. When these messages arriving on a central broker machine they dont contain the proper characters(for example Polish characters). I think that this is because the CCSID is set to 437 (default Windows).
We have several applications connecting to this central broker. Some unicode, some are non-unicode.
Question 1: Would changing the CCSID on the central broker to 1200 sort this out?
Question 2: Would this change fix the Polish character problem but possible wreck the messages from the other non-unicode applications?
If you are setting an encoding on the xml send the message without the MQSTR format. This way you do not convert and the string should be preserved in the XML format. Beware however of messages coming from a different platform and not bearing a payload in the advertised format...
(ex CCSID 500 message in EBCDIC but saying in ebcdic text "encoding UTF-8") etc... You might have to look into the way the message is written...
However if the message is well written XML you should be able to use get with convert...(i.e. on the wire the special chars appear as &somecode;
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