What to Expect with Finalist v9.0.0

Finalist 9.0.0What’s New

Edward DanleyPrincipal Software [email protected]

2

Finalist 9.0.0

BetaWe would like to thank those who participated in our Beta program for the 9.0.0 release.

If you would like to participate in future Beta’s for Finalist, please send an email to [email protected].

3

USPS/CASS DatabasesFor Finalist 9.0.0 re-certifications, the USPS requires that Cycle N DB’s be used. The Cycle N DB’s are based on data from about 6 years ago and do not include modern options like the DPV/PBSA table or PO BOX Zone data. When testing and/or re-certifying with Cycle N DB’s, the PO BOX Zone and DPV/PBSA features will not return any results because the data didn’t exist at that time. Re-certification does not test optional (Cycle O) features. Using optional features does not impact certification. This is both normal and acceptable.However, Cycle N DB’s were updated to the new Finalist 9.0.0 format. Therefore you must use the 9.0.0 versions of the Cycle N DB’s when you re-certify.All FNL 9.0.0 monthly DB’s include all of the modern features like PO BOX Zone data, DPV/PBSA data and the larger RDI file sizes.What does this mean? It simply means that testing with modern DB’s will produce different results when compared with the static Cycle N DB.

4

Finalist 9.0.0

Big release for FinalistCASS Cycle O on and offCASS Cycle O features are options at this time (default to not being on where it could impact coding)CASS Cycle N is still the CASS requirement• Cycle O basically went away

5

Finalist 9.0.0

Big release for FinalistCASS Cycle N is still the CASS requirement• However we’ve chosen to only support

Finalist 9.0.0 for CASS support going forward• Finalist 8.3 is still supported, just not in

CASS mode– No 8.3 CASS extension keys will be issued

More on CASS specifics later

6

Finalist 9.0.0

Big release for FinalistNew eLOT database format• Same performance but about 50% smaller

footprint than before

7

Finalist 9.0.0

Big release for FinalistNew Finalist ZIP4 database• Not backwards compatible

– Can’t use Finalist 9.0.0 DB with Finalist 8.x• Old database not forward compatible

– Can’t use 8.0 DB with Finalist 9.0.0

8

Finalist 9.0.0

Big release for FinalistNew API structures (parameters)• AddressDataDef (PBFNADRS) – New• SetupDataDef (PBFNGCFG) – Highly Modified• Simplify calling PBFNInit() and

PBFNProcess()– Multi-release deprecated

• Introduced with this release• Next release will be flagged as deprecated• Next release after than the old structures will

no longer be supported

9

Finalist 9.0.0

Big release for FinalistNew COBOL API’s using Standard Linkage• No more PGMNAME(LONGMIXED),DLL• Still call PBFNInit(), PBFNProcess(),

PBFNTerminate() (and others) in your COBOL program

• Existing programs do not have to change. LONGMIXED is still supported, just no longer required.

10

Finalist 9.0.0

Big release for Finalist• Finalist.exe (PGM=FINALIST, ./finalist)

changes– Now allows an output file to be a different format

than the input file• Lookup.exe (Windows only)

– New AddrScan interface• Windows installation

– Code signed by PB to ensure security

11

Finalist 9.0.0

Big release for Finalist• CICS and IMS panels

– Now consistent between the two– Modernized with current options

• Over 60 changes (including bug fixes) in this release

12

Finalist 9.0.0

Big release for Finalist• Documentation change

– New User Guide• Getting Started Guide• Working With Guide

– Now 3 manuals• Installation Guide (IG)• User Guide (UG)• Developers Reference Guide (DRG)

13

Finalist 9.0.0

Cycle O (the release that wasn’t)Cycle N now supported through July 31, 2016• Is this the last of Cycle N?

– Not sure but probably not– We are taking it 1 year at a time– This means new keys each year until a decision

is made by the USPSIf you are self-certified, when you move to 9.0.0 you need to re-certify• New DB’s

14

Finalist 9.0.0

Cycle O (the release that wasn’t)Finalist 8.1 and 8.2 are still technically Cycle N certified• This does not mean Finalist 8.1 and 8.2 are

still supported by PBFinalist 8.3 is still technically Cycle N certified• PB does not support it in CASS mode• Bugs will be researched but only patched in

9.0.0

15

Finalist 9.0.0

Cycle O (the release that wasn’t)Finalist 8.3 “Not in CASS mode”• Finalist 8.x DB’s only for the next year or so• 8.3 CASS keys expire on 8/1/2015

You MUST upgrade to Finalist 9.0.0 for full support

16

Finalist 9.0.0

Cycle N Optional ChangeR777• The On and Off again feature

– Was first announced days AFTER 8.1.1 was released and was part of Finalist 8.1.2

– Removed in Finalist 8.3.0– Two sides of the USPS didn’t know what the

other was doing• Carrier Route R777 is not street deliverable

address even though a ZIP+4 is returned

17

Finalist 9.0.0

Cycle N Optional ChangeR777• Optional in Finalist 9.0.0• New CFG option

– R777 Deliverable = ON|OFF

