These steps describe the sequence of Finalist EWS processing.
- During processing of your input file, Finalist identifies an address that is not an exact match to the current ZIP + 4 file.
- Finalist compares the address to the EWS File.
- If Finalist finds the inexact address on the EWS File, per CASS regulations, Finalist fails the address and does not update the address until the USPS adds the valid address to the ZIP + 4 File.
- The number of failed EWS addresses displays on the Finalist Batch Report and the USPS Form 3553 (CASS Summary Report).
-
On the z/OS platform, there are two methods available for working with EWS — the CBEWS file and the PBFNEWS module.
- CBEWS
- CBEWS is a VSAM file that contains all of the EWS records from the USPS. It should be populated when the USPS releases EWS data (unless you always populate the PBFNEWS module, see below).
- PBFNEWS
- PBFNEWS is a module that may or may not contain the same EWS records from
the USPS. The default configuration shipped with Finalist has no EWS records
in the PBFNEWS module. If you run the LOADEWS JCL (in FNSOURCE), LOADEWS
populates the PBFNEWS module.
- If PBFNEWS is NOT populated when Finalist runs, Finalist reads CBEWS and stores the data internally.
- If PBFNEWS is populated when Finalist runs, Finalist does not need to read the CBEWS file. This method saves time and I/O counts, especially critical in an online (CICS or IMS) environment.
- If you are ALWAYS going to populate the PBFNEWS module (LOADEWS), you do not need to load the data into CBEWS. Also, in this case, the CBEWS DD does not need to be part of your JCL stream. NOTE: This method will provide the best performance of EWS processing.
- If you do not want to run LOADEWS, then you must load data into the CBEWS file.