Batch Processing - Finalist - 10.0

These steps describe the sequence if you encounter a seed violation using the batch application.:

1. The function (DPV or LACS^Link) generating the seed violation stops processing.
2. The Finalist job continues to run to completion if the DPV Shutdown Indicator is not set to "S". Otherwise, a seed violation will stop the Finalist job.
3. An error message is written to the log.

4. Finalist generates the USPS Form 3553 (CASS Summary Report) for the job that encountered the False Positive (Seed) violation. It will be reflective of the records that were DPV/LACS^Link processed before the False Positive (Seed) violation.
5. Finalist writes the offending record to the SEEDLOG file. For Mainframe environments, your JCL includes a DD statement for SEEDLOG. The seed violation record is written to the location and filename assigned in this DD statement. For Windows and Unix environments, Finalist creates a "seedlog.txt" file in your /bin directory containing the seed violation.
6. In addition to producing a Seed Log, the output file indicates seeds by:
   1. If a DPV seed violation is encountered, the output file contains a "Y" for the DPV Flags False Positive indicator in position 3 of the three-byte output field oDPVPBSA.
   2. If a LACS^Link seed violation is encountered, the output LACS^Link Seed Detail field oLLKSD is populated with a "Y" The oLLKSD field is not available to be posted out with the Workbench for Windows.
7. The function (DPV or LACS^Link) generating the seed violation cannot process subsequent jobs until a reactivation key is applied. Any CASS job submitted after the False Positive (Seed) violation will encounter an initialization error.