| Author |
Message
|
| MrSmith |
 Posted: Thu Mar 20, 2008 6:07 am Post subject: V6 Build workspace.... |
 |
|
Master
Joined: 20 Mar 2008
Posts: 215
|
Hi, new here
I have V6.0.2 with interim fixes patch 11 of the toolkit. I have 2 particular esql files which have come from a V5 version of the toolkit. These 2 esql files consistently "break" the build of the workspace after saving the file (have been making small change and saving to ascertain a pattern), that is the only way to do anything with the toolkit from that point on is to get task manager to end the process (platform is Windows XP with all the packs etc etc) and crash the JVM.
I have taken off auto build, i have ensured adequate jvmheap allocation and have imported the projects singularly, built the workspace and then repeated the exercise, have checked the event viewer under applications and checked the workspace log - NOTHING!!
I have now resorted to commenting out the whole file and individually uncommenting line by line until i find the offending code BUT there is no consistency: it has failed on procedure calls which have been commented for the time being but will do a simple esql SET on one line say line 66 but on uncommenting line 67 "throws" the toolkit into this non completing workspace build, even tho line 67 is a repeat of line 66 (just for testing purposes). Am now bald from pulling hair out and although have searched forum and seen other posts on the workspace build not completing this would seem to be slightly different in that its almost at line level within each esql file.....any constructive ideas please |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Thu Mar 20, 2008 8:52 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Hi, welcome to the forum.
With JVM crashes, it sounds like you should raise a PMR.
One thing I'd suggest is to also check any files that are using your ESQL, as these may be inadvertantly causing the problem (i.e. the toolkit is causing them to be rebuilt when the ESQL gets changed).
-Matt |
|
| Back to top |
|
|
| MrSmith |
| Posted: Thu Mar 20, 2008 9:06 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
| Quote: |
With JVM crashes, it sounds like you should raise a PMR.
|
Matt thanks for reply. The JVM crash itself is only becasue I have to end it via the task manager else it literally (cos i tried it) just sticks on a percentage, which seems dependant on how far along the build it thinks it is, and just hangs there like forever (well in fact a whole night).
I will raise a PMR and also notice that ifix13 is out there but not sure it will fix my problem. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 20, 2008 9:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Open a new ESQL file.
Copy and paste all the ESQL code from the "bad" files to the "good" files.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| MrSmith |
| Posted: Wed Mar 26, 2008 3:33 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
| Quote: |
Open a new ESQL file.
Copy and paste all the ESQL code from the "bad" files to the "good" files. |
Jeff
i have tried that thinking it might be like RSA on some of its editor perspectives abd that cutting an pasting may "trigger" some other process to validate it differently but it has made no difference. I have as of today applied the latest toolkit ifix 013 and nothing changes. The line it gets stuck on is not even complex
example:- Set LREF.MessageType = w_msg_type; where LREF is a reference
and yet comment this out and the rest of the code until the return statment and all is fine uncomment this and any others from there on down and it hangs......it is doing my head in  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 26, 2008 3:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I was thinking that there was some weird stuff in the project that was doing things to the ESQL file somehow - that it was still being built as a v5 file instead of a v6 file and this was causing your problems. That was why I suggested what I did.
Your best bet is to open a PMR. The other thing to do is try renaming the .esql file as a .txt and seeing what it looks like that way....
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| MrSmith |
| Posted: Fri Mar 28, 2008 5:54 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
OK
Am going to raise PMR people cos have found the cause of promblem and its basically this:
Declare LREF Reference to OutputLocalEnvironment;
For some reason the statement is wrong - can't see why and there is no special keyword LREF cos i checked as far as possible so presume it justa compiler issue against the OuputLocalEnvironment cos when you just replace with full path instead of reference works a treat......
guess there may be a ifix014  |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 28, 2008 5:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MrSmith wrote: |
| guess there may be a ifix014 |
It is inevitable. Maybe called that, maybe called something else, but there's always at least one more piece of maintenance, now and forever.
I hope the one which contains a fix for your problem arrives swiftly. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