• New DPV Footnote– R7

• New 4602 error code if R777=OFF

18

Finalist 9.0.0

R77740 FLETCHER DRPLEASANT HILL TN 38578-3001

This physical address exists in the ZIP4 and DPV databases but isn’t actually deliverable. The sub-division does not receive mail and all mail is actually delivered to a PO BOX not tied through automation to this address.

Why would a customer want R777=OFF?• To keep the delivery counts up on the 3553 report• Validation of physical address• Possible UPS or FedEx type of delivery

Why would a customer want R777=ON?• To flag and keep the best possible USPS mailing information

for their customers

19

Finalist 9.0.0

Cycle N Optional ChangePBSA or Post Office Box Street Address• Semi-quietly introduced January 2013• Competitive with CMRA’s who advertise a street

address• Competitive with CMRA’s who accept FedEx and

UPS deliveries• Not all PO BOX’s have a PBSA• POB’s can’t accept some deliverables• Can’t deliver some items to POB’s

20

Finalist 9.0.0

Cycle N Optional ChangeDPV PBSA Table• New table in DPV

– DPV PBSA Table = ON in CFG– New DPV Footnote of PB (and no it’s not for Pitney

Bowes)

21

Finalist 9.0.0

Cycle N Optional ChangePO Box Only ZIP• New flag to indicate that this ZIP code only contains

PO BOX’s• However we’ve seen that this isn’t 100% true in the

literal sense– PBSA’s can still be present

22

Finalist 9.0.0

Cycle N ChangeFive-Digit Validation• For the 3553 report• The 5-DIGIT CODED value must now ensure

that the ZIP code corresponds to the CITY STATE

• Also a new flag for each record to indicate– PBFN-xxxx-ZIPVALID

• xxxx is HRTN, ZRTN, JRPA, WRPA, ADRS, etc.

23

Finalist 9.0.0

Cycle N Optional ChangeConvert unidentified secondary for a CMRA to PMB• 123 MAIN ST STE 100

– If CMRA, will be changed to 123 MAIN ST PMB 100• 123 MAIN ST # 100

– # stays the same, will not be changed

• 2809 KIRBY RD STE 116 APT 3– 2809 KIRBY RD STE 116 is the CMRA– In this case APT 3 will change to PMB 3– Same rules apply if secondary's are swapped– 2809 KIRBY RD APT 3 STE 116

24

Finalist 9.0.0

Cycle N Optional ChangeConvert unidentified secondary for a CMRA to PMB• Optional with Finalist 9.0.0• In CFG

– Convert Secondary to PMB = ON|OFF

25

Finalist 9.0.0

Calling native API’s from COBOLNo longer need to compile with• PGMNAME(LONGMIXED),DLL

Still call PBFNInit(), PBFNProcess(), PBFNTerminate() in COBOL program• Can be upper or mixed case

LONGMIXED is still fully supported• Existing applications do not need to change

26

Finalist 9.0.0Deprecated/Highly modified structures

New AddressData structure (PBFNADRS/PBFNRRTN)• Includes all PBFNProcess() structures so only one (1)

structure needs to be passed into the PBFNProcess() call– ProcessData/PBFNAPDS, PBFNHRTN, PBFNXPDS, PBFNZRTN– ParsedAdr/PBFNLPDS, PBFNJRPA, PBFNVPDS, PBFNWRPA– AdsInfo/PBFNCADS– LabelLineDef/PBFNKLBL– ErrorDef/PBFNIERR– RtnOrigDataDef/PBFNMRTN– RtnFirmDef/PBFNFRTF– LACSSeedDetDef/PBFNODTL– DPVDetailDef/PBFNUDPH

27


New AddressData structure• COBOL Copybooks = PBFNADRS/PBFNRRTN• Eliminates duplication of fieldnames/data• All fields (parsed and standard) are in one structure• Affects C, COBOL, and BAL programs• For COBOL, generally a global CHANGE ALL of

fieldnames from PBFN-ZRTN-FIRM to PBFN-RRTN-FIRM

• Some AdsInfo field names had to be renamed when merged into AddressData– PBFN-CADS-FIRM to PBFN-ADRS-ADSFIRM

28


New AddressData structure• Mutually exclusive with ProcessData and ParsedAdr

29


Modified SetupDef (PBFNGCFG) structure• Includes all PBFNInit() structures so only one

(1) structure needs to be passed into the PBFNInit() call

• Added two additional structures into SetupDef– ErrorDef/PBFNIERR– InfoDef/PBFNBINF

30


PBFNTerminate() API did not change and still accepts multiple structures

31


Currently drivers must still pass ~10 parameters to PBFNInit() and/or PBFNProcess()• Pass NULL or BY VALUE 0 for remaining 9 parameters

like you do today

32

Finalist 9.0.0

PBFNRtnSuiteLinkStatsDef structureThis structure was documented but was not able to be passed to the PBFNTerminate() APINow available

33

Finalist 9.0.0

PBFNAddressInfoDef (PBFNCADS)A new value (PBFN_PREFERRED_OVERRIDE or x’08’ or +8) was added to the PBFN-CADS-CITY-TYPE field to indicate that the output city name was changed due to a preferred city override condition

