| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| An MRM parsing error has occurred when receiving NULL fields |
« View previous topic :: View next topic » |
| Author |
Message
|
| jacquesvdm |
 Posted: Mon Feb 13, 2012 9:48 pm Post subject: An MRM parsing error has occurred when receiving NULL fields |
 |
|
Apprentice
Joined: 18 Jan 2012
Posts: 29
|
WMB 7.0.0.3
An MRM parsing error has occurred. The bit stream of the message being parsed by the MRM parser is larger than expected for a message of this type.
I get this error when parsing null values within a CSV file.
record
field1,field2,field3,,field6,field7,,field9,,field10
if I insert one space after the comma it is parsed correctly. It does however seem like null values are not interprested correctly.
I have tried all the Encoding Null options on the CSV_column (local element) and they all have the same result. |
|
| Back to top |
|
 |
| Esa |
| Posted: Mon Feb 13, 2012 11:27 pm Post subject: Re: An MRM parsing error has occurred when receiving NULL fi |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| Check that you have defined the elements as nillable. That's not enabled by default. |
|
| Back to top |
|
|
| jacquesvdm |
| Posted: Mon Feb 13, 2012 11:40 pm Post subject: |
|
|
Apprentice
Joined: 18 Jan 2012
Posts: 29
|
Don't know when It changed then but my default was set to Nillable.
Logical property, Local element , Value block, Three options, Default (selected), Fixed (not selected) and Nullable (selected)
On Physical Properties
Representation of null values block, two options, encoding null (default was Nulllogicalvalue), Encoding null value (default is blank).
I have tried all the different combinations but it has not effect on the end result.
 |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Feb 14, 2012 5:38 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
|
| Back to top |
|
|
| jacquesvdm |
| Posted: Tue Feb 14, 2012 8:55 pm Post subject: |
|
|
Apprentice
Joined: 18 Jan 2012
Posts: 29
|
Hi
Thanks, most of the settings described in that thread is now standard in version 7.
What I did however change is "Supress absent element delimeters" to Never. The default was "End of Type".
so thank you, it seems like your search skills is better than mine.   |
|
| 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
|
|
|
|
