TITLE LINE/MENU BAR ..................................................................................................................... 5 WINDOW NAVIGATION ..................................................................................................................... 6
DATA ENTRY BLOCK ...................................................................................................................... 24 LIST NAVIGATION .......................................................................................................................... 25 CHANGING EXISTING ADDRESS RECORD ......................................................................................... 25 CORRECTING NON-CERTIFIED ADDRESS RECORDS (TUTORIAL) ........................................................ 25 DELETING ADDRESSES FROM THE LIST ........................................................................................... 26 ADDING ADDRESSES TO THE LIST (TUTORIAL) ................................................................................. 26 MAIL*STAR LIST RECORD ............................................................................................................ 29 STATUS LINE ................................................................................................................................ 30 INITIAL CASS CERTIFICATION........................................................................................................ 30 APPLYING USPS AMS-II UPDATES ............................................................................................... 30 RE-CERTIFYING ADDRESSES ......................................................................................................... 30
FIELD OVERLAYS .......................................................................................................................... 31 IMPORTANT NOTE ABOUT INPUT AND USER FIRM/RECIPIENT NAME OVERLAYS ............................. 31 GENERAL RULES .......................................................................................................................... 32 EXPORTING (INPUT) FIELDS ......................................................................................................... 32 FIXED-FIELD FORMAT ................................................................................................................... 32 DELIMITED-FIELD FORMAT ............................................................................................................ 32 SETTING DELIMITED-FIELD DELIMITER AND TEXT QUALIFIER ............................................................. 32 MSG: ........................................................................................................................................... 32 LOAD FILE DEFINITION: DROP DOWN LIST BOX ................................................................................. 33 INSERT FIELD ICON ....................................................................................................................... 33 DATA WINDOW INITIALIZATION ....................................................................................................... 33 SELECTING A ROW ........................................................................................................................ 33 DELETE FIELD ROW ICON .............................................................................................................. 33 SAMPLE FILE DEFINITION USING OVERLAYS AND COMPONENT FIELDS ............................................... 34 CHECK DEFINITION ICON ............................................................................................................... 35 DISKETTE ICON............................................................................................................................. 36
CASS™, Coding Accuracy Support System, address validation is the process of normalizing addresses to USPS® Publication 28 standards validating against current USPS data. All address elements are verified adding ZIP Code™, ZIP+4™, carrier route and delivery point details.
AES is USPS CASS Certified™ for ZIP+4, carrier route, 5-digit Zip Code, LACSLink®, SuiteLink™, eLOT®, DPV® and RDI™ for Linux and Windows operating systems. AES is a non-exclusive NCOALink® Limited Service Provider Licensee, RDI Licensee, LACSLink Licensee, SuiteLink Licensee and DPV Licensee of the United States Postal Service®.
USPS® Registrations: DPV®, DMM®, eLOT®, First-Class Mail®, LACSLink®, NCOALink®, Standard Mail®, The Postal Service®, U.S. Postal Service®, United States Post Office®, United States Postal Service®, USPS®.
USPS® Trademarks: CASS™, CASS Certified™, Certified Mail™, First-Class™, PAVE™, P.O. Box™, POSTNET™, Post Office™, Postal Service™, RDI™, RIBBS™, SuiteLink™, ZIP™, ZIP Code™, ZIP+4™.
This list is not exhaustive of the trademarks belonging to The Postal Service®.
Address Management Software Mail*LIST is “Multiple Document Interface”, (MDI), application allowing multiple open sheets of information on the application desktop. There are three application sheet types including “Mail*LIST”, “File definitions” and “Selection criteria”. Mail*LIST in conjunction with the USPS CASS certified product Mail*STAR, manages and maintains CASS certified and DPV validated address lists. Mail*LIST provides the ability to:
• Connect to projects • Change passwords • Grant and revoke access to users for projects • Create new projects • Import lists from files into projects and export lists from projects to files • Certify address lists • Add/Delete addresses from address lists • Create USPS Form 3553 and PAVE USPS Qualification Reports • Print envelopes and create address labels • Create import/export and create selection criteria file definitions
Starting Mail*LIST From the Windows <START> button, “Programs �AES�Mail*LIST ” starts the program and presents a desktop with the MDI sheet “Mail*LIST” open.
Desktop This is a window with title line, menu bar and a work area where multiple MDI sheets can be opened and viewed at the same time.
Title line/Menu bar The title line identifies the Mail*LIST desktop. The envelope icon just before the title opens a menu, which allows the desktop to be restored, moved, resized and closed. The title line ends with three icons for minimizing, maximizing and closing the desktop.
The menu bar items include “File”, “Window” and “Help”.
File The “File” menu item drops down to provide another menu of options.
File�New The “File�New” menu item drops down providing a menu of the three types of MDI sheets, “Mail*LIST”, “File definitions” and “Selection criteria”. Each of these sheets is described in detail later in this document.
File�Close This item closes the current MDI sheet. The current sheet has a blue title line when using the “Windows Standard” appearance setting. To check the current setting:
“Start�Settings �Control Panel �Display ”
File�PrintSetup… This item provides access to printers and their configuration. From this option, you can change printer defaults or change the settings of an installed printer.
File�Exit The item closes the “Mail*LIST” application.
Window The “Window” menu item drops down to provide another menu of options that control desktop MDI sheet layout.
Window�Tile Vertical Changes the size of MDI sheets that are not minimized and arranges them side by side without overlap. The command tiles both horizontally and vertically when more than three MDI sheets occupy the desktop.
Window�Tile Horizontal This item is similar to “Tile Vertical” except the arrangement is from top to bottom. The command tiles both horizontally and vertically when more than three MDI sheets occupy the desktop.
Window�Layer Changes the size of MDI sheets that are not minimized to fill the desktop area and places them one on top the other.
Window�Cascade Changes the size of MDI sheets that are not minimized and layers them so that you can see the title lines of all the sheets.
Window Navigation Mail*LIST maintains a list of open sheets in either the “File” or “Window” drop down menus. If Mail*List’s main MDI sheet is active, the list of open sheets appears in the “File” menu, otherwise the list appears in the “Window” menu. The active sheet is checked. You can <click> the sheet or its menu item to make it the active sheet.
MDI Sheet This is the only sheet that can be opened before connecting to a project. For that reason, it is opened when the application starts. This sheet includes a message line and a tab control. Unlike the other MDI sheets, Mail*LIST can only have one instance. It can be closed and reopened, but any attempt to open more than one Mail*LIST instance is ignored.
Msg: The message line provides hints and other information messages. If the message is an error, it appears in red; otherwise, the text is black.
Project instance: MySQL myprj instance is read from the configuration file, config.svc. An alternate project service can be used by changing the project specification.
Tab object There are six tabs available for “projects”, “lists”, “cass”, “3553”, “pave” and “labels”. Until connected to a project, the “projects” tab is the only tab available. Until selecting an address list from the “lists” tab, tabs that operate on lists are not available. The “projects” tab takes on the name of the selected project. The “lists” tab takes on the name of the selected list.
Project tab Before connecting to a project, the “project security” block and “project description” window are the only visible controls.
MSDBA When installed, the only account is “MSDBA” with initial password “CHANGE”. The master DBA account is the only account that can create projects or grant access to the system.
Connecting to a project The first field contains the hostname or IP of the server providing access to the myprj instance followed by a colon, “:”, and port number. The default port is usually 7502.
Connect to a project by supplying the user-ID in the “User” field and password in the “Pswd” field and <click> the project you want to access. When connected, a message appears in the message field and the “change password” block appears.1
Changing passwords Any user can change their own password by typing the new password in the field marked “New” and verifying it by typing the new password again into the field marked “Verify”.
1“MSDBA” can change the name of a project by holding <F2> down and clicking on the project to be renamed.
Granting/Revoking access The “MSDBA” account can grant and revoke user access to the current project and reset passwords system wide. Change user access by selecting any action and typing the ID.
• “Grant access” – grants access to the current project only. A password is not assigned. If the user account already exists, the password is unchanged. A newly created user logs on with no password until it is changed or reset.
• “Reset password” - reset the user’s password to “CHANGE” for all projects. • “Revoke access” – remove access to the current project only.
(“MSDBA” account cannot be revoked).
Account names ending with “DBA” are granted ALL privilege for the current project. ALL privilege is required to import, export and delete lists. Other accounts are user accounts. User accounts have access to address lists belonging to the project and can select and update address data, but cannot delete, import or export lists.
Project level access: “Grant access” or “Revoke access” will affect the account name found in the field labeled “User” on the connected project only. “Reset password” effects login to all projects the user has been granted access to.
Creating projects
The “MSDBA” can create projects. Once the project name is entered, a “GO” icon appears. <Click> on the “GO” icon creates an empty project.
List tab Address lists are imported, exported and selected from this tab. The tab has an import/export block and a window of address lists. Only users with DBA privilege are allowed to import and export lists. Users without DBA privilege only have access to the window of address lists.
Import/Export block Importing address list files into Mail*LIST tables and exporting them back into files is controlled by this block. The fields and drop down list box’s precise meanings depends on the operation. All operations require file definitions that determine how address list data is imported into and exported out of project address lists.
Operation drop down list box There are two principal operations, “Import List” and “Export List”.
Special operations “Add To List” is similar to “Import List”, appending addresses to existing address list.
“Export Plus” is similar to “Export List”, exporting address based on selection criteria.2
“Import PAVE”, allows import of ZIP code and optionally carrier route data for creation of PAVE reports. The lists attribute, AMS version, is set to “PAVE” and only the “PAVE” tab is available to such lists.
2Export writes addresses in the same order in which they where imported. Export Plus will export addresses in mail presort preparation order if the criteria file specifies "PAVE Current Auto-List" > ‘’.
List name Mail*LIST requires address lists to be named for identification. If the operation is “Import List” you must type the name that will be used to identify the list. Form 3553 reports the list name. CASS allows a maximum of 25 characters for the list names.
If the operation is “Export List” you are required to <click> on an existing list in the address list data window.
Start The first row(s) of address list files may not be an address but a header. The field defaults to one. It is settable so that import can start from any row in the file. Sampling of files is possible by entering a fractional value. If you wanted a sample of only one address in seven you would enter “1/7” which would import record 7, 14, 21, etc. until the end of the file or the record specified in the field labeled “Stop”.
Stop The default value is “9999999”. Import can be stopped before the end of the address list file by setting this number to the last row to be imported.
Format definition file drop down list box The list box provides a list of file definitions. <Right-click> resets the drop down list box. File definitions are covered in detail in the section “File definition painter” later in this document.
MLIST_NATURAL The item is a built-in file definition of Mail*LIST’s natural format. “Export List” using “MLIST_NATURAL” exports all address attributes except “(USER) User Defined Field” which can then be imported to any Mail*LIST project.
Format definition annotation {“fixed-field”, “delim ited-field”} The static text above the drop down list box changes when a file definition has been selected reporting the detected format of the selected file definition.
Delimited-field control response window Delimited field records are interpreted and written based on the parameters, field delimiter and text qualifier. These parameters are initialized at startup from the “config.svc” configuration file. For details, refer to:
File definitions painter �File definitions �Delimited-Field format
A window has been provided allowing delimited-field control changes without stopping Mail*LIST. <Right-click> on the text above the file definition list box opens the following window. Delimited-field controls can be changed for the session from here.
To make the change effective for future sessions, <click> the button “set ini” which changes the “config.svc” configuration file. To restore session parameters to the values in the “config.svc” configuration file, <click> the button “get ini”.
File name For “Import”, the file must exist. Use the “Look in” drop down list box to set the path to the file. <Click> the file to import and <click> “Open” to continue or “Cancel” to abort.
For “Export”, the file does not have to exist. After selecting the path, the filename is typed in the “File name” field. The user is warned if the specified file exists.
“GO” icon When the “GO” icon appears Mail*LIST is ready to import or export with a <click> of the icon. Referring to the import/export block from the section above, the block reads:
Operation “Import List” List name “New Member List” First row “1” Last row “9999999” (read until end-of-file) Format description “New_Member_List.MSD” (comma delimited) File name “C:\AES\dat\AES_CD_Sample.dat”
<Click> the “GO” icon to start the import.
“STOP” icon The “STOP” icon replaces the “GO” icon anytime the user gives up control to a batch process so that it can be interrupted with a <right-Click> on the icon.
“Erase” icon When an address list has been selected by <click> of the list’s row, the erase icon appears which allows you to delete the list from the project database.
Dropping an address list is permanent. Before dropping lists, Mail*LIST requires confirmation. Default is, “No”. The user must select “Yes” for the list to be dropped.
List data window A row for each address list in the project appears in the data window. Once a list has been imported, it must be CASS certified before CASS statistics are set. The list imported for this sample was CASS certified before this snapshot was taken. <Right-click> on the data window refreshes the list’s statistics after certification.
Columns set by import specification
• Name – list name specified in import/export block • First: -- first file record imported • Count: -- number of records in the list • Impdate – day and year imported
Columns set by CASS certification
• AMS – version of USPS AMS-II • Coded – number of addresses certified with ZIP+4 barcodes (DPV valid) • HExact and RExact – the number of high-rise and rural route records that were
certified using non-default ZIP+4 ranges. • HDef and RDef – the number of records that were certified using ZIP+4 default
records. Refer to the Mail*STAR documentation for details about ZIP+4 default ranges.
• SLK – the number of addresses SuiteLINK enhanced • RDI – the number of addresses determined to be households • EWS – the number of addresses that were not certified because of the USPS Early
Address lists are passed to Mail*STAR using this tab. The “Select criteria” drop down list box and the “Criteria detail” field determine which addresses in the list are passed to Mail*STAR.
The three blocks below the “GO” icon are standard query language, SQL, controlling the list. The “select * from”, “where” and “order by” clauses determine which addresses Mail*STAR is given and in what order. Users do not need to edit these clauses. The “select * from” clause is set up by the list tab. The “where” clause is set by the controls of this tab. The “order by” clause is set for Mail*STAR depending on the purpose.
Select criteria All selection criteria options except “Every address” require “Criteria detail”. The first four options support using special SQL wildcards, {“%”, “_”}, in the “Criteria detail” field.
Address status Address status codes are assigned to addresses in the address list. Addresses status codes can have up to 16 characters. Refer to Mail*STAR.pdf, Appendix A for details.
When selecting “Address status” as the “Select criteria”, the “Criteria detail” object is a drop down list box listing all address status groups and the number of addresses per group. Mail*STAR is passed all addresses in an “Address status” group by selecting one of the address codes in the drop down list box and a <click> of the “GO” icon.
The drop-down-list-box reports the status of addresses for the selected list. There are 3,505 DPV valid addresses with status “****”. There are 502 addresses that are DPV valid with secondary numbers either missing or invalid with status of “***”. The 77 addresses with status “PNE” have name clues that were not matched in the city/Zip context, etc.3
Choosing the status of “PNE” and a <click> on the “GO” icon, passes these 125 addresses to Mail*STAR for interactive investigation.
3Refer to the Mail*STAR user guide - appendix A for a complete list of standard address status codes assigned during batch address certification.
Selection criteria file The Selection criteria painter, documented in a later section, allows the DBA to define complex selection criteria and save it in files. If you choose the criteria, “Selection criteria file”, criteria detail is a drop down list box of selection criteria files.
OEL Sequenced The criteria option is unique in that it is not used for address investigation, but for review of mail pieces included in a presort mailing plan in mail piece sequence order.
This can be helpful when filling sacks and trays following the PAVE tab qualification report.
Mail*STAR is synchronized to any line of the qualification report by entering the running total into the Mail*STAR counter. Mail*STAR displays sortation details on the last line.
0048006 00170-007-0008 (00144-007-07) OEL=***** ALL FOR AADC 493
Sortation details are divided into four groups as follows:
First group
Sequence number – where the mail piece is found in the overall sortation plan
Second group
Sack/tray number – sack or tray number the piece is found in Package id – package number in the tray or sack the piece is found in Package number – where the mail piece is found in the package
Third group
Group id – sequence number of the sortation group Sub-group – sequence number of the sub-group in the sortation group Group-level – code indicating USPS sort level
The USPS requires that a USPS Form 3553 be available to qualify for automated mail rates.
Processor’s name (required) The name of the processor is required and will be printed on the USPS Form 3553.
“GO” icon Before printing, the USPS form 3553 is prepared with a <click> of this icon.
“Printer” icon <Click> of this icon starts printing. <Right-click> of this icon allows for printer setup where you can choose and configure the printer.
Zoom block Since the report cannot fit into this window in its normal size, you can zoom in as well as use the scroll bars to see the entire report page.
The USPS requires a qualification report be submitted to qualify for automated mail rates. There are four objects that affect the results of the qualification report for the selected list.
Mail class drop down list box There are eight mail classes supported by Mail*LIST.
Cards check-box (First-Class Mail only) Only First-Class mail has a special rate for cards. Card rate is used to calculate and report postage due when this check-box is checked.
ECR check-box (Standard and Periodical Mail only) Carrier route sortation is turned on using this check-box. Postage may be saved sorting to the carrier route. If unsure, try this both ways and decide based on the postage due. Periodicals require a current Zone Chart for the Entry Point Zip. See Configuration.pdf .
Per Tray and Ozs. Letter and FCM Flats require number of pieces per tray. For letter trays this number is for the 2-foot tray. All mail classes require weight in ounces per mail piece.
Optional selection criteria (see Selection criteria painter) Mail*LIST permits the use of “Selection criteria” when selecting a subset of the list to mail. When a selection criteria file is used, the USPS qualification report only includes mail pieces meeting the selection criteria. This value can be reset with a <right-click>.
This sample report is the result of selecting “First-Class Mail – Automation letters and Cards” and the list is filtered by “Optional selection criteria” named “US_OCENIC_STATES.MSC”.
Rates “5B”,“3B”,“AB”,“MB” — ECR “HD”,“CR” USPS postage rates for automated mail are based on mail class and one of the standard rate codes. Totals for each rate on the postage summary determine total postage due.
Icons
“Pwiz”: <Click> of this icon opens the window that report the PS_3600R or PS_3602R Postage Summary.
“Labels”: <Click> of this icon opens the window that prints bar-coded tray or sack labels.
“Printer”: <Click> of this icon starts printing. <Right-click> of this icon allows for printer setup where you can choose and configure the printer.
“GO”: Before printing, a report is generated with a <click> of this icon. The report is based on all the other controls documented in this tab.
Mail*LIST prints labels or envelopes using address information from the selected list. Certified and non-certified addresses are printed separately. If printing fails for any reason, there is a restart feature that allows for recovery skipping the addresses already printed.
Zoom The zoom control allows you to zoom in or out to any value from 1-200%. The three radio buttons allow zoom control with a single <click>.
“GO” icon Before printing, a report is generated with a <click> of this icon. The report is based on all the other controls documented in this tab.
“Printer” icon <Click> of this icon starts printing. <Right-click> of this icon allows for printer setup where you can choose and configure the printer.
Barcode status block Complete mail list preparation control is provided by “USPS certified, “Not certified”, “Other criteria”, “Restart” and print order.
USPS certified radio button Only address with status of “****”or “***” will be printed. Address are printed in tray/sack sequence order ascending or descending depending on the checkbox setting shown here as “Print descending”. Print descending prints the first trayed mail-piece first. <Click> check box toggles “Print ascending” reversing the print order.
If printing stops for any reason, correct the problem and refer to PrintRestart.pdf.
Not certified radio button All addresses not certified will be printed. Print ascending/descending controls print order by row-id, which is the order in which they were imported.
Not certified restart is based on the Mail*STAR record number. To find the record number of the last address printed run Mail*STAR from the CASS tab selecting the last address label’s recipient.
Note: If print descending, the right record number will be printed first and restart should be the last record number printed - 1. If print ascending, the left record number will be the first printed and restart should be the last record number printed + 1.
Other criteria radio button “Selection criteria” files can be used to filter address labels. A selection criterion does not necessarily include a constraint regarding certified or not certified so the restart button must be checked. It will toggle between “Not-coded”, “Certified” and “Must set” where “Must set” is a clue to the user that one of the other two options has to be used. Restart controls and print ascending/descending work the same as they do for “USPS certified” and “Not certified”.
Three-state OEL check box – Optional Endorsement Li ne
No OEL Prints addresses without OEL.
OEL Prints addresses with OEL.
OEL/TABS
Prints addresses with OEL with a tray or sack separator.
Adjust landscape if necessary and select label The object actually contains two controls. Selection of labels is via the drop down list box. If after configuring the printer the orientation is incorrect, this button allows orientation to be corrected manually.
Address labels are defined in the configuration file “mllab.ini”. Refer to the section “Label definition” in the “Configuration” document or online help.
Mail*STAR annex When Mail*STAR is called by Mail*LIST, there are features available that are not required for address at a time “Point-of-Sale” address certification. This annex documents additional functionality for address list data maintenance.
The reader should be familiar with Mail*STAR documentation as a prerequisite. The example used is the result of CASS tab where the “Select criteria” is “Address status” and “Criteria detail” = “PNE”. This is the list of uncertified addresses where the primary name clue was not found.
Additional features allow: • Change of certified address solutions using Mail*STAR address matching • Add and delete address records from the selected address list • Display address record attributes
Data entry block Two counters appear in this extension reporting the current address of number of addresses. This example is the result of having selected address list criteria of “Address status” = “PNE”. Referring back to that section, there are 125 addresses in the address list with the status “PNE”.
List navigation <CTRL><up-arrow> or <CTRL><down-arrow> move up or down in the list. Entering an address number in the current address field allows random address access. <CTRL><SHIFT><up-arrow> or <CTRL><SHIFT><down-arrow> moves up or down the list automatically certifying the address.
Changing existing address record Mail*STAR permits investigation and resolution of non-certified addresses, as well as apply address changes in the case of a change of address.
If an address change is required, the address change can be made either by: • <Click> “paint” and paint the address and then <click> “accept” • Enter address in the “Data entry” block, <click> “certify” and <click> “accept”
Correcting non-certified address records (tutorial) After import and initial address certification, Mail*LIST and Mail*STAR can increase the percentage of certified addresses by investigating addresses that were not certified in batch. In this example, we chose to look at address status “PNE”.
Investigate the address using the Address Painter. Once resolved, <click> on “accept” sets the certified address attributes and changes the address status to MATCHED, “****”.
Deleting addresses from the list There are customers that use Mail*LIST to manage address lists and need to add and delete address records. <CTRL><ALT><KeyPadMinus> deletes the current address record from the list. For additional security, the user is asked to verify that an address should be deleted.
Adding addresses to the list (tutorial) <CTRL><ALT><KeyPadPlus> adds an address to the list. The two address counters in the “Data entry” block are updated and the new address becomes the last address in the list.
Given the following, this example shows how to add and initialize new addresses in the list. • Input address of – “1804 UNION 101, TACOMA WA” • Client key of – “6785-65-1111” • Attn: line of – “CSW Radio” • First name of – “Sue B.” • Last name of – “Stone”
Setting the address Enter the address in the “Data entry” block and <click> “certify”. The results show 2 candidates. Navigation within the “USPS CASS” block is by <up-arrow>, <down-arrow>.
In this sample, the tie is broken selecting the address with DPV confirmation. The address candidates in the “CASS block” are selected by using <up-arrow> and <down-arrow>. The button with the red check, “accept”, sets both the CASS certified and raw address attributes.
Note: After adding an address record, all address record attributes are reset except “Flags” and “Status” which have the initial value, “ADDRESS REQUIRED”. Minimal requirements are:
• A certified or non-certified address which will appear on the address label • Name(s) if not a recipient address, name(s) must be set • Unique client key or account number should be set, if the record is to be exported from
Set remaining non-address attributes Non-address attributes are editable. Editable fields in the “Mail*STAR List Record” block have blue backgrounds. <Right-click> the field you need to edit opens an edit window for the value.
<Right-click> “Client Key” opens the following window. <Click> on the “X” in the upper right hand corner of the window or <ESC> closes the window and sets the attribute.
<Right-click> and set the first three lines of the “Attn, First, Last & CASS firm” block within the “Mail*STAR List Record” block in the same way as “Client Key”.
Mail*STAR List Record All address list attributes are displayed in this block. Importing address lists as specified by the import file definition initializes all attributes. Export files are created using these attributes directed by an export file definition. Details about import/export file definitions are found in this document under “File definition painter” and “Field types”.
Write protected fields: Gray background fields cannot be edited protecting initial INPUT address values and CASS certified results. Input address fields cannot be altered after import. CASS certified fields can be only be changed by the Mail*STAR CASS certification. Data in any of these fields can be copied into the clipboard with a <click> on the field.
Editable fields: Blue background fields are editable non-address attributes. “Status”, “PMB” (private mailbox), “Client key”, “User flags”, and all three-name fields are editable. <Right-click> the field you want to edit. A window will open identifying the field and its contents. Edit the contents and <click> the “X” or hit the <ESC> key to set the value.
Field - Mail*LIST Record: This is the original record number of the imported file. When adding an address manually, it is the next available number.
Field - Type: This is a one character attribute indicating one of seven address types reckoned by Mail*STAR. Types include “G” (general delivery), “H” (high-rise), “M” (military/embassy), “P” (PO BOX), “R” (Rural Route), “S” (street) and “F” (firm). File definitions that include “(CASS) Address Type” reference this attribute.
Field - Status: The integer value to the right of the “Status” is the DPV validation code. It is not editable. <Click> on the value will open a message box displaying the standardized CASS DPV flag values and footnotes. The integer DPV code is explained in detail in the DPV documentation.
The blue background field below “Status” is the current address status. Although this is an editable field, users cannot assign reserved CASS certified status codes “*”, “**” “***” or “****”. File definitions that include “(CASS) Error Code” reference this attribute.
Note: Production of labels and envelopes distinguishes between certified and non-certified addresses. Only addresses having the status “***” or “****” are considered certified when producing bar-coded mailing labels. All others are considered non-certified.
Field - PMB: This is an editable non-address attribute. Companies that offer private mailbox services use PMB to identify the recipient’s mailbox. PMB numbers are detected and set by Mail*STAR during import. File definitions that include “(USER) PMB number” reference this attribute.
Field - Client key: This is an editable field primarily because Mail*STAR, when invoked by Mail*LIST, has the ability to add addresses to an address list. File definitions that include “(USER) Client Address Key” reference this attribute.
Block - General address lines: File definitions that include “(INPUT) Address Line One” through “(INPUT) Address Line Four” reference these attributes.
Block – Input composite urbanization, building, del ivery, last lines: File definitions that include “(INPUT) Urbanization”, “(INPUT) Building Name”, “(INPUT) Delivery Line” or “(INPUT) Last Line” reference these attributes.
Block – Input delivery components STR, PNO, UTY, SN O: File definitions that include delivery line components “(INPUT) Street Name “, “(INPUT) Street Number”, “(INPUT) Unit Type” or “(INPUT) Unit Number” reference these attributes.
Block – Input last line components CTY, STC, ZP5: File definitions that include “(INPUT) City Name”, “(INPUT) State Code” or “(INPUT) ZIP-code” reference these attributes.
Field - Flags: This is an editable field and contains “(USER) flags”. Refer to user flags for a description of how the field is formatted. Internal Mail*STAR address quality flags are displayed right justified to the right of “Flags”. Address quality flags are listed and described in detail in the Mail*STAR document appendix B and online help.
Note: CASS requires that Mail*STAR maintain “LACS” and ZIP+4 default record indicators, address quality flags “L” and “D” respectively. File definitions that include “(CASS) LACS Indicator” or “(CASS) Default Flag” reference this attribute.
Block - Attn, First, Last & CASS firm: The recipient name and first and last names are editable fields. File definitions that include “(USER) Firm/Recipient Name”, “(USER) First Name”, “(USER) Last Name” or “(CASS) Firm Name” reference these attributes.
Block - CASS composite urbanization, building, deli very and last lines: File definitions that include “(CASS) Urbanization”, “(CASS) Building Name”, “(CASS) Delivery Line” or “(CASS) Last Line” reference these attributes.
Block - CASS delivery components STR, PNO, UTY, SNO : File definitions that include “(CASS) Street Name “, “(CASS) Street Number”, “(CASS) Unit Type” or “(CASS) Unit Number” reference these attributes.
Block - CASS CTY, STC, ZP5, ZP4, DP, Chk, CRIS, eLO T County: File definitions that include “(CASS) City Name”, “(CASS) State Code”, “(CASS) ZIP-code”, “(CASS) ZIP+4 Add On”, “(CASS) Cris”, “(CASS) Delivery Point”, “(CASS) DPBC Check Digit”, “(CASS) LOT Asc/Desc”, (CASS) LOT Sequence” and “(CASS) County Code” reference these attributes.
Status line Below the “Mail*STAR List Record” block is a status line reporting CASS statistics that will be reported on the USPS form 3553.
Initial CASS certification When an address list is passed to Mail*STAR for the first time after it has been imported, the only operation allowed is CASS certification of the entire address list. Mail*STAR will issue a message that allows the user to certify the list, (YES) or exit (NO).
Applying USPS AMS-II updates AES provides monthly USPS updates. When Mail*STAR is given an address list that is not at the latest USPS revision, the user is given the chance to synchronize the list (YES), or (NO) to cancel.
Re-certifying addresses <Right-Click> on the GO icon certifies the addresses in batch.
File definition painter Open the painter from the Mail*LIST desktop File�New�File definitions. Opening the painter requires a connection to a project with DBA privilege. Multiple file definition painters can be open.
When working on a file definition you either start by opening an existing file definition using the drop down list box labeled “Load file definition” or <click> on the insert record icon.
Field overlays A field overlay occurs in fixed and delimited field formats when more than one field-type is specified for the same location. Generally, fields cannot be overlaid. There are a few important exceptions where overlays are supported.
(INPUT)/(CASS) Export overlay (INPUT)/(CASS) export overlays allow export of address information into a common set of fields regardless of certification status. If the address is certified, the overlaid field will contain the (CASS) value. Otherwise, the field will contain the (INPUT) value.
(CASS) fields can always be overlaid by their equivalent (INPUT) fields. Equivalent (INPUT)/(CASS) fields have the same address attribute name. “(INPUT) ZIP-code” is equivalent to “(CASS) ZIP-code”.
Four (CASS) fields including “Urbanization”, “Building Name”, “Delivery Line” and “Last Line”; are considered composite fields. These fields can be overlaid by the general address line fields; “(INPUT) Address Line One” through “(INPUT) Address Line Four”.
(IMPORT)/(CASS) overlays permit one and only one (INPUT) field per (CASS) field.
(CASS) Urbanization/(CASS) Building overlay “CASS Urbanization” and “CASS Building” can be overlaid allowing a third address line to report USPS building names in the absence of USPS urbanization references.
(CASS) Firm Name/(USER) Firm/Recipient Name overlay “CASS Firm Name” and “(USER) Firm/Recipient Name” can be overlaid allowing detection and correction of firm names.
Important note about INPUT and USER Firm/Recipient Name overlays CASS field-types can only appear in the definition once. All INPUT field-types plus the (USER) Firm/Recipient Name can appear twice, once intended for import and again as an overlay. If the INPUT field appears only once as an overlay, import initializes the field using the overlay specification. If the INPUT field appears by itself and a 2nd time as an overlay, import initializes the field using the specification that is not overlaid.
General rules • Most field-types cannot be referenced more than once with the exception of:
o (USER) Flags and User defined in support of multiple non-addresses flag attributes o All (INPUT) and (USER) Firm/Recipient Name supporting (INPUT)/(CASS) overlays
• Mixing composite “(INPUT) Delivery Line” or “(INPUT) Last Line” with (INPUT) delivery line or last line components causes a warning. The input composite fields override input component fields during address matching.
Exporting (INPUT) fields Care must be taken to insure the (INPUT) fields specified for export were part of the import specification4. Input fields that were not referenced by the import file definition will be blank.
Fixed-Field format Every field in a fixed-field record begins at the same place and has the same length in every record. Fixed field record lengths must be declared in the definition. Fixed-field rules include: • Offsets must be positive non-zero integers. • Lengths must be positive non-zero integers. • Comment is required but only serves as documentation. • State code length must be 2. • ZIP-code length must be 5, 9 or 10. • Fields cannot overlap unless they are field overlays. • Field overlays must have the same offset and length. • The last field definition entry must be an “END Fixed-field Record”. The offset attribute is the
record length and its length must be 1.
Delimited-Field format Delimited-field files have a delimiter between fields. The delimiter can be any single printable character or <TAB>. Delimited files can also have a text qualifier that allows the delimiter to appear within the text without it being interpreted as a delimiter.
Delimited-field rules include: • Offsets must be positive non-zero integers reflecting column number. • Lengths must be zero. • Comment is required but only serves as documentation. • Fields must be consecutive starting with 1 and not implicitly skipping fields. • Skipped field must be explicitly declared using “SKIP Delimited-Field” • The delimiter and text qualifier cannot be the same character. • The text qualifier can also appear in the sting if it is duplicated. If the text qualifier is a single
quote, the value cannot be ‘BOB’S’ but instead ‘BOB’’S’.
Setting delimited-field delimiter and text qualifie r Field delimiter and text qualifiers are usually set using the “Delimited-field control” available from the import/export block after selecting a delimited-field file definition. For details, refer to the list tab section under the topic “Delimited-field control response window”.
Parameters used to determine field separation in delimited-field files is set during startup using the following section from the “config.svc” configuration file. “Delimiter” must be one and only one printable character or tab. The “Text_qualifier” can be NULL (no character at all), or one character. <TAB> is a common delimiter. It is set by “DELIMETER=<TAB>” in “config.svc”.
Msg: Information and error messages are displayed in this field.
4 A snapshot of the import definition is stored with the address lists so that Mail*LIST can issue
warnings when attempting to export fields that were not specified during import.
Load file definition: drop down list box Selecting a file definition loads the data window with field specifications included in the file. Setting of a new field description disallows loading file definitions avoiding loss the new fields.
Insert field icon New field rows are inserted with a <click> of this icon. When a row is complete or <right-click> on the data window, the user is given the chance to set the row. Only one unset row is allowed at a time. Setting of an inserted field description disallows loading file definitions to avoid loosing the new field definition.
Data window initialization Once the data window has been initialized, three other icons appear. The data window is initialized when it has at least one row either by loading an existing file definition or setting an added row.
Selecting a row <Click> on a row in the data window, highlights and selects the row.
Delete field row icon <Click> on this icon to delete the selected field definition.
Sample file definition using overlays and component fields The example below is a delimited-field file definition where the column number shown under column heading “Off” is a positive non-zero integer. Delimited-field “Len” is always zero. In contrast, fixed-field definitions always have a positive non-zero field offset and length.
Overlays exist where more than one field-type occupies the same field. If the overlay is an INPUT/CASS overlay, the exported field depends on the address’s CASS status. If not CASS certified, the INPUT value is exported, otherwise the CASS value is exported.
USPS addresses have delivery and last lines. Puerto Rico requires a third urbanization line. Mail*LIST supports definition of composite address lines, address component fields or any combination. Address databases might have a single last line address attribute or component fields for city, state and ZIP-code or as the example below demonstrates, one field for city/state and a second field for ZIP/ZIP+4.
Note: In contrast to the example below, “INPUT General Address Lines” are frequently the best way to describe input data because input lines may not always have the same meaning.
1: Client key is imported and exported using the 1st column of each delimited-field record. 2: Column 2 shows a firm name overlay. The “attn to” line will be initialized during import using
the 2nd column of each address record. During export the imported “attn to” attribute will be replaced (overlaid) when a CASS certified firm name if present.
3: Column 3 shows an urbanization/firm overlay. Import initializes Puerto Rico urbanization with the 3rd column. If the exported address is not certified, the input value will be used. If CASS certified and present, the CASS urbanization will be exported. If there is no urbanization but a CASS building name is present, the building name will be exported.
4-7: The example models a database where the delivery line is stored as components. Import initializes the delivery line components as defined. During export the input values will be used if the address is not certified, otherwise the CASS certified value is used.
8: The example models a single CITY/STATE field implied by the absence of a state field. 9: This is an implied 9-digit CASS ZIP code implied by the absence of an implicit ZIP+4 field.
Check definition icon File definitions are checked automatically when being saving. <Click> of the red check mark icon will check the definition at any time. If errors are detected, they are reported in the message line. If the definition is valid, a summary report of the file definition will be displayed in a message box. The following message box is the result of the previous definition.
Delimited-field field_count=(9) Reports file definition type fixed-field, delimited-field and the number of columns.
+--+ Overlays +--+ Summarizes overlays discussed in the previous section.
+--+ Address Lines (Import/Export) +--+ Summarizes fields used for import �� export by USPS address lines in reverse order.
+--+ Suitable for Import +--+ +--+ Suitable for Export +--+ It is common to have separate import and export file definitions where the import definition is not suitable for export and vice versa. The example used is suitable for both import and export.
Summary: User(2) Input(7) CASS(9) DPV(0) LACS(0) Summarizes the number of fields by category. All address and non-address field-types are described later in this document in detail organized by field-type, USER, INPUT, CASS, DPV and LACS.
Diskette icon File definitions can be added or deleted using this icon. The user is asked what is to be done with the current file definition.
If the “Yes” button is selected the user specifies the file name or <click> an existing file. WARNING: The screen allows changing file path and extension. Do not change file path or extension If either one is changed, the file will not be seen by Mail*LIST as a file definition. The file extension must be “MSD” and saved in the home subdirectory “cfg”.
If the user selects an existing file, Mail*LIST requires user verification before it is saved.
Selection criteria painter Open the painter from the Mail*LIST desktop File�New�Selection criteria. Opening the painter requires a connection to a project with DBA privilege. Multiple selection criteria painters can be open. Selection criteria can be used to filter address lists in conjunction with:
• Exporting addresses using the “Export Plus” operation in the “LIST tab” • Passing addresses to Mail*STAR in the “CASS tab” • Creating USPS qualification reports in the “PAVE tab” • Printing labels and envelopes in the “Labels tab”
The example demonstrates just a few SQL operators; “IN” for lists, “BETWEEN” for ranges and “OR” logical inclusion. The example also demonstrates syntax shortcuts you are allowed for values where the painter will complete some of the details like necessary parenthesis and quotes automatically.
This criteria created here will include all U.S. states on the Pacific listing state codes and all ZIP Codes on the East Coast using a range. Selection criteria can be very complex and include user defined fields, input data and CASS results.
Begin by adding selection criterion for U.S. Pacific state codes. <Click> the first icon, insert criterion, and select the field type “CASS State Code”.
Since there are five U.S. states touching the Pacific, we will use SQL operator “IN” supporting lists.
The painter supplies some the syntax for you automatically, but commas are required. In this example typing “CA, OR, WA, AK, HI” will be corrected to “('CA','OR','WA','AK','HI')” adding the parenthesis and single quotes.
Adding logical operator “OR” followed by “CASS Zip Code” criterion with the “BETWEEN” operator allows us to enter a range of ZIP codes roughly covering East Coast states. Note that SQL “BETWEEN” requires “AND” instead of comma.
We want to check syntax validity before we save the criteria to a file using the red check icon.
Note the arrow points to the “Msg:” field reporting “Criteria is ok.” and therefore ready to be saved.
Read carefully the following SQL details; operators, precedence and the complete tutorial help for the criteria painter. Mail*LIST selection criteria is standard SQL made easier as the tool presents easy to understand field names translating them into actual column names for you.
Always test the criteria before using it in production. “AND”, “OR” precedence can be misunderstood where “AND” takes precedence. Use parenthesis, “(” and “)”, when in doubt. Look carefully at…
• CITY='PORTLAND' OR CITY='EUGENE' AND STATE='OR' -- includes 'PORTLAND MAINE' • (CITY='PORTLAND' OR CITY='EUGENE') AND STATE='OR' – only 'PORTLAND OREGON'
Why? The 1st says ‘PORTLAND’ anywhere while ‘EUGENE’ limited to ‘OR’. The 2nd limits both cities to ‘OR’. Remember, “AND” takes precedence over ‘OR’. Parenthesis grouping both cities corrects this limiting the cities group to STATE='OR'. When in doubt, use parenthesis and always test the specification.
General rules • Selection criterion must be separated by logical operators {AND, OR} • Standard SQL precedence applies, so when in doubt or default precedence does not meet
the logical requirement, group. Precedence order: 1. Group “()” 2. IN, LIKE, BETWEEN 3. NOT 4. =, >, <, <=, >=, <> 5. AND, OR
• If wildcards {%, _} are used, use relational operators {LIKE, NOT LIKE} • BETWEEN and NOT BETWEEN are inclusive with syntax:
“field_type BETWEEN low AND high” • IN and NOT IN argument syntax is:
“field_type IN (arg1, arg2, argn)”
Msg: Information and error messages are displayed in this field.
Load selection criteria: drop down list box Selecting a selection criteria file loads the window with criterion specified in the file. Setting or inserting new criterion disallows loading selection criteria avoiding loss of new specifications.
Insert row icon New criteria is inserted with a <click> of this icon. When a row is complete or a <right-click> of the data window, the user is given the chance to set the row. Only one unset row is allowed at a time.
Data window initialization Once the data window has been initialized, three other icons appear. The data window is initialized when it has at least one row either by opening an existing selection criteria file or setting a new row.
Selecting a row <Click> on a row in the data window, highlights and selects the row.
Delete criterion icon This item deletes the selected criterion.
Check criteria icon Selection criterion is checked prior to saving. The criteria can be checked at any time with a <click> of the red check mark icon. If errors are detected, they are reported in the message line. Fix the error and check the criteria again.
Diskette icon Selection criteria files can be added or deleted using this icon. The user is asked what is to be done with the selection criteria file.
If the “Yes” button is selected the user specifies the file name or <click> an existing file.
WARNING: The screen allows changing file path and extension. Do not change file path or extension If either one is changed, the file will not be seen by Mail*LIST as a selection criteria file. The file extension must be “MSC” and saved in the home subdirectory “cfg”.
Data window Each row defines Mail*LIST field-type criterion, a logical operator, {AND, OR} or parenthesis group operator, {(, )}.
#: This column orders the rows. If the order needs to be changed, change this value.
Field-type or logical drop down list box Field-type, logical operators {AND, OR} or grouping operators {(,)} are selected from the list box. This sample shows the logical and grouping operators at the end of the drop down list box’s list.
Operator drop down list box Field criterion requires a relational operator. The list of operators includes all the ones visible plus {=, <, >, <=} which are the first four in the list box.
Value The value argument depends on the field-type and relational operator. Reasonable values are values that are within the domain of the field-type. Since the domain for ZIP-code is five digit numbers “00000” – “99999”, reasonable values for “INPUT ZIP-code” are “00901”, “00985”, etc.
Precise operators {=, <, >, <=, >=, <>}: = Is equal to INPUT ZIP-code = “00901” < Is less than INPUT ZIP-code < “00901” > Is greater than INPUT ZIP-code > “00901” <= Less than or equal to INPUT ZIP-code <= “00901” >= Greater than or equal to INPUT ZIP-code >= “00901” <> Is not equal to INPUT ZIP-code <> “00901”
LIKE and NOT LIKE operators Use “LIKE” to search for values that match a predetermined pattern. Use “NOT LIKE” to search for strings that do not match a predetermined pattern. When you use “LIKE” or “NOT LIKE”, you can use special characters to match unknown characters in a pattern: • % (percent) Matches any group of characters
“009%” matches all ZIP-codes that begin with “009” (“00900” – “00999”) • _ (underscore) Matches any single character
“00_01” matches the ZIP-codes “00601”, “00701, “00801”, “00901”
BETWEEN and NOT BETWEEN operators Use “BETWEEN” to check if a value is within a range of values. Use “NOT BETWEEN” to check if a value is not in a range of values. The range of values includes the boundary values that specify the range. For example, “INPUT ZIP-code BETWEEN “00901” AND “00999”” would be the same as “INPUT ZIP-code LIKE “009%””.
IN and NOT IN operators Use “IN” to check if a value is in a set of values. Use “NOT IN” to check if a value is not in a set of values. For example ZIP codes on the beach in “SAN JUAN” would be “INPUT ZIP-code IN (“00901”,”00907”,”00913”)”.
Entering values It is not necessary to include single quotes or parenthesis when entering values. Mail*LIST will add those when validating. Mail*LIST validation is limited to syntax and does not check if the value is reasonable or within the logical domain of the field-type. A value of “SAN JUAN” will be accepted for “INPUT ZIP-code”. If a validation error occurs, Mail*LIST will issue a warning explaining the error and replace the value with the symbol “?”. The dropped value is saved in the clipboard so that <CTRL>V will restore it.
Criterion using “(USER) Flags” “(USER) Flags” use the internal Mail*LIST table column “msg”. If there is one and only one “(USER) Flag”, the value is stored literally. If multiple Mail*LIST “(USER) Flags” are imported the flags and their values are stored:
“<“ + flag_name + “=“ + flag_value + “>“ The comment column in file definition names the flag. If multiple “(USER) Flags” share the column, the selection criterion must use the relational operators “LIKE” or “NOT LIKE” and the values must include wildcards.
The file definition used throughout the document defined eight “(USER) Flags”, “f4”, “f5”, “f7”, “f9”, “f12”, “f13”, “f15” and “f20”. The import data limited the domain for each of these flags to {“N”,”Y”}. The criterion for flag “f4” with a value of “N” would be [“(USER) Flags” like “%< f4=N>%”].
Field-types for Selection Criteria and File definit ions Mail*LIST field-types are used when defining import/export file definitions and user selection criteria. Mail*LIST groups field-types into the following categories:
� “USER” – non-address attributes � “INPUT” – input address data � “CASS” – certified address data � “DPV” – USPS standardized DPV flags and footnotes � “LACS” – LACSLINK flags and footnotes � “PAVE” – Attributes generated by mail presort
(USER) non-address attributes Non-address attributes are not used to certify addresses. They may appear on address labels, be used for creating list subsets and database update keys. � (USER) Client Address Key � (USER) Firm/Recipient Name � (USER) First Name � (USER) Last Name � (USER) PMB number � (USER) Flags � (USER) User Defined Field
Client Address Key This can be an account or social security number. It can be any code that uniquely identifies an address. This key is essential in updating address database records with Mail*STAR certified addresses. It can be used by Mail*LIST to find an address.
Name fields There are three name fields. If your data has only one name, you should identify it as “Firm/Recipient Name”. If you have a single name field and a firm/attention field, you should identify the name using “First Name” and the firm name using “Firm/Recipient Name”. If there is a first and last name field, you should use “First Name” and “Last Name” so they will be printed on the same line. The Mail*LIST feature that prints labels or envelopes places the “First Name” and “Last Name” before the “Firm/Recipient Name”.
CASS requires detection and correction of swapped delivery and attention to lines. Detection and correction is limited to “(USER) Firm/Recipient Name” and the first input address line.
PMB – private mailbox Mail*LIST allows you to import and export this number. If addresses are printed, the PMB will appear as required by the USPS. Mail*STAR allows you to change, add or remove this number.
User Flags and User defined fields Mail*LIST allows you to import and export “User Flags” and “User Defined Fields”. The user may have non-address attributes that can be used to filter mailing lists by using user-defined selection criteria based on their values.
Flags There is an internal field in the address list table where flags and their values are stored. If there is only one “USER Flag”, the value is stored literally, otherwise flags are stored:
“<“ + flag_name + “=“ + flag_value + “>“
Take for example the use of two flags. The flags are “COMMITTEE” with committee membership codes {A, B, C, and D} and “SEX” with codes {M, F}. An address having a female recipient with membership in committees “A” and “D” would have flags stored internally as “<COMMITTEE=AD><SEX=F>”. Storage of these two flags requires 21 characters.
Note: The internal user flag field is limited to 254 characters. It is the site’s responsibility to make sure this field does not exceed 254 characters. Take into consideration the length of flag names, flag values and the number of user flags remembering that the use of multiple user flags requires three addition characters to store each flag as described above. Flag names are determined by the comment name used in the file definition.
User Defined Fields User defined fields are more flexible since the values can be up to 1024 characters and are stored literally in columns named by the flag in a separate table joined to the address list table. The columns may be indexed for performance. User defined fields can be used as criterion, but are not currently included in “Selection criteria” files not the build in file definition “MLIST_NATURAL”.
These columns are stored in an attribute table “ATRBn” that is joined to the “STGIn” table on a common Mail*LIST primary key, “apk”. The “n” is the same list-id number as the “STGIn” file. The column name is the comment used to define the field in the file definition.
User defined fields in selection criteria
Refer to the CASS tab section where the three SQL clauses are accessible. “The “select * from” clause referenced table “stgi1001”.
Consider a case where a “User defined field” was named ”COMMITTEE” by the comment in the file definition file and the data that was to be imported listed the committees the recipient was a member of and one of those committees was “NEW PROJECTS”. A sub-query can be added to the “where” clause that would limit addresses for cass, pave and labels. The sub-query might be written as:
AND apk IN ( SELECT apk FROM atrb1001 WHERE committee like “%NEW PROJECTS%”)
(INPUT) address attributes Raw address components are imported into an address list table using these field-types. � (INPUT) Address Line One � (INPUT) Address Line Two � (INPUT) Address Line Three � (INPUT) Address Line Four � (INPUT) Urbanization � (INPUT) Street Number � (INPUT) Street Name � (INPUT) Unit Type � (INPUT) Unit Number � (INPUT) Delivery Line � (INPUT) City Name � (INPUT) State Code � (INPUT) ZIP-code � (INPUT) Last Line
Input elements used for certification Mail*LIST accommodates a wide range of addressing models. The file definition should emulate the organizations address database model.
If the address database model has one or more fields that contain address elements that have no specific purpose, they are supported using the field definitions “Address Line One” through “Address Line Four”.
If the address model has fields with specific meaning, they should be identified using the field definitions for address composites or components. Composite fields include “Urbanization”, “Delivery Line” and “Last Line”. Delivery line and last line data can be defined as components if necessary emulate the organizations address database model.
For example, it is common that last line data is maintained in separate fields for “City”, “State” and “ZIP-code”. If that were the model, the definition of last line would use the components, “(INPUT) City Name”, “(INPUT) State Code” and “(INPUT) ZIP-code”. If the last line were modeled as one field “City/State/ZIP-code”, the definition of last line would use the composite “(INPUT) Last Line”.
Constructing input address After import, Mail*STAR constructs an input address piecing together the elements specified into a stream of up to four address lines. If there are general address fields specified, “(INPUT) Address Line One” through “(INPUT) Address Line Four”, they are added in that order. If there is an “Urbanization” it is added next. If there is a composite “(INPUT) Delivery Line” or the delivery line is defined by its components “(INPUT) Street Number”, “(INPUT) Street Name”, “(INPUT) Unit Type” and “(INPUT) Unit Number”, it is added next. If there is a composite “(INPUT) Last Line” or the last line is defined by its components “(INPUT) City Name”, “(INPUT) State Code” and “(INPUT) ZIP-code”, it is added last.
Delivery line input definitions Since parsing the delivery line is inexact because it can have urbanization and building elements, it is not attempted during import. Only the composite delivery line is used when certifying addresses. Customer delivery line models may have component fields instead of the delivery line in which case the delivery line can be described using any combination of component field-types.
Composite delivery line definition If you model the delivery line as a single field, you can describe it using the field definition “(INPUT) Delivery Line”.
Components of delivery line definition In the absence of a single delivery line field, any combination of the field definitions “(INPUT) Street Number”, “(INPUT) Street Name”, “(INPUT) Unit Type”, and “(INPUT) Unit Number” can be used. They are appended during import with a space separator to construct the delivery line.
Note: When delivery line components are used, import uses a heuristic that detects PO BOX and rural route addresses so that “(INPUT) Street Number” = ‘1’ and “(INPUT) Street Name” = ‘RR 7’ results in ‘RR 7 BOX 1’ instead of ‘1 RR 7’.
Last line input definitions Mail*LIST attempts to maintain the last line’s components. When specifying a last line composite, Mail*LIST parses it during import so that the address list can be sorted by ZIP code, city and state. Customer last line models can be defined in the following ways. The actions performed are described briefly for each method.
Composite last line definition If the last line is a single field, describe it using the field definition “(INPUT) Last Line”. The last line Components City, State and ZIP code will be parsed during import.
Components of last line definition If last line is modeled as separate fields for city, state and ZIP code, you can describe it using field definitions “(INPUT) City Name”, “(INPUT) State Code” and “(INPUT) ZIP-code”. The last line composite will be constructed during import.
Implied city/state If last line is modeled, as city/state in one field and ZIP code is another field, you can describe it using field definitions “(INPUT) City Name”, and “(INPUT) ZIP-code”. The city field without a state code field implies a city/state composite. The city and state will be parsed from the city field and the last line composite constructed during import.
(CASS) address attributes CASS certified address attributes are separate from input address attributes preserving the input address values. The CASS list includes all input address field-types plus ZIP+4, carrier route, delivery point, check digit, firm name, 12-digit barcode, error code, LACS indicator, default flag, address type, eLOT, county code and address quality flags. � (CASS) Urbanization � (CASS) Street Number � (CASS) Street Name � (CASS) Unit Type � (CASS) Building Name � (CASS) Unit Number � (CASS) Delivery Line � (CASS) Delivery Line (2) � (CASS) City Name � (CASS) State Code � (CASS) ZIP-code � (CASS) ZIP+4 Add On � (CASS) Carrier Route � (CASS) Last Line � (CASS) Delivery Point � (CASS) DPBC Check Digit � (CASS) Firm Name � (CASS) 12 Digit Barcode � (CASS) Error Code � (CASS) LACS Indicator � (CASS) Default Flag � (CASS) Address Type � (CASS) LOT Asc/Desc � (CASS) LOT Sequence � (CASS) EWS Flag � (CASS) County Code � (CASS) RDI � (CASS) SuiteLINK
� (CASS) CASS Flags
Building/Urbanization overlay File definitions can specify that “(CASS) Building Name” and “(CASS) Urbanization” occupy the same field. USPS certified urbanization names override building names. Fortunately, the USPS AMS-II data avoids building references on streets with an urbanization reference. AES recommends use of building names in Puerto Rico for accurate delivery.
Implied City/State If there is only one field in the database model that includes city and state, the file definition should include “(CASS) City Name”. In the absence of “(CASS) State Code” the definition is treated as a composite City/State and both are exported to the since field.
Implied Postal Code If there is only one field for postal-code, the file definition should include “(CASS) ZIP-code”. In the absence of “(CASS) ZIP+4 Add On” the definition is treated as a composite postal-code and both are exported to the same field.
12 Digit Barcode The barcode is not a stored field but is included for convenience and calculated for export.
Error Code The “Error Code” is synonymous with “Address Status” described in detail in Appendix A of MailSTAR.pdf . Matched addresses have one to four asterisks and DPV valid addresses have three or four asterisks. Any other value indicates why the address was not matched.
LACS Indicator The “LACS” indicator is always exported as “L” when the matched Zip+4 record indicates that a LACS conversion attempt should be made. Addresses that have been LACS converted do not have this flag set.
Default Flag The default flag is always exported as “Y” when that attribute applies to the certified address in accordance with USPS CASS and AMS-II data.
Address Type The one character attribute is “G” for GENERAL DELIVERY, “P” for PO BOX, “R” for RURAL ROUTE, “S” for STREET, “H” for HIGH-RISE and ‘F’ for FIRM address.
eLOT Acs/Desc and Sequence The sequence number is a 4 character numeric string. The Asc/Desc flag is one character in the domain {“A”, “D”}.
EWS Flag The EWS flag will appear only if the USPS Early Warning System has been enabled. Addresses that were not CASS certified because of an exact match to an Early Warning System Record and did not have an exact match to a ZIP+4 record will have this flag set.
County code Three-digit USPS county code
RDI Residential Delivery Indicator indicating that the DPV valid address is a household. The domain of the one-character field is {‘Y’, ‘N’}.
Suite LINK
The SuiteLink product improves business addressing by adding known secondary (suite) numbers to allow delivery sequencing where it would otherwise not be possible. The field is three characters wide in the domain {“”, “N00”, “YA”}. A blank response indicates that SuiteLink was not applicable; “N00” indicates no match and “YA” that the address was improved.
Flags The field contains the “AES address resolution block” and “address quality flags”.
Address resolution block The block contains resolution strategy and reliability. The block will always be formatted as “[rss]” where “ss” is the resolution strategy code and “r” reports reliability.
Address reliability flag: This value is “0” – “9” where “0” is the highest reliability and “9” is the lowest.
Address quality flags block Address quality flags are listed and described in detail in Appendix B of MailSTAR.pdf .
File definition field-type, “CASS Flags” will export the composite address quality flag field. The composite address quality flag includes flags for several CASS required discrete indicators:
• “LACS Return Indicator”
• “LACS Footnote”
• “CASS Default Range”
• “CASS SuiteLINK”
• “CASS RDI”
Selection criteria definitions access these values somewhat differently. Address filters used to identify addresses based on address quality flags require using:
The first five flags are one character in length. The last field-type, “DPV Footnotes”, requires a field width that can accommodate multiple two-character footnotes. Currently a maximum of three footnotes is possible. Their domain of values and a detailed explanation of the DPV field-types are found in the DPV documentation or online help.
(LACS LINK) USPS Address Conversion LACS fields are provided in support of USPS Locatable Address Conversion System. • LACS return indicator {Y, N, F}
“Y” = New LACS Converted Address “N” = LACS Attempted But Not Convertible “F” = False-Positive Detected
• LACS footnote {A, 00, 14, 92} “A” – LACS Record Match – The input record matched to a record in the master file. A new
address could be furnished. “00” – No Match – The input record COULD NOT BE matched to a record in the master file. A
new address could not be furnished. “14” – Found LACS Record: New Address Would Not Convert at Run Time – The input
record matched to a record in the master file. The new address could not be converted to a deliverable address.
“92” – LACS Record: Secondary Number Dropped from Input Address – The input record matched to a master file record, but the input address had a secondary number and the master file record did not. The record is a ZIP+4 street level or high-rise match.
(PAVE) USPS The field-type category “PAVE” has been changed in support of mail preparation. The category has five field-types active in “File definition”:
• "PAVE_OEL": Optional Endorsement Line • "PAVE_Presorted-Seq-Number": Master mail-piece sequence number • "PAVE Container-Tray-Group": Sack/Tray number • "PAVE_Group-Package-ID": Bundle/Package number in the tray/sack • "PAVE_Package-Seq-Number": Sequence number in the bundle/package
