| Author |
Message
|
| hellobond070 |
 Posted: Wed Nov 18, 2009 3:19 am Post subject: CWF Parser error : Message Id not found |
 |
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
Hi All,
I am getting the below error. Could you please suggest me the ways to rectify the below issue.
I am actually trying to recreate a message set with a update in a existing cobol copy book. I import this copy book and create a .mxmd file. And when I test the flow, I get the below errors.
But when I change the fields directly in the existing mxmd file, I see the flow running properly and out message getting generated.
Thanks!!!!!
2009-11-17 08:42:04.888498 5917 ParserException BIP5167E: Custom Wire Format error while parsing/writing message ''UNDEFINED''.
2009-11-17 08:42:04.888503 5917 ParserException BIP5180E: CWF Error : Unknown message type
The CWF parser or writer has received an unknown message type identifier in the message properties.
The specified message set (''DPCRKG4002001'') does not contain a message type with this identifier.
Previous errors will supply the message set name and the message type identifier.
Check that the supplied message identifier is correct
Check that the supplied message set identifier is correct
Check that the message set contains a message type with the specified identifier. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Nov 18, 2009 3:43 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The error message is accurate. The MRM parser cannot find the specified message type in the specified message set.
- Have you updated the message set name ( or message set id, if you're still using ids ) in the input node properties?
- Does the new message set use the same names for the message types as the old one did? If not, have you adjusted the Message Type in the input node properties? |
|
| Back to top |
|
|
| hellobond070 |
| Posted: Wed Nov 18, 2009 4:16 am Post subject: |
|
|
Centurion
Joined: 18 Nov 2009
Posts: 118
|
The destination is SAP. So we are using R3 MQ links. So in the esql code we use this message set. So the esql code makes use of the message set name which i have not changed. What I have done is created a new mxmd file in the message set using the cobol copy book deleting the old mxmd file. Also i have changed the name of the mxmd file keeping the message set name same.
I have checked message set name and Id(message set (''DPCRKG4002001'') ) is all perfect as per my message set.
If I use the existing mxmd file and add fields to it for my new requirement. And then try testing the flow it works absolutely fine. Only when i try creating a new mxmd file with copybook, I m facing issues. |
|
| Back to top |
|
|
| sirsi |
| Posted: Wed Nov 18, 2009 5:50 am Post subject: |
|
|
Disciple
Joined: 11 Mar 2005
Posts: 177
|
| try creating two differenct message sets and test... |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Nov 18, 2009 7:42 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I have checked message set name and Id(message set (''DPCRKG4002001'') ) is all perfect as per my message set. |
So the next thing is to check the message names in the message set. The Message Type property should match the name of one of the messages in the message set.
If you want more help, please take a user trace and quote the full text of the error messsage(s). |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 18, 2009 6:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Do all the segment names on the IDOC match a message name in the MessageSet? And be aware that this is case sensitive! The match must be exact but trailing spaces can be cut (are not part of the message name).
Have any segments been added to the IDOC? Are they being sent now where they were not sent before? Is your message Set up to date with the IDOC?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
