Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.
You are not logged in.
Pages: 1
Hi There,
I have a script which used PowerGen and PB9 successfully.
I upgraded to PB10 and PowerGen 6 with the patch from the ftp site as noted in other forum responses and made any necessary adjustments to my GEN and OLF files.
I use PowerGen with "start /wait" from the command line in a script twice.
1. To bootstrap import all the objects to build the required PBLs.
2. Build the PBDs and EXE.
Between these 2 steps, I check to see if the Project Error File exists and if it does, then the script stops and reports that there was a problem.
I believe that the bootstrap import does not remove the project error file on successful completion, since the powergen log file that has been generated reports no errors for the bootstrap import.
I look in the directory where the PBLs have been built and the Project Error File has not been removed.
Is anyone experiencing this problem ?
Thanks.
Chun.
Hi Chun,
I just tried a command-line Bootstrap Import. The operation was successful and the error log file was removed, as expected.
Try specifying a full path to the error log file. Does that make a difference?
Regards,
Phil
Hi Phil,
I opened up the PowerGen GUI and opened the Error File ... menu on the Options menu and looked at the settings that I have for the GEN project.
They were :-
1. "pgerror.log" for the session error file
2. "<full pathname>\PowerGen_Err.log" for the project error file
I performed a command line bootstrap import by using the command syntax
start /wait PwrGn10 /J=MyGenFile.GEN MyOLFFile.OLF
At the beginning of the process, I took a look into the directory where it was being built and saw both the pgerror.log and PowerGen_Err.log files.
At the completion of the bootstrap import, I took a look into the same directory where the error files were located and found that pgerror.log was not there but PowerGen_Err.log was still there.
Any Ideas ?
Regards,
Chun.
Hi Chun,
If you put a path to the session error file, it should be deleted too.
Or, since you have already done that for the project error file, you can just use that in your processing.
Regards,
Phil
Hi Phil,
I think you've misread my reply.
It's the session error file that DOES NOT have a path name and IS DELETED when the bootstrap import finishes.
The Project Error File does not get deleted and it DOES HAVE A FULL PATHNAME.
Chun.
Hi Chun,
I found the problem and am working on a solution. I let you know when we have a version to test.
Thanks for help in identifying this problem!! Sorry it took so long to resolve.
Regards,
Phil
Pages: 1