Defining City and State Information - Code-1_Plus - 5.0

CODE-1 Plus Guide for IBM i

Product type
Software
Portfolio
Verify
Product family
Data Quality - Postals
Product
CODE-1 Plus
Version
5.0
Language
English
Product name
CODE-1 Plus
Title
CODE-1 Plus Guide for IBM i
Copyright
2024
First publish date
1998
ft:lastEdition
2024-05-15
ft:lastPublication
2024-05-15T00:03:43.588945

Use the City and State Storage Options screen to define the city and state information to store in your output file. To access the City and State Storage Options screen:

  1. From the Name/Address Record Posting screen, page down to the City and State Storage Options screen (C1CPOD073).

  2. Use the following table to complete the fields on the City and State Storage Options screen.

    Field Name

    Description

    Store City/State if any information is dropped during standardization?

    Optional. Code indicating whether the standardized city/state line should be stored when information was dropped during the standardization process:

    • Y — Store the information anyway.

    • N — Do not store if information was dropped.

    • Blank — Default is Y.

    Max Correctness for storage:

    Address

    Optional. Enter a number from 0-9 to define the maximum acceptable address probability of correctness to store the standardized city/state line. Type a number between 0 and 9, where 0 indicates the best case and 9 indicates the worst case. Default is 9.

    Overall

    Optional. Enter a number from 0-9 to define the maximum acceptable overall probability of correctness to store the standardized city/state line. Type a number between 0 and 9, where 0 indicates the best case and 9 indicates the worst case. Default is 9.

    Store default City if City not matched

    Optional. Code indicating what should be stored when no city name match was found:

    • Y — Store the default city name.

    • N — Store the information indicated in the "What should be stored if a City/State is not matched or is not stored due to storage options above?" field.

    • Blank — Default is Y.

    Store if multiple ZIP + 4 matches are found?

    Optional. Code indicating whether the standardized city/state line should be stored when multiple ZIP + 4 matches were found:

    • Y — Store the standardized city/state line anyway.

    • N — Do not store the standardized city/state. Instead,    store the information indicated in the "What should be stored if a City/State is not matched or is not stored due to storage options above?" field.

    • Blank — Default is N.

    Store if multiple ZIP Code matches are found?

    Optional. Code indicating whether the standardized city/state line should be stored when multiple ZIP Code matches were found:

    • Y — Store the standardized city/state line anyway.

    • N — Do not store the standardized city/state line. Instead,    store the information indicated in the "What should be stored if a City/State is not matched or is not stored due to storage options above?" field.

    • Blank — Default is N.

    What should be stored if a City/State is not matched or is not stored due to storage options above?

    Optional. Code indicating what should be stored in cases where the standardized city/state line was not stored, either because no match was found or due to storage conditions:

    • B — Store blanks; removes any old information in the output city and state field. Ensures you will be able to detect when a record did not receive a city and state.

    • X — Store nothing.

    • Blank — Default is B.