| Author |
Message
|
| Amazer |
 Posted: Sun Jun 24, 2012 1:23 am Post subject: Error in bar file after migrating to WMB v8.0 |
 |
|
Novice
Joined: 10 Feb 2009
Posts: 24
|
Hi,
We migrated from WMB 6.1 to WMB 8.0.
When I try building a bar file (after converting the project to an application), I get an error if there is a "." in the function or procedure name. If I change it to "_" then it is OK.
For e.g Comp.Err is wrong but Comp_Err is OK.
Is there any setting globally that would take care of such errors? Or what is a quick workaround rather than editing each application and changing dots to underscores?
Thanks.
 |
|
| Back to top |
|
 |
| exerk |
| Posted: Sun Jun 24, 2012 2:08 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Moving this to the Broker forum.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jun 24, 2012 7:49 am Post subject: Re: Error in bar file after migrating to WMB v8.0 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| Amazer wrote: |
Hi,
We migrated from WMB 6.1 to WMB 8.0.
When I try building a bar file (after converting the project to an application), I get an error if there is a "." in the function or procedure name. If I change it to "_" then it is OK.
For e.g Comp.Err is wrong but Comp_Err is OK.
Is there any setting globally that would take care of such errors? Or what is a quick workaround rather than editing each application and changing dots to underscores?
Thanks.
|
Why are you changing "." to "_"? Is this because you are missing a broker schema clause? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Amazer |
| Posted: Sun Jun 24, 2012 11:12 pm Post subject: |
|
|
Novice
Joined: 10 Feb 2009
Posts: 24
|
No, it is not related to any broker schema clause.
This is a result of having procedure or function names created in MQSI ver 2.1 long back. When I migrated my project to WMB ver 6.1 it was OK.
But now when I have migrated to WMB 8.0 it is causing a problem.
Is the only alternative to change all such cases manually?
Thanks. |
|
| Back to top |
|
|
| mgk |
| Posted: Sun Jun 24, 2012 11:54 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1647
|
| Quote: |
| We migrated from WMB 6.1 to WMB 8.0. |
It would be worth raising a PMR as if it worked at 6.1 I'm not aware of any deliberate changes in this area in 8.0. Also, you could try the "In-line ESQL when compiling .msgflow" option in the BAR editor on the prepare tab to see if that makes any difference.
Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| Amazer |
| Posted: Mon Jun 25, 2012 12:33 am Post subject: |
|
|
Novice
Joined: 10 Feb 2009
Posts: 24
|
I have checked the "In-line ESQL when compiling .msgflow" option in the BAR editor - but it still does not work.
Regards,
Amazer |
|
| Back to top |
|
|
| mgk |
| Posted: Mon Jun 25, 2012 1:02 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1647
|
Can you post the exact error you see?
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| Amazer |
| Posted: Mon Jun 25, 2012 1:15 am Post subject: |
|
|
Novice
Joined: 10 Feb 2009
Posts: 24
|
This is the error:
| Quote: |
Processing file ABCDE_XYZ_Response.msgflow
Failed to add file ABCDE_XYZ_Response.msgflow to archive file.
EsqlObjectCodeLinker V6: module named [esql://routine/#"Sub_XYZ04_R_XML.To.CWF.RXYZ04"] is not defined in file [platform:/resource/MNOP4/Sub_XYZ04_R.esql] |
Regards,
Amazer |
|
| Back to top |
|
|
| Amazer |
| Posted: Mon Jun 25, 2012 1:33 am Post subject: |
|
|
Novice
Joined: 10 Feb 2009
Posts: 24
|
I just tried what was mentioned in another thread which dealt with the same error.
| Quote: |
1. Project>Clean...
2. Restart WMB toolkit
|
This worked!!
Thanks a lot for your help.
 |
|
| Back to top |
|
|
| Amazer |
| Posted: Mon Jun 25, 2012 10:15 pm Post subject: |
|
|
Novice
Joined: 10 Feb 2009
Posts: 24
|
Even though I have "Build Automatically" ON, this error happened.
I assume it is because I used the WMBv8.0 toolkit to open the workspace which was created by WMBv6.1. I did not export and import as I probably should have. After that I converted each project into an application / library.
Any feedback on this?
Thanks. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 26, 2012 1:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Build Automatically only causes builds to occur when the compiled resources are out of date compared to the EDIT: development resources.
Opening the workspace with a new version of Toolkit is going to update the project metadata, but not the project files themselves until you do *something* to cause them to be reexamined.
And they won't be out of date compared to the compiled resources until they are then re-saved.
It shouldn't be strictly necessary to restart the Toolkit in this case. A clean build should be sufficient.
Last edited by mqjeff on Tue Jun 26, 2012 3:03 am; edited 1 time in total |
|
| Back to top |
|
|
| Amazer |
| Posted: Tue Jun 26, 2012 2:34 am Post subject: |
|
|
Novice
Joined: 10 Feb 2009
Posts: 24
|
You are right. Thanks for the info.
Other application projects are working with just Project>Clean. |
|
| Back to top |
|
|
|
|
