Author |
Message
|
ghoshly |
Posted: Mon Mar 07, 2011 11:20 am Post subject: Put message using rfhutil with correct Encoding |
|
|
Partisan
Joined: 10 Jan 2008 Posts: 333
|
Hi,
I have some problem regarding CCSID and Encoding. I believe when we use RFHUtil client in order to put messages, we need to use Int Fmt and PD Fmt sections in MQMD tab. Please confirm. Can somebody provide more details on this two sections, or settings required to put message with encoding like 273 , 546 or some encoding value relates to big-endian or little endian.
Thanks in advance
Tanumoy Ghosh |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Mar 07, 2011 12:33 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
You have the choice between PC -- Host (MVS/zOS..) and Unix.
You now need to know the default endianness of these platforms...
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
ghoshly |
Posted: Mon Mar 07, 2011 12:42 pm Post subject: Possible encoding value |
|
|
Partisan
Joined: 10 Jan 2008 Posts: 333
|
If we have only big endians and little endians, we should have only two possible values for encoding. But why there are so many combinations are there?
Currently I am concerned about data flow from Windows (Little Endian) to AIX (Big Endian). While sending, which encoding value should the sending application use?
Thanks for your help. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Mar 07, 2011 12:47 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Both the CCSID and the Encoding should represent the contents of the message.
This does not necessarily have anything to do with the platform the sending application is running on, nor the platform the receiving application is running on.
If you happen to know that you are using RFHUtil (which only runs on Windows) to send zOS formatted data, then you should configure RFHUtil to indicate that the message contains zOS formatted data on both the CCSID and the Encoding.
Likewise if you happen to know that you are sending Windows formatted data, then you should indicate that.
Please also make sure you understand exactly when and what kinds of data that Encoding applies to, and when it doesn't apply. |
|
Back to top |
|
 |
ghoshly |
Posted: Tue Mar 08, 2011 9:02 am Post subject: |
|
|
Partisan
Joined: 10 Jan 2008 Posts: 333
|
As far as I know, encoding affects to Integers or numeric data on how to store the data and for that only we have big endians and little endians.
Here also in WMB when I am trying to access a integer value (without convert option and Ondemand parse timing), I am getting Navigation error because of XML parsing errors have occured.
Please correct me where I am doing mistake. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Mar 08, 2011 9:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I suggest you debug the XML parsing errors.
Preferrably with a usertrace.
XML documents are entirely character data, by the way. |
|
Back to top |
|
 |
|