| Author |
Message
|
| SandiSan |
 Posted: Fri May 07, 2010 12:34 am Post subject: Chinese Character Issue |
 |
|
Acolyte
Joined: 01 Apr 2006
Posts: 57
Location: Pune/India
|
Hi All,
I am facing a issue with chinese character. Source system is sending chinese character with CCSID 1386. In WMB 6.0 its throwing error which we try to prase the XML having chinese character. We tried to change the CCSID to 1208 message getting processed the broker successfuly however, the the value is getting changed.
Need suggestion how to process the message successfully without changing the value.
Regds
Sandisan |
|
| Back to top |
|
 |
| kimbert |
| Posted: Fri May 07, 2010 1:51 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Source system is sending chinese character with CCSID 1386 |
Are you 100% sure that the incoming message contains valid 1386 characters? If not, then there is very little that you or your message flow can do about it.
| Quote: |
| In WMB 6.0 its throwing error which we try to prase the XML having chinese character. We tried to change the CCSID to 1208 |
Please describe exactly how you changed to 1208. Did you set the Convert option on the input node? Or did you change the properties on the MQMD header? Or are you parsing as BLOB and converting to 1208 in your flow? |
|
| Back to top |
|
|
| SandiSan |
| Posted: Fri May 07, 2010 2:18 am Post subject: |
|
|
Acolyte
Joined: 01 Apr 2006
Posts: 57
Location: Pune/India
|
Kimbert thanks for your reply..
We tried in both way that is
- Using convert option in MQInput node
- Changing CodedCharSetId in MQMD.
I both the case the output chinese value is different from input value.
Also, just to let you know we are converting the message in BOLB and publishing.
Yes, I am sure that the source system is sending xml message having chinese character with CCSID 1386 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri May 07, 2010 2:36 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If you are sure your source CCSID is correct, DO NOT use conversion on the input node. Make also sure for char parsing purposes that you use char and not byte as the length... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SandiSan |
| Posted: Fri May 07, 2010 2:59 am Post subject: |
|
|
Acolyte
Joined: 01 Apr 2006
Posts: 57
Location: Pune/India
|
As is told we are publishing the message to next flow and before publishing we are converting the message to BLOB. Do you mean the we should not covert to BLOB and just publish as XML.
Also, when we try to parse incomming message with ccsid 1386 in compute node while mapping broker throws exception
XML Parsing Errors have occurred
An error has been reported by the BIPXML4C component. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri May 07, 2010 3:33 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Also, when we try to parse incomming message with ccsid 1386 in compute node while mapping broker throws exception |
So the message broker parser ( XMLNS? ) does not think that it's a valid XML document. The error message will tell you what the problem is.
| Quote: |
XML Parsing Errors have occurred
An error has been reported by the BIPXML4C component. |
That's not the whole error message - it's just the first line of the error message. You should find the rest of the message and read the advice in the User Response section.
| Quote: |
| before publishing we are converting the message to BLOB. Do you mean the we should not covert to BLOB and just publish as XML. |
No. fjb_saper is telling you not to use the Convert option on the MQInput node. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 07, 2010 4:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Also, I really really hope that you're saying that the entire message is in CCSID 1386.
Because if only *part* of it is in CCSID 1386, then you are DOA. |
|
| Back to top |
|
|
| SandiSan |
| Posted: Fri May 07, 2010 6:02 am Post subject: |
|
|
Acolyte
Joined: 01 Apr 2006
Posts: 57
Location: Pune/India
|
| Yes, entire message is with ccsid 1386. Also, locally we are pushing the message using rfhutil and setting the code page value as 1386. Broker is throwing exception when its tries to parse message in compute node. If we set the ccsid to 1208 either in MQInput node or using code in MQMD header the output chinese text is different from that of input message. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sun May 09, 2010 2:34 pm Post subject: Re: Chinese Character Issue |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| SandiSan wrote: |
| I am facing a issue with chinese character. Source system is sending chinese character with CCSID 1386. In WMB 6.0 its throwing error which we try to parse the XML having chinese character. |
The source message is bad. Without the actual error message, any relevant source bytes, or any code, it's difficult to be more specific than that.
| SandiSan wrote: |
| We tried to change the CCSID to 1208 ... |
If the source message is bad, converting it from one ccsid to another won't help. Fix the source message first. Unless an endpoint requires it, there's no need to convert at all.
| SandiSan wrote: |
| ... message getting processed the broker successfully however, the value is getting changed. |
Different ccsids can use different values to represent the same character; in that case, converting a character from one ccsid to another means changing its value.
| SandiSan wrote: |
| Need suggestion how to process the message successfully without changing the value. |
Need more details.
| kimbert wrote: |
| You should find the rest of the [error] message and read the advice in the User Response section. |
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun May 09, 2010 9:24 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
To really see the root of the problem, disconnect any debug sessions and take a user trace. The messages output will really help locate the errant character(s).
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
