| Author |
Message
|
| broker_new |
 Posted: Tue Feb 13, 2007 7:38 pm Post subject: Working with TDS Messages |
 |
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
parse--->next Exception
Last edited by broker_new on Wed Feb 14, 2007 11:29 am; edited 1 time in total |
|
| Back to top |
|
 |
| gregop |
| Posted: Wed Feb 14, 2007 1:33 am Post subject: |
|
|
Voyager
Joined: 24 Nov 2006
Posts: 81
|
I don't think there is anything you can set in the MRM to allow parsing of character data in an integer element.
I suggest you either get the sender application to pad the integer element with zeros or change variable b to as character.
If b is character you can always replace the blanks with zeros in esql (and cast to int if necessary). |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Feb 14, 2007 4:20 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
Good news : The null handling features of the MRM parser were designed for exactly this situation.
On the TDS properties for element a:
- Set 'Encoding Null' to 'NullLiteralValue'
- Set 'Encoding Null Value' to five spaces
The MRM parser will create element 'a' in the message tree and assign it a null value. |
|
| Back to top |
|
|
| vsr |
| Posted: Wed Feb 14, 2007 6:46 am Post subject: |
|
|
Centurion
Joined: 04 Apr 2006
Posts: 104
|
|
| Back to top |
|
|
| broker_new |
| Posted: Fri Feb 23, 2007 8:30 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
Yes i got it,
I did the same thing and one more thing is that we need to check the Nillable property for that particular element in TDS MessageDefnition file.
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
|
|
