All Platforms
- Non-CASS option to turn off
DPV
,LACSLink
,SuiteLink
, andRDI
processing for an individual record. If theper record
option is selected, CASS mode (3553) is turned off . - This is implemented through a SKIPxxx option in the AddressData structure (PBFNADRS) – SkipDPV, SKIPLACSLink, SkipSuiteLink and SkipRDI.
Windows
- Finalist USPS ZIP files will no longer be self extracting (.exe) files. They will be standard ZIP files like all other Finalist databases.
- The HELP files for Lookup.exe and WorkBench.exe will be URLs on the Precisely website.
- Visual Basic 6 examples have been removed.
z/OS (mainframe)
Removed COBOL helper routines from 64-bit load library.
Database
- A new database layout introduced for the 10.0 release. This database is available immediately.
- 10.0 is not backward compatible with prior releases.
- 9.x release databases are not forward compatible.
- Starting May 2023, databases from previous versions, namely 9.x, will no longer
be distributed; they will still be usable through July 2023. For the mainframe
environmentNote: Database will be valid in CASS mode for 3 months after May 2023. It can continue in non-CASS mode indefinitely without DPV, LACSLink, etc, and will not reflect current data.
Z4Select Discontinued
The Z4Select product option is no longer supported. All its references have been removed.
Process LOT Only option discontinued
The Process LOT Only option has been discontinued with this release.
Support for multiple license keys
Finalist now supports multiple license keys if more than 6 CPU ID's need to be represented.
Each key will support up to 6 CPU ID's, but you can specify up to 3 keys for a total of 24 CPU ID's.
In the Windows and Linux/UNIX environments, a single key can be passed in via the PBFNSetupDef structure or PBFN.CFG. Additional keys can be specified with the presence of a keyfile.txt, pbfnkey2.txt or pbfnkey3.txt file in the current directory.
For the mainframe environment, a single key can be passed in via the PBFNSetupDef structure or PBFNCFG. Additional keys can be specified with the presence of a load module named PBFNKEYF, PBFNKEY2, or PBFNKEY3. See the sample JCL: KEYSTORE.
Delivery Point Validation (DPV)
Finalist now returns a flag if DPV was used to resolve multiple address candidates.
A new field PBFN-RRTN-ADSDPVTIEBREAK
has been introduced. This
field will indicate if DPV tie break logic was used to match this address.
Return Parsed Input fields
Finalist has always returned the components of the parsed output address. Finalist
10.0 adds the return of the input address components as they were parsed by
Finalist. These new fields will be automatically returned as part of the
ReturnAddressDataDef
(PBFNRRTN) structure.