| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| NEON message parsing problems |
« View previous topic :: View next topic » |
| Author |
Message
|
| vadivel |
 Posted: Wed Apr 14, 2004 7:12 pm Post subject: NEON message parsing problems |
 |
|
Voyager
Joined: 05 Aug 2002
Posts: 79
Location: US
|
Hi,
I'm using the neon message parser to parse an IDOC. The nnfie file for the idoc is loaded into the database and the name of the idoc is SAP.IC.DELVRY03^3.
when I send an idoc to a queue and try to parse it, it throws an error saying
"NN111E: NEONMSG parser failed to process message. Message type : SAP.IC.DELVRY03^3 Error # : 1003 Error message : 16477 trailing characters "DRM1001 ....." after message parse. See the NNSY manuals for further information."
any ideas
Thanks & Regards
Vels |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Apr 15, 2004 5:43 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| 16477 trailing characters "DRM1001 ....." after message parse |
The parser thinks it has fully parsed the data, but there are still 16477 characters left.
Check that the message actually matches the NEON definition. You might be able to get more information using some of the NEON tools to check the parsing.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Missam |
| Posted: Thu Apr 15, 2004 11:01 am Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
| This Kind of errors are normally seen when working with NEONMSG parser.if you can provide the sample data and Format you are trying to use.it will be useful to find the problem. |
|
| Back to top |
|
|
| vadivel |
| Posted: Sun Apr 18, 2004 6:06 pm Post subject: |
|
|
Voyager
Joined: 05 Aug 2002
Posts: 79
Location: US
|
The problem looks to be happening only when the message contains Japanese characters. Even if I donot try parsing the message and route it directly to MQOutput node, it fails with the MQRC 2334 (Which has something to do with the MQRFH header).
So I tried getting the message in a file from the queue and resend it again using the RFHUtil, the parser is able to parse the data successfully.
I understand that in SAP, there is an exit which reformats the message and adds the RFHHeader to the message, and this is what causes the problem.
Any ideas??
Regards
Vels |
|
| 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
|
|
|
|
