To define your DPV processing options, follow these steps:
-
From the Mode drop down list, select a value to indicate whether Finalist performs DPV processing and the DPV mode to use for processing your file.
- OFF — Do not perform Delivery Point Validation (DPV) processing.
- ON — Perform Delivery Point Validation (DPV) processing with the DPV Full database (dpvh.db).
- MEM — Perform Delivery Point Validation (DPV) processing with the DPV Full database (dpvh.db) fully in memory for improved performance. You will need a minimum of 650MB of RAM/Memory if you choose this option. MEM is converted to ON with a buffersize (cDPVBufSize) of H (huge).
- SPL — Perform Delivery Point Validation (DPV) processing using the DPV Split database (dpvs.db). Split File processing separates the DPV Data File into 100 smaller files based on the first two digits of the ZIP Code. The Split File segment associated with the first two digits of the ZIP Code is loaded into memory. If you sort your mailing file by ZIP Code, you can bring the relevant portion of the DPV file into memory. This process reduces the number of I/O requests that normally occurs when you use the full DPV Data File. Use this option if your file is sorted by ZIP Code. This is the optimal solution for Finalist customers having at least 100MB, but no more than 650MB, of RAM/Memory.
- FLT — Perform Delivery Point Validation (DPV) processing with the DPV Flat database (dpv.db). Use the DPV Flat File for improved batch performance. This file is in excess of 2.3GB and not dependent on RAM/Memory capacity. Input files should be sorted by ZIP Code. This is an optimal solution if you have less than 100MB of RAM/Memory available.
- Blank — Defaults to OFF.
-
The USPS allows DPV processing to be used as a tie
breaker for matching inexact street records. If only one of the records in a tie is
delivery point validated, a match is allowed to the inexact record. When processing
results in an inexact match due to the input address directional, DPV processing can
be used as a tie breaker if only one of the records is found to be delivery point
validated and the delivery point validated record does not violate the cardinal
direction rule. To perform DPV Tie Breaker processing, click Tie Break. Defaults to
ON.
Note: The default is ON; however, the default value only applies when DPV Mode is defined as ON, MEM, SPL, or FLT.Note: The USPS CASS regulations require DPV Tie Break processing to generate the USPS Form 3553 (USPS CASS Summary Report).
-
From the Shutdown Indicator drop down list, select a value to specify the action to take during batch processing when a False Positive (Seed) record is encountered.
- WARNING — Continue batch processing when a False Positive (Seed) violation record is encountered. Finalist displays a warning message indicating a violation occurred. Finalist processing continues but DPV processing is disabled.
If a DPV False Positive (Seed) violation is encountered and WARNING is set, CASS processing is turned off.
CASS processing is turned off for any jobs submitted after the DPV False Positive (Seed) violation was encountered. Any jobs submitted after the DPV False Positive (Seed) violation, fail with an initialization error.
For the job that encountered the False Positive (Seed) violation, the CASS statement will be provided showing the number of records that were DPV confirmed up until the point of the False Positive (Seed) violation. No records will be DPV confirmed after the False Positive (Seed) violation occurred.
Any jobs submitted before the False Positive (Seed) violation was encountered run to completion, including DPV processing for each file. This occurs even if the jobs do not complete processing until after the time the DPV False Positive (Seed) violation was found in the job that first encountered the False Positive (Seed) violation.
- SHUTDOWN — Stop batch processing when a False Positive (Seed) violation record is encountered. Finalist does not process subsequent records and automatically exits the program.
The Shutdown Indicator applies to batch processing only. If your DPV key is NCOA or "No-Stop", this option is ignored.
- WARNING — Continue batch processing when a False Positive (Seed) violation record is encountered. Finalist displays a warning message indicating a violation occurred. Finalist processing continues but DPV processing is disabled.
-
From the Buffer Size drop down list, select a value to indicate the memory model for DPV processing:
- Pico — Pico. Stores no data in memory. No tables or indexes are loaded.
- Ultra — Ultra-small. Stores no data in memory. Partial indexes are loaded.
- Small — Small
- Medium — Medium
- Large — Large
- Huge — Huge. Stores all data in memory.
- Blank — Defaults to Medium.