| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| problem with group terminators and \r\n |
« View previous topic :: View next topic » |
| Author |
Message
|
| findingsolution |
 Posted: Tue Aug 24, 2010 11:54 pm Post subject: problem with group terminators and \r\n |
 |
|
Novice
Joined: 27 Jul 2010
Posts: 11
|
hi I have something like this in my message
...........(record, length 50)
...........(record , length 50)
....
....
....
The problem is, when I send the message as
...........(record, length 49)
...........(record, length 50)
it generates an exception since the first record is of length 49 instead of 50 and stops there. Whereas I want it to move to the next record after generating an exception. I am using group terminators as <CR><LF> and Data pattern as \r\n. Please help me out with this |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Aug 25, 2010 3:45 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The MRM parser will not continue after a *parsing* error. If you set Failure Action correctly, it can continue after a *validation* error.
If you have declared your record to be fixed-length and 50 bytes/characters then the parser will halt when it finds a 49-byte record - because that is a parsing error.
You could change Data Element Separation to 'All Elements Delimited' or 'Tagged Delimited' and allow the length of a record to vary. If you also wanted to check the length, you could do that using Value Constraints in the message model. Those will produce *validation* errors, which are not always fatal ( you can ask for those to be reported as an Exception List when the parse finishes ). |
|
| 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
|
|
|
|
