The Finalist engine (PBFN.dll) automatically creates the Seed Log file. Driver programs are not responsible for creating the Seed Log file. This applies to custom batch drivers calling FINALIST on the mainframe.
- If you perform Finalist processing using the Native or
Compatibility Interface batch mode, Finalist generates
the Seed Log and writes the Seed Log out to an output file
that is defined using the DD SEEDLOG JCL statement on the
Mainframe platform:
//SEEDLOG DD DSN=hlq.SEEDLOG, // DISP=(MOD,CATLG), // DCB=(LRECL=180,BLKSIZE=0,RECFM=FB), // SPACE=(TRK,(1,1),RLSE)
- For Windows and Unix, Finalist generates a "seedlog.txt" file automatically and places it in the /bin directory. The same Seed Log output file is used for both DPV and LACSLink seed violations.
The formats for the Header and Detail records are identical for DPV and LACSLink.