| Author |
Message
|
| kudlanka |
 Posted: Tue Mar 09, 2010 12:43 am Post subject: BIP5288 - message being parsed by the MRM parser is larger |
 |
|
Novice
Joined: 19 Mar 2009
Posts: 20
Location: Prague
|
Hello,
is it possible to get expected length of message from messageset?
We have flow which converts xml message to mrm (messageset is generated from cobol copybook) and via http request calls backend. Answer from backend is 16000 bytes long (don't ask me why, we can not change it) and we have to convert it back to xml format.
Correct answer (real data) has only 681. We have to get only this length and send it to mapping node (mrm -> xml) if not we get error 5288.
Now we have the correct length as constant - which it is not good. Is there any better way how to solve this? I cannot find anything in documentation.
Kudlanka |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Mar 09, 2010 1:07 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
|
| Back to top |
|
|
| Herbert |
| Posted: Tue Mar 09, 2010 1:10 am Post subject: Re: BIP5288 - message being parsed by the MRM parser is larg |
|
|
Centurion
Joined: 05 Dec 2006
Posts: 146
Location: Leersum, The Netherlands
|
| kudlanka wrote: |
is it possible to get expected length of message from messageset?
We have flow which converts xml message to mrm (messageset is generated from cobol copybook) and via http request calls backend. Answer from backend is 16000 bytes long (don't ask me why, we can not change it) and we have to convert it back to xml format.
Correct answer (real data) has only 681. We have to get only this length and send it to mapping node (mrm -> xml) if not we get error 5288.
Now we have the correct length as constant - which it is not good. Is there any better way how to solve this? I cannot find anything in documentation. |
AFAIK this is not possible ( wait for mqjeff, yesterday he did point me to a nice option about MRM-CWF I did not know  )
Is your input padded with spaces? Then maybe the solution could be to make the last field variable in lenght. Only the last field in a message like this can be variable in lenght. This means you must adjust the message set after every time you import the cobol copy book.
Update: Only Edit possible? No delete? The answer of Kimbert is more complete (with a nice link) When I start writing my answer the message of Kimbert was not yet there. |
|
| Back to top |
|
|
| kudlanka |
| Posted: Fri Mar 12, 2010 5:43 am Post subject: |
|
|
Novice
Joined: 19 Mar 2009
Posts: 20
Location: Prague
|
Thanks for reply.
End of bit stream works, but now I am getting exception - wrong char x'0' in the stream (or similar - I don't have original erro message)
I hope I will handle it. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Mar 12, 2010 6:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Null padding possibly?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
