| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [SOLVED] Err in parsing msg |
« View previous topic :: View next topic » |
| Author |
Message
|
| Pats21 |
 Posted: Thu Jul 02, 2009 10:59 pm Post subject: [SOLVED] Err in parsing msg |
 |
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi All,
We have a msg set which was created from a COBOL copy book.
The msg flow using this msg set works fine.
However, now there is a additional field added to the copy book, which will also be sent to broker.
To achieve this we manually added this additional field into the msg set, i.e. we did not recreate the msg set again from the copy book. This was mainly done to keep the msg set id the same.
However, when we deployed the msg set and msg flow it gives us the following error:
ImbRecoverableException caught from worker->initializeParse/setFIHandler.. Message Id not in CWF File.
can someone let me know will our approach work?
or what is the best way to achieve our goal.
Thanks
Pats ...
Last edited by Pats21 on Fri Jul 03, 2009 6:39 am; edited 1 time in total |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Jul 02, 2009 11:51 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| This was mainly done to keep the msg set id the same |
You did not specify your level so I'm assuming a supported one (6.0 and above...)
Wrong approach...
Import the new copybook into the messageset.
Right Click on the copybook file and use:
new-other-Broker-import message definition from File...
This should allow you to use the cobol import wizard to reimport the copy book and overlay the definition.
You can then redeploy with the same message set.
As for your current error are you sure the message set is referenced in the flow project.? Is it included in the bar file?
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jul 03, 2009 12:39 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
There are certain things that you can do to diagnose the problem yourself. Rather than guessing at the answer, it's probably best if I tell you how to do those basics.
Please find the full text of that error message, read it carefully, and see whether you can diagnose the problem. If not, post again quoting the full text of the error. That will allow me or somebody else to look up the error code and tell you exactly what causes it.
You can get the full text of the error in several ways:
- If on Windows, look in Windows Event Viewer
- If non-Windows, take a user trace ( not the same as putting in a Trace node! )
- Find the BIP error code in the exception list and look up the error message text in the online docs.
Please note: user trace is a very useful diagnostic facility. Please get into the habit of using it. |
|
| Back to top |
|
|
| Pats21 |
| Posted: Fri Jul 03, 2009 5:23 am Post subject: |
|
|
Disciple
Joined: 08 Sep 2006
Posts: 154
|
Hi All,
Thanks for your responses. Appreciated.
I was able to solve the issue.
I just rebuilt the msg def file again from the cobol copy book, cleaned the project and rebuild it and then deployed the msg flow and msg set and it worked.
But will surely bring the tips given here into practice.
Thanks.
Pats ... |
|
| 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
|
|
|
|
