|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
Question On Encoding |
« View previous topic :: View next topic » |
Author |
Message
|
rekarm01 |
Posted: Sun Oct 11, 2009 11:49 am Post subject: Re: Question On Encoding |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 1415
|
nmaddisetti wrote: |
Yes, CCSID used by document originator (blackbox i.e EDIFECS server) is 1208. previously I confirmed this based on the discussion with EDIFECS team and now I opened the document with RFH Util and on RFH tab at left most bottom corner CCSID is showing as 1208 but not highlighted. |
Does EDIFECS provide an actual RFH header? RFHUtil doesn't populate the RFH tab when reading a message, unless the message provides an RFH header.
Confirming the data encoding with RFHUtil requires examining the bytes themselves, from the Data tab.
nmaddisetti wrote: |
Actual failure happend in production which is SunSolaries.
I took the xml file started testing on my windows box with different CCSIDs |
Copying files from one host to another can also introduce unexpected conversions.
nmaddisetti wrote: |
Let me explain you my test flow
MQInput-->Compute1-->JavaCompute-->RCD-->Compute2-->FileOutput
here I am triggering the flow by putting dummy message on the queue
In Compute1 I am copying message headers and changing the CCSID to 819 |
Since the CCSID is coming from a dummy message, why not set it to the desired value to begin with, rather than changing it later in the message flow?
nmaddisetti wrote: |
In javaCompute I am reading the file from the file system as bitstream and passing to RCD as blob. |
The message headers are coming from a dummy message, but the message data is coming from a file. That's a bit unusual, but should still work, as long as the message header(s) accurately represent the message data.
Some Java methods can also convert character data when reading a file; which Java methods does the Java Compute node use to read the file and create the bitstream?
This would be a good place to append a Trace node, to confirm that the message header(s) still match the message data.
nmaddisetti wrote: |
Now It is working with CCSID 819.
My struggle and problem now is how can I make sure I am good with 819.
Because with the first file (<Data>2710A?¹669A</Data>) I dont see parsing issue and only database issue on windows box. |
rekarm01 wrote: |
Within a message flow, parsed character data and string literals are always UCS-2, regardless of CCSID (or Encoding).
Proper conversion of character data between the broker and database depends on the broker code page, ODBC data source definition, the database character set, and the broker environment. Check the Info Center for details regarding SQL statements and support for Unicode in databases. |
nmaddisetti wrote: |
With second (<Parameter Name="iDtPos">PO BOX 1037 P4CASH †¡‰Å†©‰„†©‰[A</Parameter>) and third <Parameter Name="iDtPos">ØFOWLER</Parameter> files
I see parsig issue on windows box |
rekarm01 wrote: |
The most likely guess is that the incoming message contains a UTF-8 byte order mark (Unicode: 0xefbbbf) before the XML data. It shouldn't. |
|
|
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
|
|
|
|