| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| FileInput Node WBI V6.1 ConversionException BIP5505E |
« View previous topic :: View next topic » |
| Author |
Message
|
| rajeevreddy |
 Posted: Wed Oct 29, 2008 7:01 am Post subject: FileInput Node WBI V6.1 ConversionException BIP5505E |
 |
|
Apprentice
Joined: 07 Sep 2004
Posts: 39
|
Using FileInput Node to prase a file which was downloaded from Mian Frame(OS/390), but i keep getting below error.
ParserException BIP5171E: An error occurred while a Custom Wire Format message was being parsed:
Current message: 'msg_TESTRECORD'
Current element: 'TEST_FIELD02'
Path from message root: '/msg_TESTRECORD'
Offset from start of message: 16
See the following errors for more details.
ConversionException BIP5505E: A data conversion failed because the data was invalid.
Type of data being read: 'packed decimal, no sign found '
Data: '0x20127f8c7f7f'
Element on the CC book is TEST-FIELD02 PIC 9(10) COMP-3.
Advance thanks for your reply's
Thnaks. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Oct 29, 2008 6:28 pm Post subject: Re: FileInput Node WBI V6.1 ConversionException BIP5505E |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| rajeevreddy wrote: |
Using FileInput Node to parse a file which was downloaded from Main Frame(OS/390), but i keep getting below error.
ParserException BIP5171E: An error occurred while a Custom Wire Format message was being parsed:
Current message: 'msg_TESTRECORD'
Current element: 'TEST_FIELD02'
Path from message root: '/msg_TESTRECORD'
Offset from start of message: 16
See the following errors for more details.
ConversionException BIP5505E: A data conversion failed because the data was invalid.
Type of data being read: 'packed decimal, no sign found '
Data: '0x20127f8c7f7f'
Element on the CC book is TEST-FIELD02 PIC 9(10) COMP-3.
Advance thanks for your reply's
Thanks. |
OK you're getting garbage. Make sure the MF initializes the field correctly.
0x20127F8C7F7F is in no way a PIC 9(10) COMP-3
Legal bytes for such a number are 0-9 in positions 0 to 9 and in position 10 you have the sign C or D F I believe would mean unsigned...
So 0x00123456789D would look like a PIC S9(10) COMP-3
0x00123456789F would look like a PIC 9(10) COMP-3 value '0123456789'
Notice that you need x/2+1 bytes to represent a Pic 9(x) comp-3.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rajeevreddy |
| Posted: Thu Oct 30, 2008 1:26 pm Post subject: |
|
|
Apprentice
Joined: 07 Sep 2004
Posts: 39
|
I was able to parse the message on FileInput node after getting the file from os/390 in EBCDIC format. CC used was
01 TEST-RECORD. 00010010
15 TEST-FIELD01 PIC X(10). 00040010
15 TEST-FIELD02 PIC 9(10) COMP-3. 00050010
In my cmpute node i am mapping to XML. (Converting to XML)
SET OutputRoot.Properties.CodedCharSetId = 437;
SET OutputRoot.Properties.Encoding = 546;
SET OutputRoot.MQMD.Format = MQFMT_STRING;
SET OutputRoot.MQMD.Encoding = MQENC_NATIVE;
/*SET OutputRoot.MQMD.CodedCharSetId = 1208;*/
SET OutputRoot.XML.TESTRECORD.TEST_FIELD01= InputRoot.MRM.TEST_FIELD01;
SET OutputRoot.XML.TESTRECORD.TEST_FIELD02= InputRoot.MRM.TEST_FIELD02;
Output in the queue looks
<TESTRECORD>
<TEST_FIELD01>ðñòóôõö÷øù</TEST_FIELD01> Data looks corrupted
<TEST_FIELD02>123456789</TEST_FIELD02> Data looks Ok
</TESTRECORD>
Actually data has to be (Expected data)
<TESTRECORD>
<TEST_FIELD01>0123456789</TEST_FIELD01>
<TEST_FIELD02>123456789</TEST_FIELD02>
</TESTRECORD>
When i open the message from RFHUTIL i see the data as, (i think input data looks fine)
F0F1F2F3F4F5F6F7F8F900123456789F (EBCDIC/HEX)
I am using FileNode to read the contents from a file supplied by MainFrame developer.
In the input parsing options for Message encoding i have selected -> Big Endian with s/390 floting point (785)
Thanks for all your help. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 30, 2008 4:45 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
When i open the message from RFHUTIL i see the data as, (i think input data looks fine)
F0F1F2F3F4F5F6F7F8F900123456789F (EBCDIC/HEX)
|
OK you have 2 parts here.
F0F1F2F3F4F5F6F7F8F9 This seems to be text 0123456789 in = PIC 9(10). ( EBCDIC)
00123456789F This would be 0123456789 in PIC 9(10) comp-3. (EBCDIC)
Enjoy
_________________
MQ & Broker 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
|
|
|
|
