|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
Unconvertable Character error |
« View previous topic :: View next topic » |
Author |
Message
|
fjb_saper |
Posted: Thu Oct 08, 2009 8:58 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20767 Location: LI,NY
|
Readability fixed by admin edit _________________ MQ & Broker admin |
|
Back to top |
|
 |
rekarm01 |
Posted: Fri Oct 09, 2009 1:54 am Post subject: Re: Unconvertable Character error |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 1415
|
wbi_telecom wrote: |
Code: |
BIP2135E: Source character ''8d'' in field ''... 20 4d 8d 50 4c 20 ...'' cannot be converted to Unicode from codepage '1208'.
The source character is an invalid code point within the given codepage.
Correct the application that generated the message. |
|
''8d'' is not a valid UTF-8 character; the source ccsid is wrong. Usually that's the source application's fault, but with the FileInput node, it's more likely the message flow's fault. Determine the correct ccsid used to write the file, and set the FileInput node ccsid property appropriately.
wbi_telecom wrote: |
This does not throw the exception but the "[" in the input message transforms into "�" |
Not exactly. That might appear to be a "[" in the input message, but it's really not, (at least not for any ASCII-based character set). Applications that display messages need to know the correct character encoding too. rfhutil is useful here, as it can display messages as characters and hex bytes. |
|
Back to top |
|
 |
wbi_telecom |
Posted: Tue Oct 13, 2009 8:54 am Post subject: |
|
|
 Disciple
Joined: 15 Feb 2006 Posts: 188 Location: Harrisburg, PA
|
I think using a File Input node instead of a MQInput node is adding to the CCSID confusion. The incoming message does not have a MQMD as its a file that gets FTPed from mainframe onto the broker box which is Z linux.
When the file node picks the file up, the InputRoot.Properties.CCSID of the message is 1208 which is also the CCSID of the broker's QM. When I use that CCSID, it gives me error in casting.
If this would have been a MQ Transport, I would have received a MQ message with appropriate CCSID and Encoding from the source application which I would have used in my CREATE PARSE.
I think there is some character (According to the users its "[") that comes in the file and looks totally different once its on the broker because of the CCSID difference. No matter what CCSID I use to parse, it will not look the same.
Am I missing something?
Cheers, |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Oct 13, 2009 9:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
wbi_telecom wrote: |
Am I missing something? |
Yes.
Don't let FTP convert the data.
Tell the FileInput node that the file is in EBCDIC. |
|
Back to top |
|
 |
wbi_telecom |
Posted: Tue Oct 13, 2009 12:00 pm Post subject: |
|
|
 Disciple
Joined: 15 Feb 2006 Posts: 188 Location: Harrisburg, PA
|
Thanks Jeff and everyone who contributed to this topic earlier.
I did exactly the way you suggested and now it's working.
Cheers, |
|
Back to top |
|
 |
|
|
|
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
|
|
|
|