| Author |
Message
|
| mattynorm |
 Posted: Thu Jun 19, 2008 4:09 am Post subject: Problem with esql in toolkit 6.1.0.2 |
 |
|
Acolyte
Joined: 06 Jun 2003
Posts: 52
|
After having upgraded my toolkit to the above version I have noticed that when retrieving projects from my code repository (Serena), some of the flows display strange behaviour with regard to esql.
When right mouse clicking on Compute Nodes, and select Open ESQL, the toolkit opens the esql file but creates a new module shell (i.e. all the bits that you would get with a new Compute node) with the same name as the correct one, at the bottom of the esql file. Saving the esql file then generates an error as the flow (correctly) states that it now has 2 modules with the same name and doesn't know which one to use.
So far I've tried deleting the surplus module and saving, changing the dropdown on the node properties to an entirely different esql module, then saving, then switching it back, then saivng again, but nothing seems to fix this problem.
Anybody else encountered this? Is it a known problem with this release? We don't really want to revert back to the previous toolkit version, as the upgrade has fixed anothe problem we were having. Is it PMR time? |
|
| Back to top |
|
 |
| sridhsri |
| Posted: Thu Jun 19, 2008 9:18 am Post subject: A PMR has been opened |
|
|
Master
Joined: 19 Jun 2008
Posts: 297
|
| I have observed this occasionally. It appears that the toolkit does have a defect. I believe a PMR has been opened for this. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Thu Jun 19, 2008 7:45 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
try rebuilding the project..
do a - clean for toolkit...
_________________
Cheers |
|
| Back to top |
|
|
| mattynorm |
| Posted: Fri Jun 20, 2008 5:46 am Post subject: |
|
|
Acolyte
Joined: 06 Jun 2003
Posts: 52
|
| Quote: |
| I believe a PMR has been opened for this. |
apologies if this is very basic stuff, but is there an easy way to search for this (or even better, do you know what the PMR number is?)?
I tried opening the toolkit using -clean, but it didn't make any difference. I do have a workaround though. |
|
| Back to top |
|
|
| chrisc |
| Posted: Sun Jun 22, 2008 4:49 pm Post subject: |
|
|
Voyager
Joined: 19 Mar 2006
Posts: 77
|
Funny, I just ran into this the other day myself (WMB v6.0) and spent two days trying to get it to acknowledge the existing ESQL modules. Like you, I was checking out existing code from a source repository.
The thing that I found was that if you just check it out directly from the repository, it seems to be unable to properly recognise the project as a message flow project or something, and hence doesn't seem to process ESQL correctly.
If I created a new, empty Message Flow Project, then did a Team->Share etc to pull it out that way, it correctly recognised the ESQL, stopped creating new ESQL modules and stopped giving me errors saying that it couldn't find the Main() method etc etc.
(Clean rebuilds etc made no difference, by the way.)
| Quote: |
| I do have a workaround |
Just out of interest, how do you resolve it at your end? |
|
| Back to top |
|
|
| mattynorm |
| Posted: Mon Jun 23, 2008 4:19 am Post subject: |
|
|
Acolyte
Joined: 06 Jun 2003
Posts: 52
|
| Quote: |
| Just out of interest, how do you resolve it at your end? |
All you can really do as far as I know is to delete the suprious module, and make the changes to the correct existing module and save the .esql file. For most of our flows there is only 1 compute node, so it's a fairly straightforward process. |
|
| Back to top |
|
|
| nagarjun_vv |
| Posted: Tue Jun 24, 2008 11:05 pm Post subject: |
|
|
Apprentice
Joined: 24 Jun 2008
Posts: 33
|
| Your code willbe there in the compute node check the name configured in compute node and and the exact code if it is different make it same and delete the new code and save the file and clean the project and check again. |
|
| Back to top |
|
|
| mattynorm |
| Posted: Wed Jun 25, 2008 1:25 am Post subject: |
|
|
Acolyte
Joined: 06 Jun 2003
Posts: 52
|
| Yes, it's moe of a pain in the backside than anything else. Not at all impressed by the 6.1.0.2 toolkit though! |
|
| Back to top |
|
|
| mattynorm |
| Posted: Wed Jul 02, 2008 3:53 am Post subject: |
|
|
Acolyte
Joined: 06 Jun 2003
Posts: 52
|
| For anyone who is interested, PMR 43565 999 866 has been raise with IBM for this. |
|
| Back to top |
|
|
| missing_link |
| Posted: Thu Jul 10, 2008 7:54 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 60
|
The issue with empty ESQL procedure shells is fixed with 6.1.0.2.0.1, however the other issue that I had (Toolkit compute node in error when no DSN even though one not needed) has now been raised as APAR IC57220.
Hopefully 6.2.0.2.0.2 will fix everything 
ash. |
|
| Back to top |
|
|
|
|
