MQSeries.net :: View topic - FileInput Node WBI V6.1.0.8 packed decimal, no sign found

Michaelscof · Posted: Wed Jun 29, 2011 8:18 pm Post subject:

Using FileInput Node to prase a file which was coming from Main Frame, but i keep getting below error.

I imported the copybook and created the messagedefination file. I am getting the below error when conveting the field DLT-AUD-PAID-AMT PIC S9(09)V99 COMP-3. from the exsisting copybook.

I check the field properties to default and nillable.Physical properties checked as singed and representation of null values specified as NullLiteralFIll and Space. Is there anything i need to mention in fileinput node properties to parse it correctly. I need very desperate help on this one :hel

p:

The copy book field which
ParserException BIP5285E: Parsing errors have occurred.
Message set name: 'WCPayGoPolicyListFileProcessing_MsgSet'
Message format: 'CWF1'
Message type path: '/msg_WSOUTDTLREC/DTL_TRAN_TYPE'
Review other error messages to find the cause of the errors.
2011-06-29 14:00:21.483463 6320 ParserException BIP5171E: An error occurred while a Custom Wire Format message was being parsed:
Current message: 'msg_WSOUTDTLREC'
Current element: 'DTL_AUD_PAID_AMT'
Path from message root: '/msg_WSOUTDTLREC'
Offset from start of message: 26
See the following errors for more details.
2011-06-29 14:00:21.483470 6320 ConversionException BIP5505E: A data conversion failed because the data was invalid.
Type of data being read: 'packed decimal, no sign found '
Data: '0x00000160da25'
Data conversion when reading or writing a message failed because the input data was invalid for the output data type.
Review other error messages for details of the message set and message type.
Check that the message model is correct and that the processed message is of the expected format and type. Specifically, the following actions might help to resolve the problem:
1. Check that the bit stream is correctly aligned with the model. For example, check the lengths of input elements against the model.
2. Check that the input message has the correct Encoding and Coded Character Set ID applied to the message body.
3. Check that the input message has an appropriate WebSphere MQ format applied to the message body.
4. If the error occured for a numeric field then check that the input data is compatible with the physical format settings defined in the model.
5. If the input message is incompatible with the MRM model definitions then check the message at source[/code]