Compile Error logs not found on AS400

gerd_renz3

VIP Member
Hi List,
I build a full package and the CDBASE.sts file accused a compilation error for B9800200. I could not find any log to find out the reason for the compile failure.
I deployed the otherwise fine full package and build an update packge with the missing BSFN. Again there was an error in CDBASE.sts, but no logs were found. The same BSFN compiled without errors on the client side.
I am used from Unix or Windows servers to have a CompileError directory. I understand that on the AS there is a library with the packages´ name which is supposed to contain a log file. I my case, this logfile is empty.
This may all be due to my lack of AS400 knowledge.
Please advise, I am willing (and still able) to learn.

Thanks, Gerd
ERP8, AS400, SP22
 
Gerd...

Not sure I'm understanding correctly, but I believe what you are after on
the 400 is found in the IFS system. You can use the iSeries Navigator
for the "fun Windows Explorer" look and feel, or utilize the WRKLNK
command on the 400.

You can also find the actual compile errors in the member named FAILED in
the library on the 400 that is named after your package. You can utilize
PDM to look at that member and it will actually show you the code and
where ever there is a compile issue, it will list it in the body of the
code. There will also be a summary at the bottom of the file. I believe
in many cases, the compile errors you'll find have to do with header
files (the .H's on the deployment server side) not being found on the
400, and yes, there's a include file on the 400 as well.

I belive you should start by looking at the FAILED member if you see one
in the library. Isn't the 400 fun??!!?? Better get used to it, as
PeopleSoft begins converging the code from the two packages, I believe
you're going to get to see more and more iSeries use!!

Regards and good luck,
Jim

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
 
Gerd,

Look for a file named FAILURE, it will have a member containing the compile listing for each BSFN that had a compile error. The file is in the package library.

Tom Davidson
 
Back
Top