This migration table maps the CI Process callarea to the Finalist native APIs and structures. The Finalist CI process (4, 5, 6, 7) call is replaced with the Finalist native PBFNProcess call. Because the CI did not accept real parsed data input, all address information would normally be passed using the PBFNAddressData structure. If your address data is in parsed component format (for example, range, pre-directional, street name, suffix), you can use the PBFN-ADRS-PARSED option (described above) to identify parsed data as input to the Finalist native PFBNProcess call.
|
COBOL C Assembler |
Position |
CI Structure/Field/Notes |
|---|---|---|
|
FINAL-FILLER lAnchorPointers $REREGS |
1-12 |
|
|
FINAL-FUNCTION-CODE cFunctionCode[0] FUNCODE |
13 |
|
|
FINAL-REPORT-KEY cakey CAKEY |
77-116 |
PBFN-ADRS-USERKEY PBFNAddressDataDef.cUserKey |
|
USER-INPUT-FIRM-LINE caInputFirm FIRMLN |
143-212 |
PBFN-ADRS-FIRM PBFNAddressDataDef.cFirm |
|
USER-INPUT-URB-LINE caInputUrb URBIN |
213-242 |
PBFN-ADRS-URB PBFNAddressDataDef.cUrb |
|
USER-INPUT-ADDRESS1 caInputAddr1 ADDRLN1 |
243-312 |
PBFN-ADRS-ADDRESS1 PBFNAddressDataDef.cAddress1 Address line, unit, and PMB information can be entered into the address lines. |
|
USER-INPUT-ADDRESS2 caInputAddr2 ADDRLN2 |
313-382 |
PBFN-ADRS-ADDRESS2 PBFNAddressDataDef.cAddress2 |
|
USER-INPUT-CITY-STATE caInputCitySt CTYST |
383-452 |
PBFN-ADRS-CITY PBFNAddressDataDef.cCity Input city, state, and ZIP Code can all be entered into the cCity field. |
|
USER-INPUT-ZIP caInputZip ZIPIN |
453-457 |
PBFN-ADRS-ZIP PBFNAddressDataDef.cZip |
|
USER-INPUT-SEC-SEG caInputSecSeg SECSGIN |
458-461 |
PBFN-ADRS-ZIP4 PBFNAddressDataDef.cZip4 |
|
USER-INPUT-CR caInputCrRte CRRTEIN |
462-466 |
PBFN-ADRS-CRRTE PBFNAddressDataDef.cCrRte |
|
Z4-RESERVED caZ4Reserved Z4RESVD |
606-725 |
No mapping. |
|
FINAL-DPV-OPT caDPV CADPV |
726 |
No mapping in native during Process call. |