| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| ccsid 1200 issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| jonasb |
 Posted: Wed Dec 08, 2010 12:04 am Post subject: ccsid 1200 issue |
 |
|
Apprentice
Joined: 20 Dec 2006
Posts: 49
Location: Sweden
|
Hi,
the environment:
Broker 7.0.0.1, MQ 7.0.1.3, AIX 6100-05
We are having trouble with a .Net generated message, we get the following error in the broker system log:
| Code: |
Dec 7 16:45:04 <machinename> user:err|error WebSphere Broker v7001[16646220]: (<Broker>.<execgrp>)[8506]BIP5009E: XML Parsing Errors have occurred. : <Broker>.9b4242ac-2c01-0000-0080-c0a43074ee6e: /build/S700_P/src/MTI/MTIforBroker/GenXmlParser2/XmlImbParser.cpp: 634: XmlImbParser::parseFirstChild: :
|
Message looks ok in rfh2-util, and from the MQMD header you get:
codepage: 1200
format: MQSTR
The first part of the message looks like this in rfh2-util:
| Code: |
<.E.n.v. e.l.o.p. 3C004500 6E007600 65006C00 6F007000
e. .x.s. i.:.n.o. 65002000 78007300 69003A00 6E006F00
N.a.m.e. s.p.a.c. 4E006100 6D006500 73007000 61006300
e.S.c.h. e.m.a.L. 65005300 63006800 65006D00 61004C00
o.c.a.t. i.o.n.=. 6F006300 61007400 69006F00 6E003D00
".B.a.c. k.E.n.d. 22004200 61006300 6B004500 6E006400
|
My inputnode is in message domain XMLNS.
Can anyone spot any obvious error? Or can anyone help me on what I should look for, since I'm running out of ideas?
Thanks in advance!
_________________
contact admin
Last edited by jonasb on Wed Dec 08, 2010 2:35 am; edited 1 time in total |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Dec 08, 2010 12:58 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What do you see when you check the xml radio button in rfcutil?
Also make sure you did not have the convert flag checked in rfcutil
So far the hex content looks good for CCSID 1200. Just check the endianness as well. (MQ Encoding) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jonasb |
| Posted: Wed Dec 08, 2010 2:15 am Post subject: |
|
|
Apprentice
Joined: 20 Dec 2006
Posts: 49
Location: Sweden
|
Hi,
Thank you fjb_saper for helping me!
Here is the beginning of the data from the XML view of the rfhutil:
| Code: |
<Envelope xsi:noNamespaceSchemaLocation="BackEndEnvelope.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TransmissionInformation> |
Here is the MQMD in hex:
Looks like encoding 546? (starting from byte 24 if I understand it)
| Code: |
4D 44 20 20 01 00 00 00 00 00 00 00 08 00 00 00 ; MD ............
FF FF FF FF 00 00 00 00 22 02 00 00 B0 04 00 00 ; ÿÿÿÿ...."....... |
546 should be expected from a windows machine, right?
If I cut the message from rfhutil xml-view, save it as a file and put it on the queue, it works well.
More pointers greatly appreciated!
_________________
contact admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 08, 2010 3:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| rekarm01 |
| Posted: Wed Dec 08, 2010 4:06 am Post subject: Re: ccsid 1200 issue |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| contact admin wrote: |
The first part of the message looks like this in rfh2-util:
| Code: |
| <.E.n.v. e.l.o.p. 3C004500 6E007600 65006C00 6F007000 |
|
For character data, the ccsid specifies the encoding scheme (including endianness):- ccsid=1200: UTF-16BE (big-endian)
- ccsid=1202: UTF-16LE (little-endian)
- ccsid=1204: UTF-16 with BOM (byte order mark)
The correct input ccsid is 1202, not 1200.
| contact admin wrote: |
| My inputnode is in message domain XMLNS. |
XMLNSC is usually a better choice.
| contact admin wrote: |
| Looks like encoding 546? |
MQMD.Encoding only applies to numeric data in the message. When MQMD.Format=MQFMT_STRING, there is no numeric data in the message. But 546 would be the expected value for a Windows machine. |
|
| Back to top |
|
|
| jonasb |
| Posted: Wed Dec 08, 2010 6:16 am Post subject: thanks |
|
|
Apprentice
Joined: 20 Dec 2006
Posts: 49
Location: Sweden
|
| Quote: |
For character data, the ccsid specifies the encoding scheme (including endianness):
ccsid=1200: UTF-16BE (big-endian)
ccsid=1202: UTF-16LE (little-endian)
ccsid=1204: UTF-16 with BOM (byte order mark)
The correct input ccsid is 1202, not 1200.
|
Of course.
 
My lack of experience with usc-2/utf-16 code pages is very obvious!
Using the second char in the file as an example: "E" is U+0045 and that would mean 0x0045 in 1200, and 0x4500 in 1202, etc.
Thank you for taking the time to help me!
_________________
contact admin |
|
| 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
|
|
|
|