34

Finalist 9.0.0

60 DANBURY RDWALLS TOWNSHIP NJ 07753

Codes to:60 DANBURY RDTINTON FALLS NJ 07753-7918

PBFN_PREFERRED_OVERRIDE

35

Finalist 9.0.0

CICS & IMS Screen PanelsFinalist On-Line 9.0.0 (C) 2014 Pitney Bowes Software, Inc.

Option Code: 1 (Valid options listed below) 13:08:55

1-Address Lookup 3-ZIPCODE Information 5-Street Information2-City Information 4-Street Name List 6-Product Information

Exception Table: N (Y/N) ALSLBL : N (Y/N/1/2/3/4/5/6)EWS: N (Y/N) FIRMLBL: D (I/D)RDI: N (Y/N) ASM : N (Y/N)LACSLink: N (Y/N) DUALADR: F (F/A/1/2/P/C)SuiteLink: N (Y/N) CTYLONG: Y (Y/N)SLK Secondary: B (B/S/I/N) R777 Deliverable: Y (Y/N)

DPV: N (Y/N/S/F) Cnvrt Sec to PMB: N (Y/N)NoStat: Y CMRA: Y Tie Break: Y (Y/N)Vacant: Y PBSA: Y (Y/N)

PF1: OPT 1 PF2: OPT 2 PF3: OPT 3 PF4 : OPT 4 PF5 : OPT 5 PF6 : OPT 6PF7: N/A PF8: N/A PF9: RESET PF10: N/A PF11: N/A PF12: EXIT

36

Finalist 9.0.0

Database ChangesNew eLOT database• About 50% smaller with no loss of

performance• New JCL to define and load the VSAM file

(z/OS)

37

Finalist 9.0.0

Database ChangesNew Finalist ZIP+4 filesVersion 9.0.0 DB• 9.0.0 DB cannot be used with Finalist 8.x• 8.0 DB cannot be used with Finalist 9.x

DB uses the same external format so the JCL is the same, but the data inside the DB is different (z/OS)

38

Finalist 9.0.0

Database ChangesBoth DB’s will be produced for a limited term of time• All are encouraged to convert to Finalist 9.0.0

and the 9.0.0 DB’s• Current support policy says current release

plus one back– When next release (9.next?) is released, the 8.0

DB’s will no longer be produced

39

Finalist 9.0.0

Database ChangesBoth DB’s will be produced for a limited term of time• Can continue to use 8.x product with 8.0 DB’s

in non-CASS mode even if the DB’s are expired per CASS regulations (120 days)– Can use May 2016 DB forever in non-CASS

mode– Not current data

40

Finalist 9.0.0

Miscellaneous changesUpdated install JCL (z/OS)Code Signed installation (Windows)All user drivers/applications should be recompiled• Must if you don’t want to see the “VERSION

DEPRECATED” message(s)Documentation changes• Four (4) guides down to three (3)

41

Finalist 9.0.0

Miscellaneous changesBatch Summary Report• New options displayed• New counts

3553• 5-Digit Count rules changes

60+ changes occurred in this release

42

Finalist 9.0.0

Compatibility Interface (CI)No specific changes• For the Init call (‘0’), the new options

(R777, convert secondary unit to PMB) are not specifically available and the CI will take the default values

• If you want to use the new options, you must use FINAL-USE-SETUP-Y option and pass parameters via SetupDef(PBFNGCFG) that is imbedded in FINALIST-CALL-AREA– This is the same process as before

43

Finalist 9.0.0

Compatibility Interface (CI)No specific changes• Lengths have changed for native

structures inside LPFNCL0x so all programs must be re-compiled with latest LPFNCL0x copybook.

44

Finalist 9.0.0

EtceteraStreamWeaver• The currently released StreamWeaver, 6.6.1, will

call 9.0.0, and return all the fields, variables, etc. it returned for 8.3– No implications to jobs other than the deprecation

message when Finalist is called with an older API set

• StreamWeaver 6.6.2 is scheduled for 1Q 2015• StreamWeaver customers may wish to wait until

6.6.2 is released before you implement Finalist 9.0.0 and implement them in parallel to avoid the deprecation messages

45

Finalist 9.0.0

EtceteraVeriMove• VeriMove 3.5.5 is scheduled for 1H 2015 and will

contain Finalist 9.0 as part of its internal CASS processing

• The use of Finalist 9.0 as an external CASS engine can be used immediately

46

Finalist 9.0.0

Release DateScheduled for November 18, 2014Can implement right away (no need to wait for August 2015 for CASS changes)Can implement optional features (what was Cycle O changes) and still remain CASS certifiedIf you were certified on your own, you need to re-certify as Cycle N• Need 9.0.0 version of Finalist and eLOT Cycle N DB• Contact Pitney Bowes

Finalist 9.0.0

Edward DanleyPrincipal Software [email protected]

What to Expect with Finalist v9.0.0

Business

Transcript of What to Expect with Finalist v9.0.0