Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.
You are not logged in.
Pages: 1
I am using batch files to sync the apps and build. However, after switching to PowerGen 6, PowerGen will GPF after the syncronization is complete and the build starts. If I manually run the build it runs fine.
Here are the batch commands:
@echo off
Echo Verifing Source Control Checked In
cd "I:\Powerbuilder\Utils"
wo.exe I:\projects\WebApp\SourceControl
cd "C:\Program Files\E. Crane Computing\PowerGen Professional"
Echo Running Synchronization
copy "i:\projects\webapp\SourceControl\webapp\*.pbg" "c:\pbapps\webapp\"
Start /Wait pwrgn8 /K=c:\pbapps\webapp\webapp.gen /pbg /nrp
If Exist c:\pbapps\webapp\webapp.ERR Goto ERROR
If Exist c:\pbapps\pbapps.ERR Goto ERROR
Echo No Errors Found
Echo Running Build Process
Start /Wait PwrGn8 /A=c:\pbapps\webapp\webapp.gen
If Exist c:\pbapps\webapp\webapp.ERR Goto ERROR
If Exist c:\pbapps\pbapps.ERR Goto ERROR
Echo No Errors Found
Goto FINISH
:ERROR
Echo Error Building WebApp
Start notepad "c:\pbapps\webapp\powergen.log"
pause
Goto END
:FINISH
xcopy c:\pbapps\webapp\*.pbd I:\Testing\webapp\Current
xcopy c:\pbapps\webapp\webapp.exe I:\Testing\webapp\Current
:END
I'll test a batch file similar to yours and get back to you later today
I ran a batch similar to yours and did not see the problem. I suspect something subtley different between your interactive run and your batch run. Are you running the batch from a different User account then the interactive run?
Regards,
Phil
I'm using the same user account for both.
This is the same batch process that I used on 5.5 and the app configs are untouched. It worked fine then.
I am going to try reinstalling powergen and see if that works.
Reinstallation didn't fix it.
I found that even though PowerGen was generating an err file with a GPF code it was not actually encountering a fault. I adjusted the batch file to grep the err file and ignore a GPF error code. With this work around it is back working again.
One point of clarification... PowerGen will create an error log file (with the GPF code) at the start of an operation. That way, if there is a GPF, the existence of the log file will be left as an indication of that. When the operation completes, the error file is either removed, if there were no errors, or rewritten with a different error code.
It sounds like you script was checking for the error file existence before the PowerGen operation completed?
Regards,
Phil
Is this a new addition. As stated before, this very batch file had no problems with the previous version.
As shown in the first post the batch file starts powergen twice in sequence. It looks like the batch file catches the existence of the precreated "GPF error" file of the first instance before it is removed. The batch file should be waiting until the program instance is released before it continues to the next line. If so, the error file is not being destroyed early enough.
Just my two cents. As stated already, I have a work around (though not optimal) so this not preventing my work anymore. Thank you for your help.
PS. Your quick reply option for the forumn is returning a bad gateway error.
The error handling has always operated this way. Are you sure the Start/Wait operation is working the way you expect? If it suspends the script until PowerGen is done you should never see the error file.
Regards,
Phil
Pages: 1