null  null
CODE-1 Plus™
Version 4.1.0
User’s Guide
For Linux, Unix, Windows, and z/OS
Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No
part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written
permission of Pitney Bowes, 3001 Summer Street, Stamford CT 06926-0700.
© 2016, Pitney Bowes Software Inc. All rights reserved.
MapInfo, Group 1, and Group 1 Software are trademarks of Pitney Bowes Software Inc. All other marks and trademarks are property of their respective
holders.
Pitney Bowes Inc. holds a non-exclusive license to publish and sell ZIP + 4® databases on optical and magnetic media. The following trademarks are
owned by the United States Postal Service: CASS, CASS Certified, DPV, eLOT, FASTforward, First-Class Mail, Intelligent Mail, LACSLink, NCOALink, PAVE,
PLANET Code, Postal Service, POSTNET, Post Office, RDI, SuiteLink, United States Postal Service, Standard Mail, United States Post Office, USPS, ZIP
Code, and ZIP + 4. This list is not exhaustive of the trademarks belonging to the Postal Service.
Pitney Bowes Inc. is a non-exclusive licensee of USPS® for NCOALink® processing.
Prices for Pitney Bowes Inc. products, options and services are not established, controlled or approved by the USPS® or United States Government. When
utilizing RDI™ data to determine parcel-shipping costs, the business decision on which parcel delivery company to use is not made by the USPS® or United
States Government.
3001 Summer Street
Stamford CT 06926-0700
USA
www.pitneybowes.com
Table of Contents
Chapter 1: CODE-1 Plus Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
What is CODE-1 Plus? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
What is Address Standardization? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
What is the Matching Process? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Understanding the CODE-1 Plus Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
What is CASS Certification? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Certifying Your Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Certified Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Total Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
CODE-1 Plus Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Using the Batch System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
File Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Using the Interactive System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Address Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Database Inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Site Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Other CODE-1 Plus Programs and Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Program Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Program Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Callable Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Executable Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Database Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 2: Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Getting Started After Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Getting Started with Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
What is the CODE-1 Plus Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Copying the IVP Job to Use as a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Modifying the Parameter Files for Your New Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Getting Started with Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
What is the CODE-1 Plus Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Copying the Sample Job to Use as a Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Getting Started with z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
What is the CODE-1 Plus Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Tailoring IVPFILE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Chapter 3: Getting Started With Your Batch Job. . . . . . . . . . . . . . . . . . . . . . . . . . 37
Introduction to Batch Jobs in CODE-1 Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Finding Your Sample Name and Address File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Analyzing the Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Input and Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Name/Address File Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Output Record Posting Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Release 4.1.0
3
User’s Guide - Open Systems
Generated Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Report Headers and Footers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Using The Tutorial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Step 1. Define Your Input and Output Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Step 2. Specify Your Input Name-and-Address Record Layout. . . . . . . . . . . . . . . . . . . 45
Step 3. Define Your Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Step 4. Specify the Reports to Generate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Step 5. Define the Headers and Footers for Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Step 6: Submit the Job for Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Step 7: Read the Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Chapter 4: Getting Started With Interactive Processing. . . . . . . . . . . . . . . . . . . . 65
Getting Started With the Interactive System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Address Matching Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Database Inquiry Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Correcting Uncoded Records Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Navigation Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
CODE-1 Plus Interactive System Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Online Help Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Address Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Scrolling Through the Match Results Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Database Inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Navigating Through the Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Moving to a Line on a Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Displaying Data about a Database Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Querying the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
An Example Work Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Step 1. Accessing the Interactive System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Step 2. Matching an Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Step 3. Querying the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Step 4. Matching an Address—Second Attempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Step 5. Geographic Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Correcting Uncoded Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Interactive Screen Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Command Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Address Matching Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Address Match Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Delivery Sequence Footnotes Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Miscellaneous Information/Base Address Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Expanded Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Geographic Coding Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Match Settings Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Multiple Elements Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Parsed Elements Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Release 4.1.0
4
User’s Guide - Open Systems
Return Codes Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Statistics Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Address Stack Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Database Inquiry Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Apartments at a House Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Cities in a State Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Cities in a ZIP Code Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
City Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Firms in a House Range Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Houses on a Street Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Streets in a City or Streets in a ZIP Code Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Geographic Coding Plus Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Screens that Support Site Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Administration Sign-on Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Interactive Customization Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Database Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Customization File Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
File Backup and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
File Repair, Re-Initialization, and Password Display . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Batch Uncoded Records Interface (G1CPBNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
How it Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
UR COMMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
UW COMMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Program Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Description of Supplied Sample G1CPBNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Chapter 5: Generating CODE-1 Plus Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Understanding the CODE-1 Plus Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Required Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Optional Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Report Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Build Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Address-Match Execution Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Control Totals Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Execution Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Parameter Record Listing Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Analysis of Matched Records Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Build Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Coding by State Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
ZIP + 4 Coding by State Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Carrier Coding by State Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Line of Travel Coding by State Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Coding by List Code Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
ZIP + 4 Coding by List Code Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Carrier Route Coding by List Code Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Line of Travel Coding by List Code Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Release 4.1.0
5
User’s Guide - Open Systems
Coding by 3-Digit ZIP Code Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
ZIP + 4 Coding by 3-Digit ZIP Code Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Carrier Coding by 3-Digit ZIP Code Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Line of Travel Coding by 3-Digit ZIP Code Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Processing Summary Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Delivery Point Validation Processing Summary Report . . . . . . . . . . . . . . . . . . . . . . . 128
Delivery Point Validation Processing by List Code Report . . . . . . . . . . . . . . . . . . . . 128
Residential Delivery File Build Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Residential Delivery File Build Execution Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
National Deliverability Index (NDI) Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
USPS Form 3553 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Chapter 6: Using Z4CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
What is the Z4CHANGE Option? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
The Z4CHANGE Option Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Rules for Using the Z4CHANGE Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Activating the Z4CHANGE Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Using Z4CHANGE Option Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Calling Z4CHANGE From Your Own Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Generating Reports for Z4CHANGE Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
z/OS Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
UNIX Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Chapter 7: Using Delivery Point Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
What is Delivery Point Validation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Resolving Multiple Matches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Using the Delivery Point Validation Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Activating Delivery Point Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Activating DPV in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Activating DPV in Callable Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Understanding DPV Return Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
DPV Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
DPV by List Code Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
DPV Processing Summary Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
DPV Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Expiration of DPV Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Open/Read Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Seed Records and Stop DPV Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Software Incompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
DPV File Load or Location Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
What If My Mailing Generates a Seed Violation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Chapter 8: Using LACSLink. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
What is LACSLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
What are the Benefits of LACSLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Release 4.1.0
6
User’s Guide - Open Systems
Who is Eligible to Use LACSLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
How Does LACSLink Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Using the LACSLink Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
LACSLink Processing Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
How Do I Install the LACSLink Option? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
How Do I Install the LACS Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
How Do I Activate LACSLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Activating LACSLink in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Activating LACSLink in Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Activating LACSLink in Callable Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Understanding LACSLink Return Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
LACSLink Processing Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
LACSLink Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
LACSLink Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
LACSLink Information on USPS Form 3553 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
What If My Mailing Generates a Seed Violation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Chapter 9: Using SuiteLink
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
What is SuiteLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
What are the Benefits of SuiteLink?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Who is Eligible to Use SuiteLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
How Does SuiteLink Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
How do I Install the SuiteLink Option? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
How do I Install the SuiteLink Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
How Do I Activate SuiteLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Activating SuiteLink in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Activating SuiteLink in Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Activating SuiteLink in Callable Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
DD Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
SuiteLink Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Input and Output Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
SuiteLink Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Chapter 10: Using Line of Travel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
What is Line of Travel?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Why Use Line of Travel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Accessing Line of Travel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Getting Started with Line of Travel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Sorting Your LOT Coded Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Calling the LTO10 Subroutine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Input Area — Parameter 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Output Area — Parameter 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
COBOL Calling Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Windows Calling Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Line of Travel Exit Routine (LTO60) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
EXITOP Parameter for the LTO60 Exit Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Line of Travel Exit Routine for Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Release 4.1.0
7
User’s Guide - Open Systems
Line of Travel Exit Routine for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Control Totals Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Alternate Sequence Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Sorting LOT Records Using Alternate Sequence Codes . . . . . . . . . . . . . . . . . . . . . . . 189
Sequence Code Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Chapter 11: Using Residential Delivery Indicator (RDI) . . . . . . . . . . . . . . . . . . . 199
What is Residential Delivery File Processing? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Building the Residential Delivery File in CODE-1 Plus . . . . . . . . . . . . . . . . . . . . . . . . 200
C1DBRDI Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Building Your RDI File in z/OS/IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Building Your RDI File in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Building Your RDI File in Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Activating the RDI Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
DPVIN Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
DPVOUT Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
PGMNAM Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
REPORT Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
RDI Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Chapter 12: Auxiliary File Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
What is the Early Warning System? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Auxiliary File Processing and EWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Building the Auxiliary File with the Early Warning System . . . . . . . . . . . . . . . . . . . . 206
C1AUXBLD Utility Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
AUXIL Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Activating the Auxiliary File/Early Warning System File. . . . . . . . . . . . . . . . . . . . . . . 209
Auxiliary File Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Auxiliary File Build (C1AUXBLD) Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Auxiliary File Build Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Auxiliary File Build Execution Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Auxiliary File Reporting in the CODE-1 Plus Matcher . . . . . . . . . . . . . . . . . . . . . . . . . 210
Chapter 13: Reducing Databases and Creating Media . . . . . . . . . . . . . . . . . . . . 211
Building a Reduced Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Creating a Reduced Database from Delivery Media (Tape) . . . . . . . . . . . . . . . . . . . . 212
Defining Parameters for G1DBLOAD Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
G1DBLOAD Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Input File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Output File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Executing G1DBLOAD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Creating a Reduced Database from Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Defining Parameters for C1PDRDSK Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
C1PDRDSK Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Calling the C1PDR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Input File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Release 4.1.0
8
User’s Guide - Open Systems
Output File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
C1PDR Parameter Call Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Executing C1PDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Performing Database Media Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Defining Parameters for G1DBTAP2 Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
G1DBTAP2 Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Input File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Output File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Executing G1DBTAP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Chapter GL: Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235
Index
Release 4.1.0
9
User’s Guide - Open Systems
Release 4.1.0
10
User’s Guide - Open Systems
CODE-1 Plus Concepts
In this chapter:











What is CODE-1 Plus? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
What is Address Standardization? . . . . . . . . . . . . . . . . . . . . . . . . .12
What is the Matching Process? . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Understanding the CODE-1 Plus Database . . . . . . . . . . . . . . . . . .15
What is CASS Certification? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Total Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
CODE-1 Plus Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Using the Batch System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Using the Interactive System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Other CODE-1 Plus Programs and Modules . . . . . . . . . . . . . . . . .28
Database Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
1
What is CODE-1 Plus?
What is CODE-1 Plus?
CODE-1 Plus is an address-matching and standardization system that improves the address data
quality and deliverability of your mail to enable you to qualify for USPS postal discounts. CODE-1
Plus matches input addresses to the addresses in the CODE-1 Plus database to correct your postal
information and add additional postal information. CODE-1 Plus helps you save money by helping
you qualify mail for USPS automation-based discounts and carrier route discounts (Line of Travel
based). You can use CODE-1 Plus to:
•
•
•
•
•
•
Add, correct, or verify 5-digit ZIP Codes
Correct or add the ZIP + 4 Codes
Add Delivery Point Codes
Add carrier route codes
Standardize street, city, and state fields according to USPS conventions
Validate addresses using the Delivery Point Validation (DPV) option
•
Use the LACSLink option to access USPS address conversion information and convert
addresses as needed
•
Use the SuiteLink option to improve business addresses deliverability by adding accurate
secondary (suite) information to the business addresses in your mailing list
Determine if an address is a business or residential address using the Residential Delivery
Indicator (RDI) option
Prevent “false positives” by using the Early Warning System (EWS)
Qualify your standard letters and flats for USPS Enhanced Carrier Route rates by using Line of
Travel.
•
•
•
You can perform these functions interactively (online) or in batch mode. Processing results are
written to one or more output files, depending on your specifications.
What is Address Standardization?
The USPS has established guidelines for what it calls quality addressing. Quality addressing
ensures standardized addresses that help the USPS provide timely mail delivery. This goal becomes
even more critical when mailers attempt to qualify for postal discounts.
A standardized address is an address that has been matched against the CODE-1 Plus database
and formatted based on USPS addressing conventions. CODE-1 Plus uses USPS conventions to
ensure deliverability of your addresses. The USPS addressing conventions include guidelines for:
•
•
•
Format
Punctuation
Address components
The first step to quality addressing is a healthy mailing list. CODE-1 Plus uses USPS address
standardization guidelines set forth in USPS Publication 28 to correct your addresses and ensure
your mail's deliverability.
For more information on address standardization, please see Postal Addressing Standards, USPS
Publication 28 at http://pe.usps.gov/cpim/ftp/pubs/pub28/pub28.pdf. You can order this publication
from:
NATIONAL CUSTOMER SUPPORT CENTER
MEMPHIS TN 38188-0001
(800) 238-3150
Release 4.1.0
12
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
What is Address Standardization?
CODE-1 Plus considers the address to be only the street, and considers the city/state/ZIP Code to
be additional information—separate from the address. For this reason, when we refer to an address
in this book, we mean any or all of the following elements shown in the figure below:
4235
House
Number
N
Leading
Directional
RR
MAIN
Street Name
123
Rural Route or
Highway
Contract
Route Type
Rural Route or
Highway
Contract
Number
ST
Suffix
NW
APT
Trailing
Directional
Apartment
Designator
100
Apartment
Number
BOX 19
Rural Route,
Highway Contract
or PO Box Number
PMB 345
Private
Mailbox
Designator
Private
Mailbox
Number
Address elements and city/state/ZIP information combine to make lines. For the purposes of this
product, these lines are defined as shown in the figure below:
Attention Line
Secondary Address Line (Firm Name)
Primary Address Line
City/State/ZIP Line
ATTN TECHNICAL SUPPORT
PITNEY BOWES INC.
ONE GLOBAL VIEW
TROY, NY 12180-8399
The USPS allows the following placements for suite/apartment numbers:
•
•
•
On the primary address line (just above the city/state/ZIP line), following the street information.
On the secondary address line (just above the primary address line), by itself.
On the secondary address line, with the secondary address line information.
CODE-1 Plus recognizes both apartment/suite designators and apartment/suite numbers on both
secondary and primary address lines, and formats those accordingly.
Release 4.1.0
13
User’s Guide - Open Systems
What is Address Standardization?
In standardizing or normalizing an address with a Private Mailbox (PMB), CODE-1 Plus puts the
PMB designator and number on the secondary address line if a secondary address line is provided.
If a secondary address line is not provided and CODE-1 Plus finds a PMB, then CODE-1 Plus
attempts to append the PMB designator and number to the primary address line. If there is not
enough room on the primary address line, the PMB designator and number is dropped. For more
information on using this option to verify PMB/MSC data, refer to "Using Delivery Point Validation”
on page 137.
Since there is no PMB data on the postal database, CODE-1 Plus will not attempt to correct or verify
PMB information. However, if you have the DPV option, it is possible to verify some PMB information
by providing Commercial Mail Receiving Agency (CMRA) return codes. For more information on
CMRAs, refer to “DPVOUT” in “Parameter Reference” in your CODE-1 Plus Reference Guide. The
following figures provide a standardization example. For a detailed discussion and more examples
for address standardization, refer to USPS Publication 28.
The original address is:
Joe Addressee
Joe
Addressee
553 East
Plaza
Circle, Suite A
Litchfield
Park, AZ
85340
553-A
East
Plaza Circle
Litchfield Park, AZ 85340
Example Address on Envelope
Release 4.1.0
14
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
What is the Matching Process?
For automation compatibility, the USPS prefers the address as it appears below:
The street suffix
(Circle) is
standardized as
CIR.
JOE ADDRESSEE
553 E PLAZA CIR STE A
LITCHFIELD PARK AZ 85340-4996
The directional (E)
appears on the same
line as the street
address.
Punctuation
(except hyphens)
is removed; type
is upper case.
The suite or
apartment
number
follows the
street address
on the same
line.
The ZIP Code is next to the
city/state on the last address
line. The ZIP + 4 Code is
separated from the ZIP Code
by a hyphen.
USPS Preferred Address on Envelope
What is the Matching Process?
During address matching and standardization, address lines are separated into components
(analyzed), and compared to the contents of the CODE-1 Plus database. Any address information
not used as part of matching is referred to as dropped address information. If a match is found, the
input address is standardized according to the contents of the database.
If no database match is determined, CODE-1 Plus provides the option to normalize input addresses.
The normalization process attempts to format the address lines according to conventions outlined in
USPS Publication 28. When the normalization option is invoked and no database match is found for
a particular address, CODE-1 Plus attempts to recognize the individual elements and formats them
according to USPS conventions.
Understanding the CODE-1 Plus Database
The CODE-1 Plus database contains virtually every house number range in the U.S. CODE-1 Plus
ensures that your addresses are correct and in the USPS-specified format. Optionally, CODE-1 Plus
stores match results and return codes relating to each input address. These include match results
for the following:
•
•
•
•
•
•
•
Release 4.1.0
ZIP Codes
ZIP + 4 Codes
Carrier route codes
Standardized address line and/or elements
City names and state abbreviations
Normalized address lines
Address match return codes
15
User’s Guide - Open Systems
What is CASS Certification?
The return codes help you to flag errors in your input file and allow you to select or reject processed
addresses based on your job requirements.
What is CASS Certification?
The USPS Coding Accuracy Support System (CASS) measures the accuracy of address-matching
software. To receive automated processing discounts, you must use software that has been CASScertified and registered by the vendor with the USPS. The following regulations apply:
•
•
•
•
•
The address-matching software used must have been CASS-certified for the current CASS
cycle.
Coding of each file must be performed at least annually (e.g., the mailing date must be within
one year of the coding date).
The database used during an address-matching run must be “current.” A current database is
defined by the matrix in DMM 708.
USPS Form 3553 lists the address-matching software used to process the mailing list. This
report must be submitted with each mailing and must represent all address lists used to generate
that mailing.
CODE-1 Plus includes LACSLink, DPV, and SuiteLink processing. For further details regarding the
options and requirements for CASS certification, see the USPS-issued document on CASS
Cycles on the Rapid Information Bulletin Board System (RIBBS) website, http://ribbs.usps.gov.
CODE-1 Plus does not produce a CASS statement if LACSLink, DPV, or SuiteLink processing is
turned off.
Certifying Your Configurations
If you do not use one of the configurations certified by Pitney Bowes, or if you are calling CODE-1
Plus™ from your own application, you will have to certify the configurations you are using in order to
qualify for mailing discount rates.
Before undertaking your own CASS certifications, serious consideration should be given to support,
audit, and on-going testing for CASS. The standard maintenance and support agreement does not
provide support for clients obtaining their own certification or NCOA approval.
You can obtain support from our Professional Services Group for your own certification or NCOA
approval. Please contact your local sales or support representative for details.

Your product license agreement may not permit you to obtain your own certification. Please
review your software agreement for scope and use of CODE-1 Plus.
When ordering the CASS materials from the USPS, you can request:
•
•
•
Stage 1 (self-measurement) media
Stage 2 (certification test) media
Both media
You are encouraged to order both media, and to experiment with the Stage 1 File until you are
satisfied with the results. During this process, examine the returned address elements returned by
CODE-1 Plus that differ from those the USPS views as “correct.”
When you submit your Stage 2 test, the USPS will probably require you to submit the “parameters
used for matching.” To satisfy this requirement, you should set up a job for CASS, and submit the
parameter list produced by the job to the USPS.
Release 4.1.0
16
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
What is CASS Certification?
Use the “CASSA1” parameter to fill in the CASS-certified company name, software name, and
software version if you attempt CASS certification with CODE-1 Plus (using our batch driver
C1BM00) and have your company and/or software name on record with the USPS as a CASScertified company.
Certified Configurations
USPS Form 3553 is required to include the specific configuration of the address-matching software
that was used in the mailing. This specific configuration must have been CASS-certified. CODE-1
Plus™ automatically produces USPS Form 3553 when the parameters are set to a certified
configuration.

If you use CODE-1 Plus™ with an uncertified configuration, CODE-1 Plus™ does not
produce a USPS Form 3553. It is against USPS regulations for address-matching software to
produce a USPS Form 3553 when uncertified configurations are used. If you use uncertified
configurations, CODE-1 Plus™ generates a message telling you that the configuration is not
certified, and that no form was printed.
Pitney Bowes has CASS-certified the following configurations.
CODE-1 Plus Certified CASS Configurations (Part 1 of 2)
Parameter
Position/Value
Description
AM OUT
8-10
blank
USPS record type.
CONFIG
8
10
12
M (default)
M (default)
M (default)
Strictness code for street name match, firm name
match and directional/suffix match must all be
medium.
CS OUT
19
Blank (default)
I
Store the information in position 72.
Store the input city.
CS OUT
59
Z
Store the ZIP + 4 File preferred last line city name
(override city name).
DPVIN
DPV must be invoked to produce USPS Form
3553.
FIRMNM
The FIRMNM parameter is required when you use
the STELNK parameter.
LACS
LACSLink must be invoked to produce a USPS
Form 3553.
SA2OUT
Release 4.1.0
15
Y
Perform preferred alias processing.
17
User’s Guide - Open Systems
What is CASS Certification?
CODE-1 Plus Certified CASS Configurations (Part 2 of 2)
Parameter
SA OUT
Position/Value
51
Description
N
Return the base street name.
You must invoke SuiteLink processing to produce
USPS Form 3553.
You must specify “S” (default) in STELNK position
8. If you specify “I” or “W” in position 8, CODE-1
Plus does not generate a USPS Form 3553. The
value in position 8 determines whether to shut
down when SuiteLink reports an error.
• I — Ignore error and continue to attempt
SuiteLink processing. CODE-1 Plus does not
generate a USPS Form 3553 (USPS CASS
Summary Report) if you specify the value “I”.
STELNK
• S — Shutdown when SuiteLink reports an error
(default). Specify the value “S” if you want to
generate a USPS Form 3553 (USPS CASS
Summary Report).
• W — Issue warning message and turn off
SuiteLink processing. CODE-1 Plus does not
generate a USPS Form 3553 (USPS CASS
Summary Report) if you specify the value “W”.
NOTE: The FIRMNM parameter is required
when you use the STELNK parameter.
A non-CASS configuration is determined if the maximum probability of correctness indicators are not
the same for all the parameters. The following table provides descriptions of all non-CASS
configurations.
CODE-1 Plus Non-CASS Certified Configurations (Part 1 of 3)
Parameter
Position/Value
Description
AE OUT
64
AM OUT
8-10
BYPEXP
1-6
CONFIG
8, 10, 12
Any other combination of strictness codes other
than MMM (Ex. MEM, EEE, TEM, etc.).
CONFIG
14
Y
Accept multiple matches.
CONFIG
38
P
For dual address match, return a PO Box match
regardless of address line.
CONFIG
40
X
For unique ZIP Code handling, store the input ZIP
Code.
CONFIG
42
X
For PMB handling, store all private mailbox
numbers.
CONFIG
44
N
For enhanced high rise alternate matching, do not
attempt to match to the base record.
Release 4.1.0
X
Store all Private Mailbox Designator.
Location for USPS record type code is specified.
BYPEXP
Override expired US Postal database.
18
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
What is CASS Certification?
CODE-1 Plus Non-CASS Certified Configurations (Part 2 of 3)
Parameter
Position/Value
Description
CONFIG
46
N
For multiple secondary component processing,
assign default ZIP + 4 Code.
CONFIG
49
X
Return vanity city names when they most closely
match input city (a CASS certified configuration will
be created but will not be eligible for postal
automation presort discount).
CONFIG
53
X
For limited locality option, limit address match to
ZIP Code locality.
CONFIG
55
N
Do not perform split indicia processing.
CS OUT
19
Z
Store the primary city for the valid input ZIP Code.
CS OUT
59
C
Store the USPS-preferred City Name from USPS
City/State File.
Store the Primary City Name from the USPS City/
State File.
P
DPVIN
8
N
Do not attempt to DPV confirm if the input file
contains multiple matches of the ZIP Code and the
PO Box or rural route/highway contract.
DPVIN
10
N
Do not attempt to DPV confirm if the input file
contains multiple matches of the ZIP Code and the
street address type.
DPVIN
12
N
Do not attempt to DPV confirm if the input file
contains multiple matches of the Carrier Route in
CODE-1 Plus.
DPVIN
14
N
Do not attempt to DPV confirm if the input file
contains multiple matches of the directional.
DPVIN
16
N
Do not attempt to DPV confirm if the input file
contains multiple matches of the suffix.
DPVIN
18
N
Do not attempt to DPV confirm if input file contains
multiple matches of the suffix/directional
correction.
DPVIN
20
N
Do not attempt to DPV confirm if input file contains
multiple matches of the secondary components
with no designator.
DPVIN
22
N
Do not perform DPV validation using the ZIP+4
assigned by CODE-1 Plus during regular
processing.
DPVIN
24
N
Do not perform DPV validation using secondary
information.
DPVIN
52
N
DPVIN position 52 (RDI Indicator) indicates
whether to perform RDI processing:
• Y — Attempt both DPV and RDI processing.
• N — Do not attempt DPV processing. Perform
RDI processing only. If you specify “N” in
position 52, CODE-1 Plus does not generate a
USPS Form 3553.
• Blank — Perform DPV processing only.
Release 4.1.0
19
User’s Guide - Open Systems
Total Solution
CODE-1 Plus Non-CASS Certified Configurations (Part 3 of 3)
Parameter
Position/Value
Description
SA OUT
51
69
Y
M
If you specify “Y” in position 52, CODE-1 Plus does
not generate a USPS Form 3553.
For multiple standardized address matches, store
the standardized address anyway.
SA2OUT
15
N (default)
Do not perform preferred alias processing.
SA2OUT
50
A
Return alternate address.
Z5 OUT
66
X
For unique ZIP Code handling, store the
information indicated in position 72.
Total Solution
CODE-1 Plus can be used with other Pitney Bowes products as the first step to a total postal
discount and list management solution. Once you have processed a file with CODE-1 Plus, you can:
•
•
•
•
•
Use the CODE-1 Plus reports and return codes to determine the quality of your input file.
Use the Pitney Bowes MailStream Plus software to obtain automation, carrier route, and
additional presort discounts such as machinable and non-automation presort rates.
Use MAIL360 to generate Intelligent Mail® Barcodes.
Use Residential Delivery Indicator to help you make informed shipping decisions by identifying
whether a delivery type is classified as residential or business (especially helpful for parcel
shippers and rate analysis agents).
Use List Conversion Plus to easily convert rented or purchased mailing lists from one format to
another more usable format.
CODE-1 Plus Overview
CODE-1 Plus includes a batch component and an interactive component.
Using the Batch System
The batch system enables you to:
•
•
•
•
•
Release 4.1.0
Process a name-and-address file
Create, edit, and save CODE-1 Plus parameters
Submit CODE-1 Plus jobs
Generate output file(s)
Generate reports
20
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
Using the Batch System
•
Download and reduce the size of the CODE-1 Plus Database
Batch Processing Components
Component
Description
Batch Driver (C1BM00)
Acts as the “engine” by coordinating the matching and output engine
processes.
The standard C1BM00 driver program allows for 200 list codes, and
requires 390 K of memory. An identical C1BM00XL driver program
allows for up to 10,000 list codes, and requires 2.25 MB of memory to
run. To take advantage of the additional list code processing, change
your control language appropriately.
Address Analyzer Module
Analyzes each input record for use by the matcher.
Batch Matching Module
Matches the analyzed elements to the database to determine address
matches.
The figure below provides an overview of the CODE-1 Plus batch components
* Required to generate USPS Form 3553.
Release 4.1.0
21
User’s Guide - Open Systems
Using the Batch System
File Names
CODE-1 Plus Batch System Files (Part 1 of 2)
File Name
System File Name
Assignment
Description
City Database File
CODE-1 Plus City database file.
CITYDB
County Names Database File
CODE-1 Plus USPS County Names
database file.
COUNTY
Customization File
Site customization file for online.
G1CPFDF
Delivery Point Validation Files
(DPV)
Delivery Point Validation system
files.
• DPVDB for Flat DPV DB
• DPVHDB for Full DPV DB
• DPVSDB for Split DPV DB
Details Database File
CODE-1 Plus Details database file.
DTLDB
Enhanced Street Matching
(ESM) File
Enhanced Street Matching file.
C1STRDB
Input Name-and-Address File
Contains the records that you want to
correct using CODE-1 Plus.
C1BMNAM
Input Parameter Record File
Contains the parameters that define
your batch job requirements. These
parameters are discussed later in
this chapter.
C1BMPRM
Invalid ZIP Code Unmatched
Output File
Contains the records with invalid ZIP
Codes that did not match against the
CODE-1 Plus database.
C1BMIZP
LACS Database File
LACSLink Database File.
LLKDB
Line of Travel File
CODE-1 Plus Line of Travel
database file.
LTMASTR
Locality Database File
CODE-1 Plus Locality database file.
LCLDB
Output 3553
USPS Form 3553.
PRNTCAS
Output Execution Log File
Contains the Execution Log.
PRNTXLG
Output Matched Records FIle
Contains all the records that CODE-1
Plus matched with the CODE-1 Plus
database and then verified and
corrected.
C1BMCOK
Output Reports File
Contains the CODE-1 Plus reports,
including the standard Parameter
Record Listing, Control Totals, and
Form 3553.
PRNTRPT
Output Statistics File
Contains all information currently
available in CODE-1 Plus generated
reports (with the exception of
percentages).
C1BMSTA
Release 4.1.0
22
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
Using the Batch System
CODE-1 Plus Batch System Files (Part 2 of 2)
File Name
System File Name
Assignment
Description
Output Unmatched Records
File (Uncoded)
Contains the records with valid U.S.
ZIP Codes that did not match against
the CODE-1 Plus database for some
reason.
C1BMNCO
Preferred/Abbreviated
Database File
Preferred/Abbreviated Database
File.
C1PAL2
Residential Delivery File (RDI)
Residential Delivery File (RDI).
RDIMSTR
SuiteLink Database File
SuiteLink Database File.
SLKDB
Z4CHANGE Option Database
Z4CHANGE USPS database.
Z4CHNG
ZIP + 4 Coded Output File
Contains all the records to which
CODE-1 Plus standardized the ZIP +
4 Codes.
C1BMZP4
ZIP Index Database File
CODE-1 Plus ZIP Index database
file.
ZIPIDX
Parameters
Parameters pass user-specific information (for example, the layout of your input file) to CODE-1
Plus. The two types of parameters include:
•
•
Required —parameters that are necessary to run a job.
Optional—parameters that you use to customize a job.
In this section, we briefly describe each CODE-1 Plus parameter to help you determine the
parameters to use in your job. You can define parameters to describe your input file, output file, and
reports. There are other miscellaneous parameters used for processing functions.
Defining Your Input File
To define an input file, use the following parameters.
Input File Parameters
Parameter
Description
ADDRDF
Required. Specifies the location, length, and format of the address in the input
records and the location and length of the urbanization name field.
FILEDF
Required. Identifies and specifies the structure of the input file. You can also
limit the number of records processed from an input file and define an exit
routine that reads the records from the input file.
CS ZIP
Required. Specifies the location and format of the city, state, and ZIP Code and
the location and format of the Master File vintage date for Z4CHANGE
processing.
FIRMNM
Specifies the location and length of the firm names (company names) in the
input record.
Release 4.1.0
23
User’s Guide - Open Systems
Using the Batch System
Input File Parameters
Parameter
L CODE
Description
Specifies the location of the list codes and specifies up to a 9-character client
code on your input record.
NOTE: The standard batch driver, program C1BM00, processes 200 list
codes. To process up to 10,000 list codes, use the C1BM00XL driver program,
and change your control language appropriately.
MOVE I
Rearranges pieces of the input record before the record is processed.
NTHSEL
Specifies to process only a fraction of records from an input file, or to process
every nth record.
Defining Your Output File
At least one xx OUT parameter is required in a batch job. To define an output file, use the following
parameters.
Output File Parameters
Parameter
Description
AE OUT
Specifies where to store individual address elements.
AM OUT
Specifies where to store the address match return codes.
AM2OUT
Specifies a separate output location for High Rise Default, Rural Route Default,
and Military Default records.
AP OUT
Specifies where to store the normalized address.
CR OUT
Specifies where to store carrier route code.
CS OUT
Specifies where to store the standardized city and state.
FILEDF
Defines the input and output files to the CODE-1 Plus driver program, and may
specify a user-defined exit routine.
FIRMNM
Specifies the location and length for the standardized firm names.
MOVE O
Rearranges the pieces of the output record before the record is written to the
output file.
SA OUT
Specifies where to store the standardized address on the output record.
SA2OUT
Continuation of the SA OUT parameter.
Z4 OUT
Specifies where on the output record to store the ZIP + 4 Code, Delivery Point
Barcode (DPBC), and the Master File vintage date for using the Z4CHANGE
option.
Z5 OUT
Specifies where to store the 5-digit ZIP Code information.
Release 4.1.0
24
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
Using the Batch System
Defining Information for Geographic Coding
To include these parameters in your job, you must have the Pitney Bowes Geographic Coding Plus
or Geographic Coding System installed. To define information for geographic coding, use the
following parameters:
Geographic Coding Parameters
Parameter
Description
G9 OUT
Defines the output storage locations for elements returned by the Pitney Bowes
products Geographic Coding System or Geographic Coding Plus.
G9XOUT
Defines the output storage locations for more elements returned by Geographic
Coding Plus.
G9ZIP9
Defines the location and format of the ZIP and ZIP + 4 Code for the Geographic
Coding System and Geographic Coding Plus products.
Defining Report Information
To define reports for your job, use the following parameters.
Report Parameters
Parameter
Description
CASSA1
Overrides CASS certification data in box A1 of USPS Form 3553.
CASSA4
Overrides Z4CHANGE certification data in boxes A4 - A6 of USPS Form 3553.
CASSA7
Overrides ELOT certification data in boxes A7 - A9 of USPS Form 3553.
HEADER
Required. Defines a header to print below the report title on each page of each
report. Defines starting and stopping ZIP Codes.
LISTID
Defines the name and ID of the address list. Prints on USPS Form 3553.
LISTNM
Defines the list processor’s name. Prints on USPS Form 3553.
MAILER
Defines the mailer’s name and address. Prints on USPS Form 3553.
PAGESZ
Indicates the number of lines to print on each page of the Execution Log and
other reports.
REPORT
Specifies the reports to print. Also, specifies whether to print USPS Form 3553
in a separate print file.
UHDxx
Defines additional headers that print above the report title on each report page.
UFTxx
Defines additional footers that print just below the report title on the bottom of
each report page.
Release 4.1.0
25
User’s Guide - Open Systems
Using the Batch System
Defining Additional Processing Requirements
To define additional processes for your job, use the following parameters.
Additional Processing Parameters
Parameter
Description
BYPEXP
Overrides an expired database.
CHCKPT
Defines a checkpoint every n records (where n is a number you specify). If your
job is terminated for any reason, you can restart the job from the last successful
checkpoint. For the mainframe platform only.
CONFIG
Identifies the matching algorithms and the storage conditions to be used in the
job.
CONFRM
Specifies that records containing either special ZIP Codes or “confirmation flag
values” should be confirmed without undergoing the matching process.
CONTRL
Required. Controls job processing.
EXITOP
Defines an exit routine.
PGMNAM
Enables different versions of the batch matcher (different memory requirements)
to be selected for use. It is possible to choose between 1, 3, 6, 12, and 28 MB
versions of the batch matcher program. There are platform limitations for
PGMNAM. For more information on the PGMNAM parameter, please refer to
"Parameter Reference" in your CODE-1 Plus Reference Guide.
SEQCHK
Defines processing when the input file is not in sorted sequence.
TESTIT
Checks the syntax of your parameters before you run the entire job.
Other Add-On Processing Options
The following options are not included in the standard matching process.
Add-On Processing Parameters
Parameter
Description
AUXIL
Used with the program G1AUXBLD to read an auxiliary file (downloaded USPS
EWS file).
AUXIL1
Indicates the presence of an auxiliary reference file for matching purposes.
DPVIN
Defines matching options when attempting Delivery Point Validation and RDI
processing.
DPVOUT
Specifies where to store the Delivery Point Validation and RDI processing
information.
LOTOUT
Specifies location on the output record to store the information returned from the
Line of Travel master file.
LACS
Used with LACSLink processing option to provide mailers with an automated
method of obtaining new addresses when a 911 emergency system has been
implemented.
SUITELink
Enables SuiteLink processing to improve secondary address information for
businesses.
Release 4.1.0
26
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
Using the Interactive System
Using the Interactive System
The interactive system enables you to perform the following functions:
•
•
•
Address matching
Database inquiry
Site customization
Address Matching
Use Interactive address matching to:
•
•
•
•
Match a single input address against the database.
Analyze return codes to determine the actions taken when attempting a match.
Detect the types and quantities of problems encountered in an input address.
Control the closeness (“tightness” or “looseness”) of address matches.
Additionally, the address matching function provides access to the Pitney Bowes Geographic
Coding Plus screen where you can access geographic match results for the ZIP and ZIP + 4 Code
from your address matching attempt.
Database Inquiry
Use Database inquiry to browse the contents of the CODE-1 Plus database. You can use this
feature for any city on the CODE-1 Plus database to display:
•
•
•
•
•
•
Street Information — Leading directional, street names, street suffixes, post-directional, and ZIP
Codes.
House Information — Even/odd house number ranges, ZIP Codes, ZIP + 4 Code ranges, carrier
routes, USPS record types, alias information, and firm names
Firm Information — House and apartment number ranges, firm names, ZIP Codes, ZIP + 4
Codes, and carrier route codes.
Apartment Information — Apartment number ranges, ZIP Codes, ZIP + 4 Codes, carrier route
codes, USPS record types, apartment types, and number of firms.
ZIP Code Information — Long/short city names, state codes, and city types.
City Information — City names, state codes, ZIP Code ranges, city type codes, urbanization
indicators, and unique ZIP indicators.
Site Customization
Use Site customization to:
•
•
Release 4.1.0
Update access passwords.
Change site-specific default values.
27
User’s Guide - Open Systems
Other CODE-1 Plus Programs and Modules
Address matching, database display, and site customization components operate independently of
the CODE-1 Plus batch driver. Use address matching as part of your own (or other vendor)
applications. The figure below illustrates the relationship of the interactive CODE-1 Plus
components.
CODE-1 Plus Interactive System Component Overview
For more detailed information on the CODE-1 Plus Interactive System, refer to "Getting Started With
Interactive Processing” on page 65.
Other CODE-1 Plus Programs and Modules
CODE-1 Plus also provides you with program modules, callable routines, and executable programs
for flexible use of CODE-1 Plus with your own applications.
Program Interface
CODE-1 Plus includes a program interface that enables you to call up to seven CODE-1 Plus
program modules from any Windows 32-bit applications. The modules can perform the following
functions:
•
•
•
•
•
Match your input address against the CODE-1 Plus database
Browse the CODE-1 Plus database
Separate elements of an address and format them to USPS standards
Generate and print CODE-1 Plus reports
Match ZIP Codes to city/state combinations
•
•
Generate the Delivery Sequence File2 footnotes required by the USPS (required for DPV users)
Determine if the USPS has changed any addresses within a particular ZIP Code since the
previous match attempt
Release 4.1.0
28
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
Other CODE-1 Plus Programs and Modules
Program Modules
The program modules enable you to analyze and match input addresses and add ZIP + 4 Codes
and carrier routes to your addresses. For more information about these program modules and call
areas, refer to your CODE-1 Plus Reference Guide. There are platform limitations for the different
C1MATCHx memory models.
Program Modules
Module
Description
C1MATCHI
Address matcher for interactive processing.
C1MATCHB
Default address matcher for the batch environment (using 3 MB of memory).
C1MATCHS
Matcher for batch processing uses 1 MB (small memory model).
C1MATCHM
Matcher for batch processing uses 6 MB (medium memory model).
C1MATCHL
Matcher for batch processing uses 12 MB (large memory model).
C1MATCHH
Matcher for batch processing uses 28 MB (huge memory model).
C1ANZADR
Analyzes the elements of an input address so that the elements can be used by
C1MATCHx for matching purposes. If an address cannot be matched against
the CODE-1 Plus database, it can be normalized to standard address formats.
To use a module, pass, as parameters, the names of pre-defined call areas. These call areas give
the module all the information necessary to perform the function accurately and return the
appropriate information. COBOL copybooks are available on the distribution media that is used in
your program to define the call areas.
Callable Routines
CODE-1 Plus provides you with the following callable routines.
Callable Routines
Routine
Description
C1BMCBD
Produces a sample CASS report with a callable version of the CODE-1 Plus
matcher. Current USPS regulations require any user-written program calling
CODE-1 Plus for the purpose of claiming automation discounts to undergo
CASS certification. A user-written program must generate and print the USPS
Form 3553, not use the sample generated by C1BMCBD.
C1PRPT
Prints CODE-1 Plus reports without using the CODE-1 Plus batch driver.
C1CTYLKP
Matches ZIP Codes to city/state combinations.
C1CTYLKC
Matches ZIP Codes to city/state combinations from your own CICS application.
EXTADDR2
Separately calls a six-line address line extraction module.
G1CPLKB
Browses the contents of the CODE-1 Plus database from batch and non-CICS
applications.
G1CPLKC
Browses the contents of the CODE-1 Plus database from your own CICS
application.
G1STATW
Creates statistical file records.
Release 4.1.0
29
User’s Guide - Open Systems
Other CODE-1 Plus Programs and Modules
Callable Routines
Routine
Description
C1P430
Processes only those input records that have not been coded by CODE-1 Plus
with the most recent changes according to the USPS Z4CHANGE product. For
more information on the Z4CHANGE option, refer to "Using Z4CHANGE” on
page 131.
C1PDR
Builds a reduced-size database from either your delivery media or a previously
installed CODE-1 Plus database. For more information about C1PDR, refer to
"Calling the C1PDR Module” on page 224.
LTO10
Assigns Line of Travel information to input records. For more information on Line
of Travel, refer to "Using Line of Travel” on page 177.
To use these callable routines, pass, as parameters, the names of pre-defined call areas. These call
areas give the routine all the information necessary to perform the function accurately and return the
appropriate information. For more information, please refer to "CODE-1 Plus Callable Subroutines"
in your CODE-1 Plus Reference Guide.
Executable Programs
The executable programs include the following:
Executable Programs
Program
Description
G1CPDFL
Provides various functions related to the interactive system file G1CPFDF. It can
initialize or repair the file, and can be used to display the encrypted password
stored on the file’s ADMIN record. For more information about G1CPDFL and
the customization file, refer to "Customization File Administration” on page 112.
G1G001
Prints detailed reports using your coded record output file. To execute the
module, you define parameters. The parameters enable you to define the input
file; headers and footers to print on the reports; column headers; report layout
and content; and records to select based on input record values. For more
information on G1G001, refer to "Using G1G001" in your CODE-1 Plus
Reference Guide.
G1AUXBLD
Builds an Early Warning System (EWS) auxiliary file. For more information on
EWS, refer to "Auxiliary File Processing” on page 205.
C1DBRDI
Builds an Residential Delivery File (RDI) to conduct RDI processing. For more
information on RDI, refer to "Using Residential Delivery Indicator (RDI)” on
page 199.
C1PDRDSK
Creates a reduced or regional CODE-1 Plus database from a previously
installed CODE-1 Plus database (disk). If you process name-and-address
records in a limited geographic region of the United States, building and using a
reduced database can save you a significant amount of disk space. For more
information about reducing your database, refer to "Reducing Databases and
Creating Media” on page 211.
C1DBSTSZ
Produces the CODE-1 Plus State Sizes Report. Using this program, you can
determine the total size, in bytes, of the CODE-1 Plus database and the
approximate sizes for each state’s data. The total size of the database is not
equal to the sum of the state sizes, because there is global data that is common
to all states. For more information about the State Sizes Report, refer to
"Generating CODE-1 Plus Reports” on page 117.
Release 4.1.0
30
User’s Guide - Open Systems
Chapter 1: CODE-1 Plus Concepts
Database Expiration
Executable Programs
Program
Description
C1PDBPRT
Produces the CODE-1 Plus Database Print Report. Using this program, you can
select up to 100 ZIP Code ranges and then print the addresses from the
database residing within those ranges. You can produce reports with
information relative to a single ZIP Code or a range of ZIP Codes. For more
information about the Database Print Report, refer to "Generating CODE-1 Plus
Reports” on page 117.
G1DBLOAD
Creates a generic database load program.
G1DBTAP2
Copies complete or reduced databases to media files.
Database Expiration
The CODE-1 Plus database expires in accordance with USPS regulations. When your CODE-1 Plus
database is within 45 days of the expiration date, the following message appears on your Parameter
Record Listing Report in batch and on the CODE-1 Plus Interactive screen.
****************************************************************************
* WARNING: THE CODE-1 Plus MASTER FILE WILL EXPIRE IN 36 DAYS ON MM/DD/YYYY*
* CONTACT CUSTOMER SUPPORT IF ASSISTANCE IS NEEDED
*
****************************************************************************
If your database expires (it is not current as defined by the USPS Domestic Mail Manual (DMM)
708), CODE-1 Plus will not run. In batch mode, the Parameter Record Listing Report prints with the
following message.
****************************************************************************
*
CODE-1 Plus Master File EXPIRED on MM/DD/YYYY
*
****************************************************************************
The interactive matcher ceases to function in accordance with the DMM A960 matrix. The interactive
system inquiry area, however, remains available even after the interactive matcher expires. In this
case, the following message will be displayed on the prompt line above the function key
descriptions:
CODE-1 Plus DATABASE IS EXPIRED
You can, however, use the EXTEND command to bypass the expiration date in the interactive
system.
You can use the BYPEXP parameter to override an expired database and run a job. However, a
USPS Form 3553 will not be produced. The following message prints.
*****************************************************************************
* USPS FORM 3553 SUPPRESSED DUE TO BYPASSING DATABASE EXPIRATION DATE CHECK *
*****************************************************************************
For more information on the BYPEXP parameter, refer to "Parameter Reference" in your CODE-1
Plus Reference Guide.
The Delivery Point Validation (DPV) option will stop working at the end of the fourth month from the
release of the database.
If you have an expired DPV database, this message appears.
******************************************************************************
* DELIVERY POINT VALIDATION SUPPRESSED DUE TO DATABASE EXPIRATION DATE CHECK *
******************************************************************************
Release 4.1.0
31
User’s Guide - Open Systems
Database Expiration
Release 4.1.0
32
User’s Guide - Open Systems
Getting Started
In this chapter:




Getting Started After Installation . . . . . . . . . . . . . . . . . . . . . . . . . .34
Getting Started with Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Getting Started with Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Getting Started with z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
2
Getting Started After Installation
Getting Started After Installation
After installing the software, loading the CODE-1 Plus Database, running the IVP job, and looking at
the execution log to ensure that your job ran to completion, you will notice additions to your system.
If you installed the product on a Windows operating system, you probably noticed that some icons
were placed in the folder where you installed the software. If you installed the software on a
mainframe or Unix platform, you probably see some new library members.
You probably also noticed that Pitney Bowes supplied an installation verification procedure (or IVP)
or sample job. This is the template for your own jobs. This chapter describes the CODE-1 Plus
database, how to copy and use the IVP job as a template for your own jobs, and how to change
parameter records for your jobs.
The CODE-1 Plus installation differs by platform. This chapter provides separate sections for each
platform.
Getting Started with Windows
After you complete your Windows installation and run your IVP job, take a look at the Group 1 folder.
If this is the first time you installed a Pitney Bowes product, you’ll find that this is the folder that the
installation program creates to contain the applications and the associated files. For purposes of this
discussion, we assume that you installed CODE-1 Plus in directory c:\Program Files\Group1\C1P\.
What is the CODE-1 Plus Database?
Double-click the DB folder icon to view the items in it. This folder contains the CODE-1 Plus
database. Note that there are some pairs of files: one file with the .vix extension, and an
accompanying file with no extension. The C1DBLOAD.XLG file is the execution log file resulting
from the last time you loaded a CODE-1 Plus database.
Pitney Bowes compiles the CODE-1 Plus database from the update files received from the United
States Postal Service. These files allow CODE-1 Plus to process your files accurately and ensure
that your mailings comply with USPS regulations. If you keep these files current, you can reduce
delivery errors and maximize postal discounts. The database installation procedure discusses the
installation of these files in the \DB directory. Pitney Bowes recommends that you keep your \DB
directory up to date with the most current CODE-1 Plus database files.
Copying the IVP Job to Use as a Template
The CODE-1 Plus installation process copies one Installation Verification Procedure (IVP) file to
your system. This file is a basic job that verifies the proper installation of the application files and
programs. IVP jobs are useful as a template for creating your own new jobs. The IVP jobs illustrate
the required organization and content. For a step-by-step tutorial on creating a basic batch job, refer
to "Getting Started With Your Batch Job” on page 37.
The first step in defining your CODE-1 Plus jobs is to copy the IVP job for use as a template for your
new job.
1. Go to the Group1 folder and locate the C1P sub-folder.
2. Double-click on the C1P folder icon.
3. Double-click on the DATA folder icon.
Release 4.1.0
34
User’s Guide - Open Systems
Chapter 2: Getting Started
Getting Started with Unix
4. Click on the sample.prm file to highlight it.
5. Right-click to copy the job, then paste it, and rename it for use as a template for your new job.
Modifying the Parameter Files for Your New Job
Refer to Getting Started With Your Batch Job in Chapter 3 on page 37, for a step-by-step tutorial
on writing your own parameters and adding them to your job script.
Getting Started with Unix
This section describes the CODE-1 Plus database and how to use the sample job as a template.
What is the CODE-1 Plus Database?
Pitney Bowes compiles the CODE-1 Plus database from the update files received from the USPS.
These files allow CODE-1 Plus to process your jobs accurately and ensure that your mailings
comply with USPS regulations. If you keep current your CODE-1 Plus database, you can reduce
delivery errors and maximize postal discounts.
Copying the Sample Job to Use as a Template
The CODE-1 Plus installation copies a sample job (installation verification procedure (IVP)) to your
system. This is a basic job that verifies the proper installation of the application files and programs.
The sample job is useful as a template for your new jobs as it has the required organization and
content.
The first step in defining your CODE-1 Plus jobs is to copy the sample job to use as a template for
your own jobs.
1. Go to the $G1C1P/bin directory, where $G1C1P is the directory structure where CODE-1 Plus is
installed.
2. Source the setup file. For example:
. ./setup
This is necessary once at login time and usually not necessary to do again for the session.
3. Copy sample to newname.
newname is the name you assign to the job.
For example, to create a job called myown, enter the following:
cp sample myown
The name you choose will be prefixed to all output data and report file names.
4. Edit the file created.
Release 4.1.0
35
User’s Guide - Open Systems
Getting Started with z/OS
Getting Started with z/OS
The installation process installs the following libraries:
•
•
•
•
•
Load library that contains the CODE-1 Plus (C1P) load members.
PDSE (Partitioned Dataset Extended) library that contains the CODE-1 Plus (C1P) DLL
(Dynamic Link Library) members.
Object library that contains the CODE-1 Plus object members.
Install JCL library that contains all required JCL for proper execution and maintenance of
CODE-1 Plus.
Sample library that contains members that illustrate and facilitate building your own CODE-1
Plus jobs and programs.
What is the CODE-1 Plus Database?
Pitney Bowes compiles the CODE-1 Plus database from the update files received from the USPS.
These files allow CODE-1 Plus to process your jobs accurately and ensure that your mailings
comply with USPS regulations. If you keep your CODE-1 Plus database current, you can reduce
delivery errors and maximize postal discounts.
Tailoring IVPFILE
After completing your z/OS CODE-1 Plus product installation, go to the Instalib created by the
installation and locate the member IVPFILE. You can use this sample installation verification job to
verify that the installation was successful.
1. Locate member IVPFILE. Edit this member using the table in the JCL. This table contains lowercased variables that should be substituted with your installation-specific requirements.

Be sure to set “CAPS ON” before editing.
2. Submit the IVPFILE JCL for processing.
3. Once the IVP job runs, go to your SDSF, or IOF screen to view the results of the job.
4. Select the jobid for the IVPFILE job that you just ran.
All steps should complete with a return code of zero (RC=0). Among several other files created,
each job produces the PRNTRPT Report and PRNTXLG Execution Log for the CODE-1 Plus
batch driver program (C1BM00) that executes the CODE-1 Plus product. Review the PRNTRPT
Report and PRNTXLG Execution Log created for the driver execution.
The install JCL is required for proper execution of CODE-1 Plus. The sample JCL, programs, and
interface areas illustrate and facilitate building your own CODE-1 Plus jobs.
Release 4.1.0
36
User’s Guide - Open Systems
Getting Started With Your
Batch Job
In this chapter:




Introduction to Batch Jobs in CODE-1 Plus . . . . . . . . . . . . . . . . .38
Finding Your Sample Name and Address File . . . . . . . . . . . . . . . .38
Analyzing the Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Using The Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
3
Introduction to Batch Jobs in CODE-1 Plus
Introduction to Batch Jobs in CODE-1 Plus
In this chapter we will lead you through a basic CODE-1 Plus batch job using the sample name-andaddress file that came with your installation media. We will only be covering a few of the options
available to you when setting up and running a CODE-1 Plus job. For any basic CODE-1 Plus job,
you must:
•
•
Specify the layout of your input file
Specify the layout of your output file.
On the following pages, we will create a sample job that uses CODE-1 Plus functions to standardize
addresses, correct ZIP Codes, and add ZIP + 4 and carrier route codes to input records. This
sample job goes a bit beyond what CODE-1 Plus requires for the most basic job. This will give you
the opportunity to experiment with a few options.
TIP: If you wish to add other options to your batch job that are not covered in this tutorial, please
refer to your CODE-1 Plus Reference Guide for a detailed list of all the CODE-1 Plus parameters.
Finding Your Sample Name and Address File
Depending on which platform you are running CODE-1 Plus, your sample file will be found in
different locations. Below is a table of all the platforms and where to find the sample name-andaddress file.
TIP: You can run the sample job provided with your installation media and use the sample control
language as a template for your own jobs.
Location of Sample File by Platform
Platform
Location of Name/Address File
Location of Parameter File
Mainframe
yourhlq.CODE1P.IVP.NAMEADDR
In stream in the IVPFILE member
Unix
$C1C1P/data directory/sample.c1bmnam
JOB: $G1C1P/bin/sample or sample.csh
$G1C1P/data/sample.c1bmprm
Windows
C:\Program Files (x86)\Group1\C1P\data\sample.nam
JOB: C:\Program Files\Group1\
C1P\bin\sample.bat
Analyzing the Job
Before you begin defining your sample job, you need to analyze the following job requirements:
•
•
•
•
•
Your sample input file contents and output files
Your sample input file layout
Your output file contents
Reports you wish to generate
Headers and footers you want on your reports

Release 4.1.0
Periods (.) indicate spaces in the parameter examples (for example, L.CODE.001.5). Do
not type in the periods in your parameters.
38
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Analyzing the Job
Input and Output Files
The following are the input and output files that you must define for this batch job:
•
•
•
•
C1BMNAM — Input name-and-address file
C1BMCOK — Output matched and coded records
C1BMNCO — Output records with valid ZIP Codes and no matched address
C1BMIZP — Output records with invalid ZIP Codes
Name/Address File Layout
The input file we will use for this job is called C1TUTOR. The following represents the complete input
file:
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+
TM129
SAM GERSHWIN
MUSICIANS AND OTHERS
RT 1 BOX 108
PEN ARGYL
PA 18072
TM049
DONALD DUCK
5303 SHERRER PL NW
WASHINGTON
DC 20016
TM059
PEEWEE HERMAN
4205 VAN BUREN ST
UNIVERSITY PARK
MD 20782
TM019
PETER RABBIT
UNITED JUNIOR HIGH
19001 LAUREL GROVE TER
GERMANTOWN
MD 20874
TM059
MINNEY MOUSE
22 S FREDERICK AVE APT 205
GAITHERSBURG
MD 20877
TM059
ALAN QUARTERMAIN
GENERAL HOSPITAL
240 GOLDKETTLE DR
GAITHERSBURG
MD 20878
TM019
MASON WILLIAMS
CLASSICAL GASSERS
9003 TURTLE DOVE LN
GAITHERSBURG
MD 20879
TM129
JOHN WILLIAMS
BOSTON POPS
3514 DUKE ST
COLLEGE PARK
MD 20740
TM049
JOHN WATSON
216 WINCHESTER CT
ANNAPOLIS
MD 21401
TM059
ELLEN BERMAN
9207 SPRUCEWOOD DR
BURKE
VA 22015
TM059
ROBERT E LEE
LEE HISTORICAL SOCIETY
12126 WEDGEWAY CT
FAIRFAX
VA 22033
TM019
BUGS BUNNY
QUEENS COLLEGE
1004 WOODSMANS REACH RD
CHESAPEAKE
VA 23320
TM019
ELMER FUDD
SCHOOL FOR THE DEAF
516 WATERS EDG DR APT F
NEWPORT NEWS
VA 23606
TM059
PAM FLANARY
14 BICKFIELD DR
HAMPTON
VA 23666
TM049
MARTIN FINCH
ST BRIDES COLLEGE
14231 JIB ST APT 22
LAUREL
MD 28989
TM129
MARY ELLEN EPPS
CALVIN COOLIDGE HIGH
2516 BANDER HILL RD
COLUMBIA
SC 29209
TM059
WALT DISNEY
6201 CHARLOTTE HWY
YORK
SC 29745
TM059
JOHN LENNON
JOHN LENNON FAN CLUB
10573 GULF SHORES DR
NAPLES
FL 33963
TM129
JOHN PAUL
ROMAN CATHOLIC SCHOOL BRD 2080 SE MADISON ST
STUART
FL 34997
TM019
JIMMY BUFFET
PIRATES OVER FORTY
5525 GRANNY WHITE PK
NASHVILLE
TN 35589
TM059
BOZ SCAGGS
BOX 8181 STATION B
NASHVILLE
TN 37202
TM049
AL STEWART
2615 HICKORY VALLEY RD
NASHVILLE
TN 37205
TM059
PETER WHITE
1443 CELINA DR
NASHVILLE
TN 37207
TM019
RANDY HOLMBERG
3922 S MISSION OAKS DR
CHATTANOOGA
TN 37412
TM059
YOKO ONO
PO BOX 167
HUDSON
IL 61748
TM059
OLIVE OIL
OLIVE GROWERS OF AMERICA 1003 JUSTIN LN APT 3069
AUSTIN
TX 78757
TM049
JEB STEWART
REBELS FOR A CAUSE
816 W BALBOA BLVD
NEWPORT BEACH
CA 92661
TM049
KEN MURRAY
ASPENITE CORPORATION
770 MAHOGANY LN
SUNNYVALE
CA 94086
TM059
PETER PAN
NEWFOUNDLAND PUBLIC LIBR 2226 BOXWOOD DR
SAN JOSE
CA 95128
TM129
GEORGE HARRISON
TRAVELING WILBURIES
1113 NE BURKE PL
CORVALIS
OR 97330
TM059
MICKEY MOUSE
12106 SE 31ST ST APT D102
BELLEVUE
WA 98005
TM059
PAUL MCCARTNEY
JOHN LENNON FAN CLUB
15433 COUNTRY CLUB DR
MILL CREEK
WA 98012
TM059
PADDY O'NEILL
ST PATRICKS MERCY HOME
5055 8TH AVE NE
SEATTLE
WA 98105
TM049
ROBERT MONDAVI
4225 BROOKLYN AVE NE APT 12
SEATTLE
WA 98105
TM019
POPEYE T SAILOR
716 N 150TH ST
SEATTLE
WA 98133
TM059
RINGO STAR
JOHN LENNON FAN CLUB
8001 SANDPOINT WAY NE
SEATTLE
WA 98155
Release 4.1.0
39
User’s Guide - Open Systems
Analyzing the Job
This mailing list contains name-and-address records that are laid out as follows.
Name-and Address Record Layout
Position
Data Element
1-5
List Code
9-28
Name
30-54
Secondary Address Line
56-85
Primary Address Line
87-106
City Name
108-109
State
111-115
ZIP Code
Output Record Posting Requirements
We are going to perform the following tasks in this tutorial:
•
•
•
•
Standardize the input addresses.
Correct the original ZIP Codes (if necessary).
Add ZIP + 4 and carrier route codes to the records.
Store the output records in the same format as the input records, with the ZIP + 4 Code and
carrier route code added as follows.
ZIP + 4 Code and Carrier Route Layout
Position
Data Element
116-120
ZIP + 4 Code (stored with preceding hyphen)
122-125
Carrier Route Code
In addition, we want CODE-1 Plus to:
•
•
•
Release 4.1.0
Store the normalized address (if no match was found). A normalized address is an input address
that could not be found on the CODE-1 Plus database; however, CODE-1 Plus was able to put
the address elements in the input address into a USPS-recognized format.
Store the individual standardized address elements.
Store return codes.
40
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Analyzing the Job
In your job, you will tell CODE-1 Plus to store the following components.
Address Elements Layout
Position
Data Element
131-181
Address Elements
183-212
Normalized Address Line 1
214-238
Normalized Address Line 2
240-274
Return Codes
Generated Reports
CODE-1 Plus produces the following reports.
•
•
•
•
ZIP + 4 Coding
Carrier Coding
Line of Travel Coding
Summary
These reports can be generated by state, list code, or 3-digit ZIP Code. For our sample job, we only
want the state reports to print.
When running a job, CODE-1 Plus automatically generates two report files: PRNTXLG and
PRNTRPT. These report files contain all of the CODE-1 Plus reports that were created as the result
of a job execution:
•
•
PRNTXLG—contains only one report called, the Execution Log Report. This report always
prints.
PRNTRPT—can contain up to eight different reports. Four reports will output to this file
automatically:
– Parameter Record List Report
– Control Totals Report
– Address-Match Execution Statistics Report
– USPS Form 3553 (this will only be generated for jobs run with a valid CASS configuration).
The following reports are output to this file by default. If you do not want to generate one of these
reports, you must use the REPORT parameter to tell CODE-1 Plus which reports not to print.
–
–
–
–
–
–
–
–
–
–
–
Release 4.1.0
Analysis of Matched Records Report
ZIP + 4 Coding by State Report
Carrier Coding by State Report
Line of Travel Coding by State Report
ZIP + 4 Coding by List Code Report
Carrier Coding by List Code Report
Line of Travel Coding by List Code Report
Processing Summary by State Report
Processing Summary by 3-Digit ZIP Code
Processing Summary for Delivery Point Validation
Processing by List Code for Delivery Point Validation
41
User’s Guide - Open Systems
Using The Tutorial
–
–
–
–
–
–

Processing Summary for Residential Delivery File processing
Processing by List Code for Residential Delivery File processing
ZIP + 4 Coding by 3-Digit ZIP Code
Carrier Coding by 3-Digit ZIP Code
Summary by List Code
Line of Travel Coding by 3-Digit ZIP Code
The National Delivery Index (NDI) Report is not generated by default. To generate this report,
you must use the REPORT parameter.
Report Headers and Footers
There are several parameters that define the information to print on the reports including:
•
•
•
Headers
Footers
Number of lines to print on a page
For our sample batch job, all reports print 60 lines per page with the headers and footers:
Main Header
Secondary Header
Sample Job
CODE-1 Plus Tutorial
Footer
CODE-1 Plus User’s Guide
Performance Considerations
To ensure that your CODE-1 Plus job runs efficiently, the following are recommended:
•
•
Sort your input address file by ZIP Code.
Use the memory model appropriate for your site capability. For more information on memory
models, refer to the PGMNAM parameter.
Using The Tutorial
In this tutorial, you will perform the tasks listed below:
1. Define your input and output files.
2. Specify your input name-and-address record layout.
3. Define your output.
4. Specify the reports to generate.
5. Define the headers and footers for reports.
6. Submit the job for processing.
7. Read the output.
Release 4.1.0
42
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
Step 1. Define Your Input and Output Files.
In this step of the tutorial you will specify the files to be processed and generated by your sample
batch job. The following is a list of each file and what it contains after you process your batch job:
•
•
•
•
C1BMNAM — Input Name-and-Address file
C1BMCOK — Matched and coded records
C1BMNCO — Records with valid ZIP Codes and no matched address
C1BMIZP — Records with invalid ZIP Codes
We use FILEDF parameters to define these files.

For more detailed information on each parameter discussed in this chapter, refer to your
CODE-1 Plus Reference Guide.
First, we start by defining the Input Name-and-Address File (C1BMNAM).
Defining the Input Name-and-Address File
The following steps show you how to specify the input name-and-address file:
1. First, you must start by telling CODE-1 Plus which parameter you are going to define:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF
This is called the keyword; you will see this term used throughout this tutorial.
2. Then, you enter the name of the file that you are going to define. As you remember from the list
above, we are going to define the C1BMNAM file first:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMNAM
3. Now, you are going to tell CODE-1 Plus the format of your name-and-address file. Your file is in
a fixed length format, so you will be using the code F.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMNAM.F
4. Then, you will define the length of your input record. For your sample file, use a length of 115
characters.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMNAM..F.0115
5. Finally, you are going to add the block size. The block size for your input file is 32,600.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMNAM..F.0115.32600
Defining the Output Matched Coded File
Next, you are going to define one of your output files; the C1BMCOK that contains the matched and
coded records that have been processed through CODE-1 Plus.
1. First, enter the FILEDF keyword:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF
2. Then, enter the name of the file that you are going to define:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMCOK
Release 4.1.0
43
User’s Guide - Open Systems
Using The Tutorial
3. Then, enter the format you want for your output file. You want the record format to be fixed, so
enter the code F.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMCOK.F
4. Next, enter the length of the output record. Looking on "Address Elements Layout” on page 41,
you can see that the return codes will be the last information in your output record, in positions
240-274. Therefore, your output record has a length of 274 characters.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMCOK.F.0274
5. The last thing you need to define in this parameter is the block size. For this output file there is a
block size of 32,606. Now your parameter is completed:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMCOK..F.0274.32606
Defining the Output Uncoded File with Valid ZIP Codes
Next, you need to define another output file in your sample job. The C1BMNCO contains the
unmatched records with valid ZIP Codes that have been processed through CODE-1 Plus.
1. First, enter the FILEDF keyword:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF
2. Then, enter the name of the file that you are going to define:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMNCO
3. Now, enter the format for the output record. Yours is a fixed format, so we use the code F.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMNCO.F
4. Next, enter the length of your output file. Refer to step 4 in the previous section and notice that
the length would again be 274. Therefore, enter a length of 274 characters.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMNCO.F.0274
5. Lastly, you need to define the block size. For your sample job, enter a block size of 32,606 to
complete the parameter.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMNCO.F.0274.32606
Defining the Output File with Invalid ZIP Codes
Next, you need to define another output file. The C1BMIZP contains the records with invalid ZIP
Codes that were not matched against the database.
1. First, enter the FILEDF keyword:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF
2. Then, enter the name of the file that you are going to define:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMIZP
3. Now, enter the record format. Yours is a fixed format, so use the code F.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMIZP.F
Release 4.1.0
44
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
4. Next, enter the length of your output file. For your sample job, enter, once again, a length of 274
characters.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMIZP.F.0274
5. Lastly, you need to define the block size. For your sample job, enter a block size of 32,606 to
complete the parameter.
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMIZP.F.0274.32606
Review the Parameters for Step 1
After following all the steps in this section, your job should look like this:
....+....1....+....2....+....3....+....4....+....5....+....6
FILEDF.C1BMNAM..F.0115.32600
FILEDF.C1BMCOK..F.0274.32606
FILEDF.C1BMNCO..F.0274.32606
FILEDF.C1BMIZP..F.0274.32606
Step 2. Specify Your Input Name-and-Address Record Layout.
In this step of the tutorial you will specify the layout of your input file. For your sample job, you will be
defining the following information:
•
•
•
•
Street address
City
State
ZIP Code
You will use four different parameters to define this information and run your job:
•
•
•
•
ADDRDF — Defines the street address input layout.
CS ZIP — Defines the city/state/ZIP Code input layout.
L CODE — Defines the list code input layout.
CONTRL — Required to run a job.
Input File Format
Position
Street Address
Information
Data Element
1-5
List Code
9-28
Name
30-54
Secondary Address Line
56-85
Primary Address Line
87-106
City Name
108-109
State
111-115
ZIP Code
First, you will start by defining the layout of your street address information. That i information is
located in positions 30-85, as indicated in the table above. This requires the addition of an ADDRDF
parameter to your CODE-1 Plus job.
Release 4.1.0
45
User’s Guide - Open Systems
Using The Tutorial
Defining Street Address Input
The address fields on your input file are arranged to correspond to lines on an address label, so we
are going to define both address fields in order for CODE-1 Plus to locate the primary address
information. Primary address information is found in either positions 30 to 54 or positions 56 to 85 of
your sample input record.
1. First, enter the ADDRDF keyword to define your street address information:
....+....1....+....2....+....3....+....4....+....5....+....6
ADDRDF.
2. Next, you need to tell CODE-1 Plus the format of your street address information. In the sample
file, the street address information is contained in two lines, so you will use the code L, which
tells CODE-1 Plus that the address information is contained in 2, 3, 4, 5, or 6 lines with or without
a city and state.
....+....1....+....2....+....3....+....4....+....5....+....6
ADDRDF.L
3. Now, you need to tell CODE-1 Plus where the first address line starts. Looking at your sample
input file in "Input File Format” on page 45, you see that the first line of address information starts
in position 30. Enter that number to your job.
....+....1....+....2....+....3....+....4....+....5....+....6
ADDRDF.L.030
4. After telling CODE-1 Plus where the first line of address information begins, you need to tell
CODE-1 Plus the length of this information in your sample input file. Returning once again to
"Input File Format” on page 45, you see that our first line of address information ends in position
54. This means that the length of the first address line is 25 characters long.
....+....1....+....2....+....3....+....4....+....5....+....6
ADDRDF.L.030.25
5. Now, you need to tell CODE-1 Plus where the second line of address information starts and its
length, just like in steps 3 and 4. Once again, the second line of address information starts in
position 56, so we add that to our job.
....+....1....+....2....+....3....+....4....+....5....+....6
ADDRDF.L.030.25.056
Then, you see, by looking at "Input File Format” on page 45 once again, that the second line of
address information is 30 characters long:
....+....1....+....2....+....3....+....4....+....5....+....6
ADDRDF.L.030.25.056.30
You have now completed the ADDRDF parameter for your sample job.
Defining the City/State/ZIP Code Layout
The city, state, and ZIP Code information in your sample input file are located in separate fields.
Since you want to specify the location, length, and format of each of these three data elements, you
need to add a CS ZIP parameter to your job.
The city information is located in positions 87 to 106, the state information is located in positions 108
to 109, and the ZIP Code information is located in positions 111 to 115 in your sample input file. You
will need to define all of this information for CODE-1 Plus.
1. First, you must enter the CS ZIP keyword to define your city, state, and ZIP Code information:
....+....1....+....2....+....3....+....4....+....5....+....6
CS.ZIP
Release 4.1.0
46
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
2. Next, you need to define how the city, state and ZIP Code information resides in your sample
input file. In your file, the city, state, and ZIP Code are in three separate fields, so you add the
code S to your job.
....+....1....+....2....+....3....+....4....+....5....+....6
CS.ZIP.S
3. Now, you need to tell CODE-1 Plus where the ZIP Code information is located in your input file.
Looking at the "Input File Format” on page 45, you see that this information starts in position 111.
....+....1....+....2....+....3....+....4....+....5....+....6
CS.ZIP.S.111
4. In this next step, you need to tell CODE-1 Plus that your ZIP Code is in a 5-byte character format
by using the code C.
....+....1....+....2....+....3....+....4....+....5....+....6
CS.ZIP.S.111.C
5. Next, you need to tell CODE-1 Plus the location and length of your city information in the input
file. Looking at "Input File Format” on page 45 once again, we see that the city information starts
in position 87 and is 20 characters long, so you add this to your job.
....+....1....+....2....+....3....+....4....+....5....+....6
CS.ZIP.S.111.C.087.20
6. Next, you need to tell CODE-1 Plus the location and length of your state information in your input
file. Looking at "Input File Format” on page 45, you see that your state information starts in
position 108 and is 2 characters long, so you add this to your job.
....+....1....+....2....+....3....+....4....+....5....+....6
CS.ZIP.S.111.C.087.20.108.02
Specifying CONTRL Parameter
In order for any CODE-1 Plus job to run, you must enter a CONTRL parameter in your batch job.
Add the CONTRL keyword to your job:
....+....1....+....2....+....3....+....4....+....5....+....6
CONTRL
You have now completed setting up the parameters for your input information. In the next section we
will discuss the output parameters you are going to use in your sample job.
Review the Parameters for Step 2
After following all the steps in this section, your job should look like this:
....+....1....+....2....+....3....+....4....+....5....+....6
ADDRDF.L.030.25.056.30
CS.ZIP.S.111.C.087.20.108.02
CONTRL
Step 3. Define Your Output
Now that you have defined your input information, you will need to define your output. In this part of
the batch job tutorial, you will define the following information:
•
•
•
•
•
Release 4.1.0
How to store the standardized address
How to store the individual address elements
How to store the normalized address lines
How to store the standardized city and state information
How to store the 5-digit ZIP Code
47
User’s Guide - Open Systems
Using The Tutorial
•
•
•
•
•
How to store the ZIP + 4 Code
How to store the carrier route code
How to store the various return codes
How to store default indicators
How to store information returned from the Line of Travel master file.
In order to do this, you must use the following parameters in your sample CODE-1 Plus job:
•
•
•
•
•
•
•
•
•
•
SA OUT
AE OUT
AP OUT
CS OUT
Z5 OUT
Z4 OUT
CR OUT
AM OUT
AM2OUT
LOTOUT
Before you begin adding any parameters to your job, you need to determine how you want your
output information to appear in the output record. For your sample job, you want CODE-1 Plus to
store the output records in the same format as the input records, with the ZIP + 4 Code and carrier
route coded added as follows.
Layout Example 1
Position
Data Element
116-120
ZIP + 4 Code (stored with preceding hyphen)
122-125
Carrier route code
126-130
LOT Code (numeric and alphabetic)
Remember, your ZIP Code information ended in position 115—that is why the ZIP + 4 Code will start
in position 116. You also want CODE-1 Plus to store the normalized address (if no match was
found), the individual standardized address elements, and return codes. You want these
components stored as follows.
Layout Example 2
Position
Release 4.1.0
Data Element
131-181
Address Elements:
House Number (10 characters in length)
Leading Directional (2 characters in length)
Street Name (15 characters in length)
Street Suffix (4 characters in length)
Apartment Designator (1 character in length)
Apartment Number (1 character in length)
183-212
Normalized Address Line 1
214-238
Normalized Address Line 2
240-282
Return Codes
48
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
You are now ready to define your output information.
Storing the Standardized Address
In order to tell CODE-1 Plus how to store the standardized address information in your sample job,
you will need to add an SA OUT parameter to your job.
1. First, enter the SA OUT keyword to your job:
....+....1....+....2....+....3....+....4....+....5....+....6
SA.OUT
2. Next, tell CODE-1 Plus where to store the 1-character Address Return Code in your output file.
Looking at "Layout Example 2” on page 48, you can see that the return codes are to be stored in
positions 240-282. Enter 240 as the position for your Address Return Code.
....+....1....+....2....+....3....+....4....+....5....+....6
SA.OUT.240
3. Then, you need to tell CODE-1 Plus where you would like the standardized street address to be
stored in the output file. For your sample job, you are going to enter the code INP. This means
that if the input primary address matches the database, the standardized primary address line is
stored in the same position on the output file as it was on the input file.

If you choose the INP storage option, CODE-1 Plus overlays the standardized address
on your original input address.
....+....1....+....2....+....3....+....4....+....5....+....6
SA.OUT.240.INP
You have now completed adding the SA OUT parameter to your sample job.
Storing the Individual Address Elements
In order to tell CODE-1 Plus how to store the standardized street address elements in your output
file, you will need to add an AE OUT parameter to your sample job.
1. First, enter the AE OUT keyword to your job.
....+....1....+....2....+....3....+....4....+....5....+....6
AE.OUT
2. Next, you need to tell CODE-1 Plus the location for the house number and leading directional in
your output file. Looking at the second table, you see that the house number information is 10
characters long and your leading directional information is 2 characters long. Therefore, enter a
location of 131 for the house number information and 142 for the leading directional information.
....+....1....+....2....+....3....+....4....+....5....+....6
AE.OUT.131.142
3. Now, you need to tell CODE-1 Plus the location and length of your street name information in the
output file. Looking at the second table, you see that our street information is 15 characters long.
Following the leading directional information in position 142 from step 2, you see that your street
name information needs to be placed starting in position 145.
....+....1....+....2....+....3....+....4....+....5....+....6
AE.OUT.131.142.145.15
4. Now, you need to tell CODE-1 Plus where to put the street suffix information. Looking at "Layout
Example 2” on page 48, you see that this information is 4 characters long, so it will begin in
position 161 and end in position 164.
....+....1....+....2....+....3....+....4....+....5....+....6
AE.OUT.131.142.145.15.161
Release 4.1.0
49
User’s Guide - Open Systems
Using The Tutorial
5. Next, you need to tell CODE-1 Plus where to put the apartment designator and the apartment
number in your output file. Looking at the second table, you see that both the apartment
designator and the apartment number are one character in length. So, calculating the street
suffix information from the previous step as being 4 characters long, you realize that your
apartment designator needs to reside in position 166 and the apartment number in position 168.
....+....1....+....2....+....3....+....4....+....5....+....6
AE.OUT.131.142.145.15.161.....166.168
6. Finally, you need to tell CODE-1 Plus what to store in your output file if no standardized match
can be found for any of your input addresses. You want CODE-1 Plus to store blanks, so enter
the code B.
....+....1....+....2....+....3....+....4....+....5....+....6
AE.OUT.131.142.145.15.161.....166.168.............B
That completes the AE OUT parameter for your sample job.
Storing the Normalized Address Lines
A normalized address is an address for which CODE-1 Plus could not find a match. However,
instead of CODE-1 Plus not storing the address on the output file, it takes the address lines and puts
them in a USPS-preferred format. If you want to store the normalized address lines in your output
file, you need to tell CODE-1 Plus by using an AP OUT parameter in your sample job.
1. First, add the AP OUT keyword to your job:
....+....1....+....2....+....3....+....4....+....5....+....6
AP.OUT
2. Next, you need to tell CODE-1 Plus how you would like to store the normalized primary address
line. For your example, you want to store the normalized primary address line only when the
standardized address is not stored, so add the code X to your job.
....+....1....+....2....+....3....+....4....+....5....+....6
AP.OUT.......................X
3. Next, you need to tell CODE-1 Plus where to store the normalized primary address lines in your
output file and the length of that information. Choose position 183 with a length of 30 characters.
Note that in the AE OUT parameter, by choosing position 183, you are placing the normalized
primary address information to the right of all of your standardized address information.
....+....1....+....2....+....3....+....4....+....5....+....6
AP.OUT.......................X.183.30
4. Now, you need to tell CODE-1 Plus how you would like to store the normalized secondary
address line. For your example, you want to store the normalized secondary address line only
when the standardized address is not stored, so add the code X to your job.
....+....1....+....2....+....3....+....4....+....5....+....6
AP.OUT.......................X.183.30.X
5. As for the normalized primary address line in step 3, you need to tell CODE-1 plus where you
want the normalized secondary address line stored and its length. For your example, enter 214
for the location on the output file and a length of 25.
....+....1....+....2....+....3....+....4....+....5....+....6
AP.OUT.......................X.183.30.X.214.25
You have now completed the AP OUT parameter for your sample job.
Release 4.1.0
50
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
Storing the City and State
In order to store the city and state information in your output file, you need to add a CS OUT
parameter to your sample job.
1. First, add the CS OUT keyword to your sample job:
....+....1....+....2....+....3....+....4....+....5....+....6
CS.OUT
2. Then, you need to tell CODE-1 Plus where to store the city/state return code on the output file.
This return code will give you the reason why city and state information was or was not stored in
your output file. Enter a position of 242.
....+....1....+....2....+....3....+....4....+....5....+....6
CS.OUT.242
3. Now, you need to tell CODE-1 Plus where to store the returned city name on the output file and
the length of this information. For your example, choose position 87 for the city information with a
length of 20 characters.
....+....1....+....2....+....3....+....4....+....5....+....6
CS.OUT.242.087.20
4. To finish this parameter, you need to tell CODE-1 Plus where you would like the 13-character
short city name to be stored on the output file. A short city name is the USPS-accepted
abbreviation of a city. For example, the short city name for Macomb Township, MI is Macom Twp.
For your example, choose position 108.
....+....1....+....2....+....3....+....4....+....5....+....6
CS.OUT.242.087.20...108
Storing the 5-digit ZIP Code
In order to store the 5-digit ZIP Code information in your output file, you need to add a Z5 OUT
parameter to your sample job.
1.
First, add the Z5 OUT keyword to your sample job.
....+....1....+....2....+....3....+....4....+....5....+....6
Z5.OUT
2. Next, you need to tell CODE-1 Plus where to store the ZIP Code return code in the output file.
The ZIP Code return code tells you why the ZIP Code information was not stored in your output
file. You want CODE-1 Plus to store this code in position 257 of your output file.
....+....1....+....2....+....3....+....4....+....5....+....6
Z5.OUT.257
3. Next, you need to tell CODE-1 Plus where you would like the standardized ZIP Code stored in
your output file. For your sample job, store the standardized ZIP Code in position 111.
....+....1....+....2....+....3....+....4....+....5....+....6
Z5.OUT.257.111
4. Finally, you need to tell CODE-1 Plus the format of your output ZIP Code. You would like the ZIP
Code to be stored as a 5-byte character number, so use the code C.
....+....1....+....2....+....3....+....4....+....5....+....6
Z5.OUT.257.111.C
Storing the ZIP + 4 Code
In order to store the ZIP + 4 Code information in your output file, you need to add a Z4 OUT
parameter to your sample job.
Release 4.1.0
51
User’s Guide - Open Systems
Using The Tutorial
1. First, add the Z4 OUT keyword to your sample job:
....+....1....+....2....+....3....+....4....+....5....+....6
Z4.OUT
2. Next, you need to tell CODE-1 Plus where to store the ZIP + 4 return code. This return code tells
you why the ZIP + 4 Code information was not stored in your output file. You want CODE-1 Plus
to store this code in position 261 of your output file.
....+....1....+....2....+....3....+....4....+....5....+....6
Z4.OUT.261
3. Next, you need to tell CODE-1 Plus where to store the standardized ZIP + 4 Code in your output
file. For your sample job, you want to store the standardized ZIP + 4 Code in position 116.
....+....1....+....2....+....3....+....4....+....5....+....6
Z4.OUT.261.116
4. Finally, you need to tell CODE-1 Plus the format of your ZIP + 4 Code information. You want the
ZIP + 4 Code to be stored as a 4-byte character number with a preceding hyphen, so use the
code -.
....+....1....+....2....+....3....+....4....+....5....+....6
Z4.OUT.261.116.-
Storing the Carrier Route
In order to store the Carrier Route information in your output file, you need to add a CR OUT
parameter to your sample job. Carrier Route Codes improve the deliverability of addresses and
enable you to presort to take advantage of USPS carrier route discounts.
1. First, add the CR OUT keyword to your sample job.
....+....1....+....2....+....3....+....4....+....5....+....6
CR.OUT
2. Next, tell CODE-1 Plus where you want the Carrier Route return code stored in your output file.
This return code tells you why the Carrier Route information was not stored in your output file.
You want CODE-1 Plus to store this information in position 259 in your output file.
....+....1....+....2....+....3....+....4....+....5....+....6
CR.OUT.259
3. Finally, you need to tell CODE-1 Plus where you want the standardized carrier route stored in
your output file. Enter position 122.
....+....1....+....2....+....3....+....4....+....5....+....6
CR.OUT.259.122
You have now completed the CR OUT parameter for your sample job.
Storing the Return Codes
CODE-1 Plus includes many return codes that can be stored in your output file. Return codes can
tell you what happened in your processing to certain types of information—from directionals to ZIP
Codes. In this section of the tutorial you will add an AM OUT parameter to your sample job to tell
CODE-1 Plus where to store the return codes you want in the output file.
1. First, add the AM OUT keyword to your sample job.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT
Release 4.1.0
52
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
2. Now, you want to add an output location for the USPS Record Type. The USPS Record Type will
tell you what kind of address was coded. For example, if you receive a return code of R in this
position, you will know that it is a Rural Route address. Select position 250 for the location of this
return code.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT.250
3. Next, you want to add an output location for a general return code. The general return code tells
you why your address did not code properly in CODE-1 Plus. For example, a return code of B
means that there is insufficient or blank address information in your input file and no match could
be made. You want this return code to appear in position 253 in the output file.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT.250.253
4. Next, you want to add an output location for a directional return code. A directional return code in
the output file will tell you how the directional information in your input file was processed in
CODE-1 Plus. For example, a return code of F tells you that the directional was correct, but was
in the wrong location in your input file. You want this return code to appear in position 255 in the
output file.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT.250.253.255
5. Next, you want to add an output location for a suffix return code. A suffix return code in the
output file will tell you how the suffix information in your input file was processed in CODE-1 Plus.
For example, a return code of S tells you that the suffix did not match the database. You want
this return code to appear in position 244 in the output file.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT.250.253.255.244
6. Next, you want to add an output location for an apartment return code. An apartment return code
in the output file will tell you how the apartment information in your input file was processed in
CODE-1 Plus. For example, a return code of A tells you that the apartment information in your
input file does not match the database. You want this return code to appear in position 246 in the
output file.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT.250.253.255.244.246
7. Next, you want to add an Overall Probable Correctness Score to your output file. You want this
score to appear in position 248 in the output file.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT.250.253.255.244.246.....248
8. Next, you want to add a Street Name Match Score to your output file. This score will tell you the
closeness of the street name match. The scoring is similar to the Overall Probable Correctness.
You want this score to appear in position 268 in the output file.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT.250.253.255.244.246.....248.....268
9. Next, you want to add an Address Probable Correctness code to your output file. This code is
also similar to the Overall Probable Correctness, except it is for your address information only.
You want this code to appear in position 272 in the output file.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT.250.253.255.244.246.....248.....268.....272
Release 4.1.0
53
User’s Guide - Open Systems
Using The Tutorial
10. Finally, you want to add a ZIP Code Confirmed/Altered/Original Indicator to your output file. This
indicator tells you whether or not the ZIP Code was confirmed by CODE-1 Plus as correct,
altered, or the original input ZIP Code. You want this indicator to appear in position 274 in the
output file.
....+....1....+....2....+....3....+....4....+....5....+....6
AM.OUT.250.253.255.244.246.....248.....268.....272.....274
Review the Parameters for Step 3
After following all the steps in this section, your job should look like this:
....+....1....+....2....+....3....+....4....+....5....+....6
SA.OUT.240.INP
AE.OUT.131.142.145.15.161.....166.169.174.........B
AP.OUT.......................X.183.30.X.214.25
CS.OUT.242.087.20...108
Z5.OUT.257.111.C
Z4.OUT.261.116.CR.OUT.259.122
AM.OUT.250.253.255.244.246.....248.....268.270.272.....274
Step 4. Specify the Reports to Generate
Now that you have finished defining your input information and your output file, you need to select
the reports you want CODE-1 Plus to generate. For more information on CODE-1 Plus reports, refer
to "Getting Started With Your Batch Job” on page 37. Four reports are generated automatically with
any CODE-1 Plus job:
•
•
•
•
Execution Log
Control Totals
Address Match Execution Statistics
USPS Form 3553 (only if you are running a CASS-certified configuration)
If you want to generate other reports besides those listed, you need to add a REPORT parameter to
your job. For your sample job, you will be adding a Summary by State report. You also will tell
CODE-1 Plus to print your reports in mixed case. If you add a REPORT parameter to your job, you
will be printing every report that CODE-1 Plus can produce, so you must mark which reports you DO
NOT want printed out of that list of reports.
1. First, add the REPORT keyword to your sample job:
....+....1....+....2....+....3....+....4....+....5....+....6
REPORT
2. Next, you need to add an N in the correct positions for every report you don’t want printed.
....+....1....+....2....+....3....+....4....+....5....+....6
REPORT.N.N.N.N.N.N.N
3. Next, tell CODE-1 Plus which report you do want to print—the Summary by State Report. The Y
needs to go in position 22.
....+....1....+....2....+....3....+....4....+....5....+....6
REPORT.N.N.N.N.N.N.N.Y
4. Continue to tell CODE-1 Plus to not print other reports.
....+....1....+....2....+....3....+....4....+....5....+....6
REPORT.N.N.N.N.N.N.N.Y.N.N
5. In position 28 you have the option to tell CODE-1 Plus to print the reports in mixed case. So, add
an N to your sample job in position 28.
....+....1....+....2....+....3....+....4....+....5....+....6
REPORT.N.N.N.N.N.N.N.Y.N.N.N
Release 4.1.0
54
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
6. Continue telling CODE-1 Plus not to print any additional reports.
....+....1....+....2....+....3....+....4....+....5....+....6....+....7...
REPORT.N.N.N.N.N.N.N.Y.N.N.N.N.N.N.N.N.N..............................N
Step 5. Define the Headers and Footers for Reports.
In this step you will define the headers and footers that you want to appear on your CODE-1 Plus
reports. For your sample job you want to print the header “01/01/2012 Sample Job” on the first page
of each report. You also want to print the secondary header “CODE-1 Plus Tutorial” on every page
and to print the footer “CODE-1 Plus User’s Guide.” To define this information, you need to add
these parameters to your sample job:
•
•
•
HEADER
UHD
UFT
Adding a Header to Your Job
In order to print the header “01/01/2015 Sample Job” on the first page of each report, you need to
add a HEADER parameter to your sample job.
1. First, add the HEADER keyword to your sample job:
....+....1....+....2....+....3....+....4....+....5....+....6
HEADER
2. Next, enter the date that you want to appear in your header.
....+....1....+....2....+....3....+....4....+....5....+....6
HEADER.01/01/2015
3. Then, enter the header text that you want to appear on the top of the first page of each report.
....+....1....+....2....+....3....+....4....+....5....+....6
HEADER.01/01/2015.Sample.Job
You have now completed the HEADER parameter for your sample job.
Adding Additional Header Information to Your Job
In order to print the header “CODE-1 Plus Tutorial” at the top of the page on the left side of header
line 1, you need to add a UHD parameter to your sample job.
1. First, add the UHD keyword to your sample job:
....+....1....+....2....+....3....+....4....+....5....+....6
UHD
2. Next, tell CODE-1 Plus on which header line number you want our information printed. For your
example, choose line 1.
....+....1....+....2....+....3....+....4....+....5....+....6
UHD1
3. Then, tell CODE-1 Plus on which side of the header line you want your information printed. For
your example, choose the left side of the line.
....+....1....+....2....+....3....+....4....+....5....+....6
UHD1A
Release 4.1.0
55
User’s Guide - Open Systems
Using The Tutorial
4. Finally, tell CODE-1 Plus the text you want printed in the header line. This text will appear first
line of the header on the left side of every page of your reports.
....+....1....+....2....+....3....+....4....+....5....+....6
UHD1A.CODE-1.Plus.Tutorial
You have now completed the UHD parameter for your sample job.
Adding a Footer to Your Job
In order to add a footer to your sample job, you need to add a UFT parameter. You want each page
of each report to have the footer “CODE-1 Plus User’s Guide” printed at the bottom of the page on
the left side of footer line 1.
1. First, add the UFT keyword to your sample job:
....+....1....+....2....+....3....+....4....+....5....+....6
UFT
2. Next, tell CODE-1 Plus on which line you want the footer printed. For your sample job, you want
the footer printed on line number 1.
....+....1....+....2....+....3....+....4....+....5....+....6
UFT1
3. Next, you want to tell CODE-1 Plus on which side of the footer line you want your footer printed.
For your sample job, you want the footer printed on the left side of the footer line.
....+....1....+....2....+....3....+....4....+....5....+....6
UFT1A
4. Finally, you need to tell CODE-1 Plus what you want printed in your footer. This text will appear in
first line of the footer on the left side of every page of your reports.
....+....1....+....2....+....3....+....4....+....5....+....6
UFT1A.CODE-1.Plus.User’s.Guide
You have now completed the UFT parameter for your sample job.
Reviewing Parameters for Step 5
After following the steps in this section, your job should look like this:
....+....1....+....2....+....3....+....4....+....5....+....6
HEADER.01/01/2012.Sample.Job
UHD1A.CODE-1.Plus.Tutorial
UFT1A.CODE-1.Plus.User’s.Guide
You have now completed all the parameters for your sample batch job.
Step 6: Submit the Job for Processing
Using Different Environments
This section provides processing information and step-by-step instructions for running CODE-1 Plus
batch jobs. It does not contain entire script/JCL examples, so please refer to the installation media
for complete examples and templates.

Release 4.1.0
The instructions in this section cover multiple platforms. Be sure to use the appropriate
platform-specific instructions to modify the script and/or JCL examples for your environment.
56
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
File Names
Regardless of the environment in which you are running CODE-1 Plus, the following file names are
used for the various input and output files:

For z/OS, and IMS Platforms: To process up to 10,000 list codes, you must change the
driver name from the standard C1BM00 program to C1BM00XL. C1BM00XL requires 2.25
MB of memory to run. (The standard C1BM00 driver program allows for 200 list codes, and
requires 390 K of memory.)
File Names for Input and Output Files (Part 1 of 2)
Assignment
Release 4.1.0
Description
C1BMCHK
(IBM Mainframe only) The checkpoint / restart file
C1BMPRM
The input parameter file
PRNTRPT
The output reports file
PRNTXLG
The output Execution Log report file
PRNTCAS
The USPS Form 3553
C1BMNAM
The input name-and-address file
C1BMCOK
The output matched records file
C1BMNCO
The output unmatched records file
C1BMIZP
The output invalid ZIP Code records file
C1BMZP4
The output ZIP + 4 coded records file
C1PALA
The Abbreviate Alias file
C1PALP
The Preferred Alias file
C1STRDB
The enhanced street matching database file
Z4CHNG
The Z4CHANGE Option Database
ZIPIDX
The CODE-1 Plus ZIP Index database file
COUNTY
The CODE-1 Plus USPS County Names database file
LCLDB
The CODE-1 Plus Locality database file
CITYNM
The CODE-1 Plus City Name files
DTLDB
The CODE-1 Plus Details database file
CITYDB
The CODE-1 Plus City database file
G1CPFDF
The CODE-1 Plus customization file
LTMASTR
The CODE-1 Plus Line of Travel file
57
User’s Guide - Open Systems
Using The Tutorial
File Names for Input and Output Files (Part 2 of 2)
Assignment
Description
PTRDB
The CODE-1 Plus Locality pointer file
G1STAT
The CODE-1 Plus Statistics file
G1C1AUX
The CODE-1 Plus Auxiliary file
DPVDB
The CODE-1 Plus Flat Delivery Point Validation database file
DPVHDB
The CODE-1 Plus Full Delivery Point Validation database file
DPVSDB
The CODE-1 Plus Split Delivery Point Validation database file
LLKDB
LACSLink database file
SLKDB
SuiteLink database file
RDIDB
Residential Delivery Indicator database file
IMS JCL
The example IMS JCL assigns the input and output datasets and runs the CODE-1 Plus driver
program (C1BM00). You can find this file in the IVPFILE member of the INSTALL library.
z/OS JCL
The example z/OS JCL assigns the input and output datasets and runs the CODE-1 Plus driver
(C1BM00). You can find this file in the IVPFILE member of the INSTALL library.
UNIX Shell Scripts
To run CODE-1 Plus under UNIX, you must complete these steps:
1. Source the Setup script to set up the CODE-1 Plus environment variables. The setup script
found on the installation media sets all the CODE-1 Plus environment variables. The setup script
resides in $G1C1P\bin. You may need to modify the paths and file names appearing in
lowercase, bold type. For more information on the bin/setup file, see your Installation
Instructions.
2. Source the job script to set up the CODE-1 Plus job variables. The job script, named sample,
assigns file names to all the CODE-1 Plus file variables. The script sample resides in
$G1C1P\bin. You need to modify the paths and file names appearing in lowercase, bold type.
3. Execute the runc1bm00 script to execute the CODE-1 Plus batch driver. The runc1bm00 script
executes the CODE-1 Plus batch driver. The runc1bm00 script resides in $G1C1P\bin.
Windows
This section assumes you are familiar with the CODE-1 Plus Windows Installation Instructions and
the details of how the product was installed on your system. The Pitney Bowes products for the
Windows environment are designed so that you can set up and run a job with a minimum amount of
typing. Information that does not change from job to job is stored in files that you can edit, via the
Pitney Bowes icons provided, using your preferred text editor.
Release 4.1.0
58
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
This section describes how to:
•
•
•
•
Edit/Save job files
Edit/Save parameter files
Run a CODE-1 Plus batch job
Print reports from an RTF file
Customization Issues
If you need to modify the CODE-1 Plus components to suit your needs, be prepared to add your
modifications again when we send a product update. Record the modifications you make, so that if
you need to call Pitney Bowes Technical Support, Pitney Bowes can duplicate your problem.
In CODE-1 Plus, the bin\SETUP.BAT file defines environment variables needed for any invocation of
CODE-1 Plus functions. You should review bin\SETUP.BAT for any customization that is necessary
for your system. If you have any questions, please contact Technical Support.
Step 1. Edit/Save Job Files
A job file is a batch command file (.BAT extension) that runs one of the CODE-1 Plus programs,
including configuring the program’s environment to define the files the program is to use. Pitney
Bowes provides six jobs in the bin directory that are used to test the product while serving as
examples and templates for you to create your own job files. These jobs are the following:
•
•
•
•
•
•
SAMPLE—runs the batch driver program (C1BM00) to process the standard Installation
Verification Procedure (IVP), which uses data\SAMPLE.NAM as the input file and the national
files.
SAMGRW—runs the Generalized Report Writer program (G1G001) to print some of the fields of
all data\SAMPLE.NAM file records. For more information on G1G001, please refer to "Using
G1G001" in your CODE-1 Plus Reference Guide.
SAMZ4C—runs C1BM00 to exercise the ZIP + 4 Changes Option (requires the CODE-1 Plus
ZIP + 4 Changes Option/Windows product to be installed). For more information on the
Z4CHANGE Option, please refer to "Getting Started With Your Batch Job” on page 37.
SAMDBPRT—runs the database print program (SAMDBPRT) to create reports from the CODE1 Plus database using selected ZIP Code ranges.
REDIVP—runs the database reduction program using the CODE-1 Plus database from the
original distributed media. Refer to "Getting Started With Your Batch Job” on page 37 for more
information on this option.
REDDSK—runs the database reduction program using a previously installed CODE-1 Plus
database. Refer to "Getting Started With Your Batch Job” on page 37 for more information on
this option.
Important Job File Commands
This section describes important job file commands, how to create a new job file, and how to edit an
existing job file. For illustration purposes, we show SAMPLE.BAT and REDIVP.BAT on the following
pages.
The most important job file commands use the SET command to initialize the G1JOB variable and
the DD_environment variables. DD_environment variables associate the system file names used by
the CODE-1 Plus programs with the files you want processed in your job. The system file names
used by CODE-1 Plus are listed at the beginning of this chapter.
The job file also contains a RUN command that specifies the CODE-1 Plus program to be invoked.
Naturally, it is important to run the correct program.
Release 4.1.0
59
User’s Guide - Open Systems
Using The Tutorial
Creating a New Job File
The easiest way to create a new job file is to modify an existing one, such as the SAMPLE.BAT file
provided on your installation media. To create a new job file, you can use the following two methods:
1. Use the File Manager to copy bin\SAMPLE.BAT to bin\MYJOB.BAT.
2. Select the Edit Job File icon and specify MYJOB as the file to edit.
OR
Select the Edit Job File icon.
3. Specify the name of a new job file.
4. Paste in bin\SAMPLE.BAT.
Italicized text indicates information you may need to modify. In addition, it is always a good idea to
change the opening comments to describe the batch job.
Editing a Job File
You can edit job files by invoking the Edit Job File icon or by invoking your text editor and editing the
job file in the bin directory. Ensure that the job file has the extension .BAT and the job name is unique
among the batch files in the directory.

This program accepts the G1EDIT environment variable as the name of the editor you prefer
to use. If G1EDIT is not defined, NOTEPAD is used as the editor.
Step 2. Edit/Save Parameter Files
Parameter files use the .PRM extension. Pitney Bowes provides five example parameter files with
the product:
•
•
•
•
•
SAMPLE.PRM—parameters for the batch driver program of the Installation Verification
Procedure (IVP)
SAMGRW.PRM—parameters for the Generalized Report Writer (G1G001) program for the IVP.
SAMZ4C.PRM—parameters for the batch driver program for the Z4CHANGE Option product’s
IVP.
RDBUNLD.PRM—parameters for the reduction database program C1PDR.
SAMDBPRT.PRM—parameters for the database print program (C1PDBPRT).
Creating a New Parameter File
The easiest way to create a new parameter file is to modify an existing one, such as the file
SAMPLE.PRM. To create a new parameter file, you can use the following two methods:
1. Use the File Manager to copy data\SAMPLE.PRM to data\MYJOB.PRM.
2. Select the Edit Parm File icon and specify MYJOB as the file to edit.
OR
3. Select the Edit Parm File icon.
4. Specify the name of a new job file.
5. Paste in data\SAMPLE.PRM.
Release 4.1.0
60
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
Editing a Parameter File
You can edit parameter files by invoking the Edit Parm File icon or by invoking your text editor and
editing the parameter file in the DATA directory. Ensure that the parameter file has the extension
.PRM and the job name is unique among the batch files in the directory.

This program accepts the G1EDIT environment variable as the name of the editor you prefer
to use. If G1EDIT is not defined, NOTEPAD is used as the editor.
Step 3. Run a Job
To run a batch job you can use the Run CODE-1 Plus Job icon. The icon prompts you for the name
of the job you want to run, and then runs the job. When the job completes running, you are prompted
to press a key to continue so that the window is not refreshed before you read any error messages.
To run a batch job (C1BM00):
1. Double-click on the Run CODE-1 Plus Job icon.
2. Once you enter a job name, the Run CODE-1 Plus icon:
a. Runs the VB script C1PRUN.VBS which creates a randomly named temporary batch file and
b. Transfers control of the job to the temporary file.
The temporary file:
– Calls the bin\SETUP.BAT file to initialize the CODE-1 Plus environment
– Calls the bin\jobname.BAT file to tailor the environment to the job requested and run the
C1BM00 program
– Pauses the process so you can see any error messages, and then deletes the temporary
job file.
Printing Reports
The reports generated by CODE-1 Plus, such as the USPS Form 3553, are created in ASCII text
and rich text format (RTF). You can use the Windows Wordpad accessory to view and print reports
created with the RTF extension.
TIP: Wordpad does not recognize page breaks. To print with page breaks, use a word processor that
supports page breaks.
Step 7: Read the Output
When you run a job, CODE-1 Plus automatically generates two report files: PRNTXLG and
PRNTRPT. These report files contain the CODE-1 Plus reports created as a result of your job
execution.
•
•
PRNTXLG — Contains only one report, the Execution Log Report. This report always prints.
PRNTRPT — Contains up to 15 different reports. The following reports will be output to this file
automatically:
– Parameter Record List Report
– Control Totals Report
– Address-Match Execution Statistics Report
– USPS Form 3553 (this will only be generated for jobs run with a valid CASS configuration).
The other reports that are located in this file are the reports you defined in the previous step with
your REPORT parameter. So, your sample job will produce the four reports listed above and the
following report you defined in your REPORT parameter:
–
Release 4.1.0
Processing Summary by State Report
61
User’s Guide - Open Systems
Using The Tutorial
You will also generate the following output files:
•
•
•
C1BMCOK for the matched and coded records
C1BMNCO for records with valid ZIP Codes with no matched address
C1BMIZP for records with invalid ZIP Codes.
Coded Output File
The following pages show the coded output files generated by this sample job. For information about
CODE-1 Plus reports, see Generating CODE-1 Plus Reports in Chapter 5 on page 117.
Record Positions 1 through 135
Release 4.1.0
62
User’s Guide - Open Systems
Chapter 3: Getting Started With Your Batch Job
Using The Tutorial
Record Positions 136 through 274
Uncoded Output File
Record Positions 1 through 115
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+
TM059
BOZ SCAGGS
BOX 8181 STATION B
37202
TM049
AL STEWART
2615 HICKORY VALLEY RD
37205
TM059
PETER WHITE
1443 CELINA DR
37207
Record Positions 216 through 274
....2....+....3....+....4....+....5....+...6....+....7....+....8....+....9....+....0
M
4
0
M
2
0
M
2
0
The return codes indicate that
CODE-1 Plus could not code these
addresses.
Record Positions 1 through 125
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....0....+....1....+....2....+
TM019
JIMMY BUFFET
PIRATES OVER FORTY
5525 GRANNY WHITE PK
35589
Record Positions 180 through 274
8....+....9....+....0....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+.
PIRATES OVER FORTY
S
2
O
Return codes indicate an invalid ZIP Code.
Release 4.1.0
63
User’s Guide - Open Systems
Using The Tutorial
Release 4.1.0
64
User’s Guide - Open Systems
Getting Started With
Interactive Processing
In this chapter:















Getting Started With the Interactive System . . . . . . . . . . . . . . . . .66
CODE-1 Plus Interactive System Screen . . . . . . . . . . . . . . . . . . . .68
Address Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Database Inquiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
An Example Work Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Interactive Screen Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Function Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Address Matching Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Database Inquiry Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Screens that Support Site Customization . . . . . . . . . . . . . . . . . .107
Database Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Screens that Support Site Customization . . . . . . . . . . . . . . . . . .107
Database Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Customization File Administration . . . . . . . . . . . . . . . . . . . . . . . .112
Batch Uncoded Records Interface (G1CPBNC). . . . . . . . . . . . . .113
4
Getting Started With the Interactive System
Getting Started With the Interactive System
This chapter describes the CODE-1 Plus interactive address matching and database inquiry
functions. The CODE-1 Plus Interactive System is an environment where you can match and correct
addresses online through one easy-to-use screen. This screen enables you to use the two main
functions, Address Matching and Database Inquiry, and a secondary function that enables you to
correct uncoded records. (You must implement the user-exit G1CPBNC to correct uncoded records
interactively.) To implement the user-exit G1CPBNC, refer to "Correcting Uncoded Records” on
page 77.


To minimize maintenance, the interactive screens in this chapter do not display the database
version and the date stamp. We also use “__ of __” to represent the screen currently
displayed, instead of “1 of 62,381,” for example.
The CODE-1 Plus Interactive System does not support Auxiliary File/EWS processing.
Address Matching Function
The interactive address matching function enables you to:
•
•
•
•
Match a single input address against the master file
Analyze return codes to determine actions that were taken to attempt a match
Detect the types and quantities of problems encountered in an input address
Control the closeness (“tightness” or “looseness”) of address matches
For each match attempt, CODE-1 Plus displays return codes that indicate the success or reason for
failure of the attempt. You can view these return codes in code or expanded English format.
In addition to the return codes, CODE-1 Plus shows you, for each match attempt, parsed address
elements and Delivery Sequence Footnotes (DSF2 codes).
Geographic Coding
The address matching function provides access to the Geographic Coding Information screens.
Please refer to the User’s Guide that you received with your Geographic Coding software for details
about Geographic Coding Plus.

To access the Geographic Coding Information screens, you must purchase and install the
Pitney Bowes Geographic Coding Plus software.
Database Inquiry Function
The database inquiry function lets you browse the contents of the CODE-1 Plus database. Using this
feature, you can look up houses, apartments, and firms on a given street, in a particular city. You can
display and analyze the following information for each city in the CODE-1 Plus database:
•
•
•
•
Release 4.1.0
City name
Cities within a state
Cities within a ZIP Code
ZIP Codes in a city
66
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Getting Started With the Interactive System
•
•
•
•
•
•
Streets within a city
Streets within a locality
Streets within a ZIP Code
House ranges on a street
Apartment ranges on a street range
Firm names within a street range
Database Expiration and Incompatibility
The interactive matcher ceases to function in accordance with the Domestic Mail Manual (DMM)
A960 matrix. The interactive system inquiry area, however, remains available even after the
interactive matcher expires. In this case, the following message will be displayed on the prompt line
above the function key descriptions:
CODE-1 Plus DATABASE IS EXPIRED
Alternatively, if the CASS cycle date has passed, the following message displays at the prompt:
CODE-1 Plus DATABASE CASS CYCLE IS EXPIRED
The interactive system validates the release of the database against the release of the software. If
the releases are incompatible, the following message will appear when you enter the CODE-1 Plus
interactive transaction code:
CODE-1 Plus PROGRAM ERROR, RETURN CODE=ICPT INCOMPATIBLE
DATABASE FOUND
In this case, neither the inquiry nor the match process will be accessible.
Expiration of Delivery Point Validation (DPV) Processing
The DPV option will stop working at the end of the fourth month from the release of the database.
If you have an expired DPV database, this message will appear:
DELIVERY POINT VALIDATION SUPPRESSED DUE TO DATABASE
EXPIRATION DATE CHECK
Correcting Uncoded Records Function
When you run a batch job in CODE-1 Plus, you can generate an uncoded records output file
(C1BMNCO). This file contains records with valid ZIP Codes, but for some reason, the records did
not match against the database. With a supplied user-exit, you can correct these records in the
CODE-1 Plus Interactive screen. You display an uncoded record in the input area, correct the
record, write the corrected record to a corrected output file, and then display the next uncoded
record. For more information, refer to "Correcting Uncoded Records” on page 77.
Navigation Function
The navigation function coordinates the match and inquiry functions to position the inquiry portion of
the split screen format as close as possible to the point of match failure on a non-matched address.
Navigation does not change the display on a matched address; it is geared to react to the matcher’s
non-space return codes to drill down into the database as far as possible.
Release 4.1.0
67
User’s Guide - Open Systems
CODE-1 Plus Interactive System Screen
For example, a house range mismatch generally will result in the inquiry half of the screen being
positioned at the house range on the street entered on the top half of the screen. If the street is
misspelled, however, the position will be at the same street name entered on the match portion of
the screen. The purpose of this process is to get as close as possible to a correct address without
having to drill through apparently correct levels of the database.
The Navigate (Nav) toggle command turns navigation on or off. Navigation is only available in split
screen processing (since a non-matched address is required to activate the function) and can be
used in concert with the UR (batch not coded) function. For more information on the commands
available in interactive processing, refer to "Command Field” on page 78.
CODE-1 Plus Interactive System Screen
The Interactive CODE-1 Plus System screen includes the address matching function on top and the
database inquiry function on the bottom.
Function
Keys
Database
Command
Field
Input
Match Fields
Results
CODE-1 Plus Coding System
-------------------------------------------------------------------------Firm Name:
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr:
Correct ZIP Y
City, ST:
Mixed Case: Y
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
-------------------------------------------------------------------------Command:
Nav DPV
__ of __
City Information
LN City
State
ZIP Range
Type
URB Unique-ZIP
1 A A R P
CA
90848
V
2 A A R P INS
PA
19187
V
Y
3 A A R P PHARMACY
CA
90848
V
Y
4 A A R P PHARMACY
CT
06167
V
Y
5 A C NIELSEN
TX
79966-79974
V
Y
6 A H MCCOY FEDERAL BLDG
MS
39269
V
7 A M F GREENSBORO
NC
27425
V
8 A M O R C
CA
95191
V
Y
The match settings have been changed.
1=Help
2=ZC
3=Quit
4=SC
5=CZ
8=Down
9=Mat
10=Flip
Interactive CODE-1 Plus System Screen Components
You can enter an address and attempt a match, or display database information.
•
•
•
•
•
Release 4.1.0
Input Fields—Enter the address that you want to match.
Match Results—CODE-1 Plus returns the standardized address.
Command Field—Enter screen commands.
Database Inquiry—The first database inquiry screen displays an alphabetical list of cities in the
database.
Function Keys—Access other functions for address matching or database inquiry components.
68
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Address Matching
Online Help Facility
The CODE-1 Plus Interactive System has an extensive help facility. Help is available on three levels:
•
•
•
Context sensitive help
System Tutorial
List of Commands
To access the online help facility from any screen in the Interactive CODE-1 Plus System:
1. Enter Help in the Command field or press function key F1 or the Help key.
2. The online help facility displays a menu, and you can choose to see the tutorial, a list of all valid
commands, or context sensitive help on the screen that was displayed when you accessed the
online help facility.
3. To exit the help facility, press function key F10 or enter X in the Selection field.
Address Matching
To match an address, follow the steps below.
1. Move your cursor to the top of the screen using the Tab key, arrow keys, or
Field Exit key.
2. Enter any firm name, primary and secondary address lines, city, state, and/or ZIP Code.
3. Press Enter.
4. CODE-1 Plus searches the database to find an address that matches the one you entered.
5. If a match is found, the standardized address line and the standardized city/state/ZIP Code line
appear for you on the top half of the screen.
6. You can display other match result information by entering RC (return codes) or MAT in the
Command field, or pressing F9.
Scrolling Through the Match Results Screens
There are six screens of match results in the CODE-1 Plus Interactive System. Each screen shows
you different information about your match attempt. These screens are the following:
•
RC—Return Codes screen
•
•
•
•
•
DS—Delivery Sequence Footnotes2 screen
PE—Parsed Elements screen
ME—Multiple Elements screen
ST—Statistics screen
DI—Miscellaneous Information/Base Address screen.
Release 4.1.0
69
User’s Guide - Open Systems
Database Inquiry
You can access these screens from anywhere in the system by typing the screen’s 2-character code
in the Command field. You can display these screens sequentially in the order shown below with the
DOWN command or F8 or ROLL UP keys and the UP command or the F7 or ROLL DOWN keys.
Sequential Order of CODE-1 Plus Interactive System Screens
In addition to the six match results screens, there are three other screens that support the address
matching function. These screens follow:
•
•
•
•
ER—Expanded Return Codes screen shows you English descriptions of the return codes.
MS—Match Settings screen enables you to change the settings for the match algorithms to
control the strictness of the match attempt.
GC—Geographic Codes screen enables you to see Geographic Coding Results for your address
(if the Geographic Coding System is installed).
DB—Database Commands displays the information for your database, including software
release and the expiration date of your databases.
To view one of the above screens, type its 2-character code in the Command field and press the
Enter key.

If you change to one of these match results screens, and attempt another match, the Return
Codes screen is not re-displayed; the screen that is currently shown remains until you move
to another screen. To return to the Return Codes screen, enter RC in the Command field.
Database Inquiry
The bottom half of the Interactive CODE-1 Plus screen contains the first database inquiry screen.
The database inquiry function supports the following screens:
•
•
•
•
•
•
•
•
•
•
•
AH—Apartments at a House Range
CS—Cities in a State
CZ—Cities in a ZIP Code
CI—City Information
FM—Firms on a Street
HS—Houses on a Street
SC—Streets in a City
SL—Streets in a Locality
SZ—Streets in a ZIP Code
GEO—Geographic Coding Interface
ZC—ZIP Codes in a City.
To make any database inquiry screen take up all of the space on the screen:
1. Type FLIP in the Command field or press function key F10.
More lines are available to display additional information stored in the database.
2. To restore the screen to the original display, enter FLIP again in the Command field.
Release 4.1.0
70
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Database Inquiry
Navigating Through the Screens
You can access the CI, CS, CZ, and SZ database inquiry screens from anywhere in the system by
typing the screen’s 2-character code in the Command field. Note that to access:
•
•
•
The Cities in a State screen, type CS followed by a 2-character state code in the Command field.
The Cities in a ZIP Code screen, type CZ followed by a 5-digit ZIP Code (or 2-digit line number if
you are on Cities in a State or database screens).
The Streets in a ZIP Code screen, type SZ followed by a 5-digit ZIP Code (or 2-digit line number
if you are on Cities in a ZIP Code screen).
You can scroll through data on a specific screen as shown in the figure below with the DOWN
command or F8 or ROLL UP keys and the UP command or the F7 or ROLL DOWN keys.
Screen Order in CODE-1 Plus Interactive System
Moving to a Line on a Screen
To position the data on the screen to a specific spot alphabetically:
1. Type an L (short for locate) in the Command field.
2. Then type the search string and press the Enter key.
For example, if you wanted to position the list to Lanham while displaying a Cities screen, you
would enter L LANHAM in the Command field. The first city that starts with the letters L-A-N-HA-M would become the first city displayed.
Release 4.1.0
71
User’s Guide - Open Systems
Database Inquiry
Displaying Data about a Database Entry
To display data for any database line on the screen, use one of the following methods. All methods
produce the same result.
•
First, in the Command field, you can type the 2-character command and the appropriate line
number. For example, if the city of Lanham, MD is the second city displayed, and we want to
display all of the streets in Lanham, MD, we would:
Type SC 2 (streets in the city on line 2) in the Command field.
•
Most 2-character screen abbreviations (like SC above) are assigned to function keys on the
current screen. Refer to the display line on the bottom of the screen for the corresponding
function keys. If you want to use a function key to access data instead of typing the 2-character
code, you can use one of the two methods described below. To display the streets in Lanham,
Maryland again:
Type 2 in the Command field and press the function key F4.
All the streets in the city of Lanham appear.
or
Position the cursor on the second line of the display (the line with Lanham, MD) and press F4.
Querying the Database
The following steps clarify the concepts presented above.
1. Start at the first database inquiry screen.
2. Enter FLIP in the Command field and press Enter.
3. Enter L LANHAM in the Command field. The screen changes to display only database inquiry
without address matching.
4. Enter SC 2 in the Command field and press Enter.

You could also enter just SC. The line number defaults to 1, if no line number is entered
in the Command field.
The cursor moves to the Streets in a City screen for the city on the first line of the display (in this
case, Lanham MD).
5. Enter DOWN in the Command field and press Enter or press F8 to see the next display of
streets in Lanham, MD. The screen appears with all the streets in Lanham, Maryland.

Release 4.1.0
To combine a display command and a locate command, you can enter the display command,
followed by the line number for the display command, followed by the locate string. For
example, if your screen displayed the cities in the database, positioned with LANHAM, MD as
line 4, and you wanted to see all of the streets in LANHAM starting with PARLIAMENT PL,
you would enter SC 4 PARLIAMENT. The Streets in a City screen would be displayed, and
PARLIAMENT PL would be the second street displayed.
72
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
An Example Work Session
An Example Work Session
The remainder of this chapter is devoted to an example of how to use the interactive functions to
correct problem addresses. The first step is to access the interactive matching function and enter an
address. The address will not match, so we use the database inquiry to see if our “detective” skills
enable us to find the address. Once we find an address, we return to the address matching function
to look at the results of a match.
The following address is used as input:
LOCUS INC
2560 HUNT
JEFFERSON VA
You will follow the steps below to correct your input address:
1. Access the CODE-1 Plus Interactive System.
2. Attempt to match a questionable address using different matching algorithms.
3. Browse the postal database to determine the correct address.
4. Successfully match the corrected input address, thereby producing a ZIP + 4 Code, parsed
address elements, and output return codes.
5. Display geographic codes for the address.

To access the Geographic Coding System screen, you must have purchased and
installed the Pitney Bowes Geographic Coding Plus.
Step 1. Accessing the Interactive System
1. To start the CODE-1 Plus Interactive system:
•
•
•
In a Windows environment, go to Programs/CODE-1 Plus/Matcher-Inquiry.
In a Unix environment, type the following command: bin/runonline.
For CICS or IMS users, we start our session at a blank screen.
2. Enter G1CP to invoke the CODE-1 Plus Interactive System.
3. The CODE-1 Plus Interactive System appears on your screen.
Release 4.1.0
73
User’s Guide - Open Systems
An Example Work Session
Step 2. Matching an Address
At this point, you can enter an address for a match or search the database for specific information.
For the example, we enter an address match attempt.
1. Type the address in question and press Enter.
CODE-1 Plus Coding System
-----------------------------------------------------------------------Firm Name: LOCUS INC
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: 2650 HUNT
Correct ZIP: Y
City, ST: JEFFERSON VA
Mixed Case: Y
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
-----------------------------------------------------------------------Command:
Nav DPV
__ of __
City Information
LN City
State
ZIP Range
Type
URB Unique-ZIP
1 A A R P
CA
90848
V
2 A A R P INS
PA
19187
V
Y
3 A A R P PHARMACY
CA
90848
V
Y
4 A A R P PHARMACY
CT
06167
V
Y
5 A C NIELSEN
TX
79966-79974
V
Y
6 A H MCCOY FEDERAL BLDG
MS
39269
V
7 A M F GREENSBORO
NC
27425
V
8 A M O R C
CA
95191
V
Y
The match settings have been changed.
1=Help
2=ZC
3=Quit
4=SC
5=CZ
8=Down
9=Mat
10=Flip
2. CODE-1 Plus attempts to match the address, but is unsuccessful (no match address or City/
State/ZIP Code line is displayed). Next, review why a match was not found.
3. To display the Return Codes screen, type RC in the Command field and press Enter. CODE-1
Plus codes the example address. Return codes appear on the screen.
4. To change to the database inquiry function, type INQ in the Command field and press Enter.
Release 4.1.0
74
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
An Example Work Session
Step 3. Querying the Database
The lower half of the screen changes and displays the list of cities in the database.
1. In the Command field, type CS VA JEFFERSON and press Enter. The list of cities in Virginia is
repositioned with Jefferson Manor, ZIP Code 22303 at the top of the list. This seems close
enough to our original address that it bears further investigation. At this point, Jefferson Manor is
a secondary city name. The primary city (i.e., the USPS-preferred city name) is obtained through
the ZIP Code.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm Name: LOCUS INC
Firm: M D/Suf:M
Secondary Addr:
St: M Vcity:S
Primary Addr: 2560 HUNT
Correct ZIP Y
City, ST: JEFFERSON VA
Mixed Case: Y
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Y
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
------------------------------------------------------------------------------Command: cz
Nav Off
__ of __
Cities in Virginia
LN City
State
ZIP Range
Type
URB Unique-ZIP
1 JEFFERSON MANOR
VA
22303
S
2 JEFFERSONTON
VA
22724
P
3 JENKINS BRG
VA
23399
P
4 JENKINS BRIDGE
VA
23399
P
5 JERSEY
VA
22481
P
6 JETERSVILLE
VA
23083
P
7 JEWELL RIDGE
VA
24622
P
8 JEWELL VALLEY
VA
24622
S
1=Help
2=ZC
3=Quit
4=SC
5=CZ
6=Back
7=Up
8=Down
9=Mat
10=Flip
2. In the Command field, type CZ and press Enter.The Cities in ZIP Code screen appears. Notice
that there are two cities for this ZIP Code. Alexandria has a city type of “Primary,” and Jefferson
Manor has a city type of “Secondary.” Alexandria is the USPS-preferred city name for the ZIP
Code 22303.
3. Now, see if there is a street called Hunt in this ZIP Code. To display all of the streets in the ZIP
Code range for the first city (Alexandria), in the Command field type SZ HUNT and press Enter.
4. The Streets in ZIP Code screen appears so that “HUNT” would have been the first street on the
screen if it existed. Notice that there is no Hunt Street, but there is a Huntington Avenue. This
bears further investigation.
5. In the Command field, type HS 3 2560 and press Enter.
6. The list is positioned so that the house range containing 2560 is at the top of the list. Notice that
2560 Huntington Avenue is a high rise house type.
7. In the Command field, type FM 3 and press Enter.
8. The Firms on a Street screen appears. The screen displays Locus Inc. located at 2560
Huntington Avenue, apartment number 302. The search is complete.
Release 4.1.0
75
User’s Guide - Open Systems
An Example Work Session
Step 4. Matching an Address—Second Attempt
Now that there is an accurate address, enter it interactively and look at the match return codes. The
first thing to do is change the matching algorithm settings to “tight” from the default of medium.
1. In the Command field, type MS and press Enter.
2. The Match Settings screen appears. Type T for each of the matching algorithms and press
Enter. The Match Settings screen disappears, and the Firms in a Street screen appears again. A
message appears at the bottom of the screen telling you that the settings were changed.
3. Type the correct address matching fields and press Enter.
4. CODE-1 Plus matches the address and shows the matched address.
5. To review the return codes for the match, in the Command field, type RC and press Enter.
6. The Return Codes screen appears. Scroll through to see the other match results screens. In the
Command field, type DOWN or press F8.
The Delivery Sequence Footnotes screen displays, showing DSF codes that applied to this
match attempt.
7. Continue to type DOWN in the Command field, or press F8.
The Parsed Elements screen appears.
8. Type DOWN in the Command field, or press F8.
The Multiple Elements screen appears.
9. Type DOWN in the Command field, or press F8.
The Statistics screen appears.
10. Type DOWN in the Command field, or press F8.
The Miscellaneous Address Values screen appears.
11. To exit from the Interactive System, type QUIT in the Command field or press F3.
Step 5. Geographic Coding
In addition to address matching, you can return geographic coding information about the address. If
you enter a match attempt, and then access the Geographic Coding Interface screen, the
geographic match results appears for the ZIP Code and ZIP + 4 Code from the match attempt. If you
do not enter a match attempt before accessing the Geographic Coding Interface, enter the ZIP Code
and ZIP + 4 Codes directly on the screen.

To access the Geographic Coding interface screen, you must have purchased and installed
Pitney Bowes's Geographic Coding Plus.
1. In the Command field, type GEO and press Enter. The first Geographic Coding Interface screen
appears.
2. To display the second Geographic Coding Interface screen, press F8. The second Geographic
Coding Interface screen appears.
3.
Release 4.1.0
Press F7 once to return to the top of the Geographic Coding Interface screen, and then press
F10 in the Command field.
76
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Correcting Uncoded Records
Correcting Uncoded Records
If you implement the G1CPBNC user-exit program, you can correct uncoded records from the
G1CPBNC output file. To correct uncoded records using the CODE-1 Plus Interactive system, use
two commands: UR (User Read) and UW (User Write). These commands are described below:
To correct uncoded records from the C1BMNCO output file, follow the steps below:
1. Start at the CODE-1 Plus Interactive System screen.
2. Type UR in the Command field.
An uncoded address appears in the input area.
3. You can use any address matching or database inquiry functions necessary to find a match for
this address.
4. Once the uncoded address is matched to the database and corrected, type UW in the
Command field. The corrected address is written to an output file.
5. Repeat steps 2 through 4 until all the records in the uncoded records output file are corrected.

Release 4.1.0
For information on the G1CPBNC program, refer to "Batch Uncoded Records Interface
(G1CPBNC)” on page 113.
77
User’s Guide - Open Systems
Interactive Screen Reference
Interactive Screen Reference
This section provides a reference for the CODE-1 Plus interactive screens. Each screen is
presented, along with its fields and function keys.
Command Field
There is one field that appears on every screen in the Interactive CODE-1 Plus System: the
Command field. This field enables you to move gracefully through address match attempt results as
well as database inquiry data. The following table lists all of the commands that you can enter in the
Command field. In addition, the table lists alternate actions you can take to accomplish the same
results as the command. For each command listed, the underlined portion is all that is required for
entry (you can enter the entire command string, however).
Valid Entries in the Command Field (Part 1 of 5)
Command
Description
Alternate Method
General Commands
BOTTOM
Move to the bottom of the data. In the address
match function, this command brings you to the
Base Address/Dropped Information screen. In
the database inquiry function this command
repositions the list of data to the last entry.
None.
DOWN
Move down one display of data. In the address
match function this command moves you to the
next match results screen. In the database
inquiry function this command repositions the list
of data down one display.
NOTE: If the cursor is placed on a specific line,
“DOWN” will result in that line appearing as the
first displayed line on the screen.
Press F8
F8 with a number between
1 and 9998 on the
command line will scroll
down that number of lines.
EXTEND
Allows you to override database expiration, so
you can match interactively with an expired
database.
NOTE: You must use the “EXTEND” command
each time an expired database is identified by
the software initialization.
None.
FLIP
Flip the screen from the combined functions to
the zoomed database inquiry function or from
the zoomed database inquiry function to the
combined functions, whichever is appropriate.
Press F10.
HELP
Access the online help system.
Press F1.
Right
Scroll right to see more of the firm/alias name on
the Houses on a Street screen.
None.
LEft
Scroll left to see first part of firm/alias name on
the Houses on a Street screen.
None.
QUIT
Exit from the Interactive CODE-1 Plus System.
Press F3.
TOP
Move to the top of the data. In the address match
function this command brings you to the Return
Code screen. In the database inquiry function,
this command repositions the list of data to the
first entry.
None.
Release 4.1.0
78
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Interactive Screen Reference
Valid Entries in the Command Field (Part 2 of 5)
Command
UP
Description
Alternate Method
Move up one display of data. In the address
match function this command moves you to the
previous match results screen. In the database
inquiry function this command repositions the list
of data up one display.
NOTE: If the cursor is placed on a specific line,
“UP” will result in that line appearing as the last
displayed line on the screen.
Press F7
F7 with a number between
1 and 9998 on the
command line will scroll up
that number of lines.
Customizing Interface Commands
ADMIN
Go to the Administration Sign-on screen. Can
be called from the split match/inquiry or full (flip)
screens.
None.
NAVIGATE
Toggle navigation mode on and off. Positions
inquiry screen as close as possible to the lowest
level of match success on a non-matched
address.
None.
DPV
Toggle DPV mode on and off. When turned on
you will be able to do Delivery Point Validation
processing.
On the Interactive
Customization Screen, you
can enter blank or x under
Perform DPV Process.
DPVKEY
Displays the Seed Code of the DPV seed record
encountered which disabled DPV
processing.You will need to be provide this Seed
Code to Pitney Bowes before you can receive
another permanent License Management key to
continue your DPV processing.
None.
DPVZAP
Initializes the customization area that contains
the Seed Code. This does NOT inhibit DPV
processing.
None.
LOT
Toggle LOT mode on and off. When turned on
you will be able to do Line of Travel matching.
LTO
LTO
Toggle LOT mode on and off. When turned on
you will be able to do Line of Travel matching.
LOT
RDI
Toggle RDI mode on and off. When turned on
you will be able to do Residential Delivery File
matching
RDI
Database Inquiry Command
AH <line number>
Move to the Apartments at a House Range
screen for the house range displayed on line
<line number>.
This command is only valid from the Houses on
a Street screen.
Type the desired line
number in the Command
field and press F4.
or
Position your cursor on the
desired line and press F4.
ALIAS <line number>
Display the base street name for the alias street
listed on line <line number>.
For the Apartments at a House Range screen
and Firms on a Street screen only.
Type the desired line
number in the Command
field and press F2.
or
Position your cursor on the
desired line and press F2.
Release 4.1.0
79
User’s Guide - Open Systems
Interactive Screen Reference
Valid Entries in the Command Field (Part 3 of 5)
Command
Description
Alternate Method
BACK
Return to the previous database inquiry level.
(For example, if you were at the Streets in a City
screen, this command would take you back to
the Cities in the Database screen.)
Press F6.
CI <city>
Go to the City Information screen.
None.
CS <state abr.>
Go to the Cities in a State screen for the two
character state abbreviation that is entered as
<state abr.>.
None.
CZ <line number>
or
CZ <ZIP Code>
Move to the Cities in a ZIP Code screen for the
ZIP Code that is displayed on line <line
number>.
or
Move to the Cities in a ZIP Code screen for the
ZIP Code entered as <ZIP Code>.
Type the desired line
number in the Command
field and press F5.
or
Position your cursor on the
desired line and press F5.
DB
Display the information for your database,
including software release and the expiration
date of your databases.
None.
FM <line number>
Move to the Firms on a Street screen for the
street name or house range displayed on line
<line number>.
Type the desired line
number in the Command
field and press F5.
or
Position your cursor on the
desired line and press F5.
This command is only valid from the Houses on
a Street, or Apartments at a House Range
screens.
HS <line number>
Move to the Houses on a Street screen for the
street name that is displayed on line
<line number>.
This command is only valid from the Streets in a
City or Streets in a ZIP Code screens.
Type the desired line
number in the Command
field and press F4.
or
Position your cursor on the
desired line and press F4.
LOCATE <string>
Generally positions the database inquiry to the
first entry that starts with <string>.
NOTE: If there are multiple cities with the same
name, they will be listed by finance number,
highest to lowest.
None.
MATCH
Go to the address match function. (The match
results screen that appears when you access
the database inquiry function re-appears.)
Press F9.
SC <line number>
Move to the Streets in a City screen for the city
name that is displayed on line <line number>.
This command is only valid from the Cities in the
Database screen.
Type the desired line
number in the Command
field and press F4.
or
Position your cursor on the
desired line and press F4.
SL <line number>
Display all streets in the city locality displayed on
line <line number> on the Streets in a City
screen.
Type the desired line
number in the Command
field and press F4.
or
Position your cursor on the
desired line and press F4.
Release 4.1.0
80
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Interactive Screen Reference
Valid Entries in the Command Field (Part 4 of 5)
Command
Description
Alternate Method
SZ <line number>
Move to the Streets in a ZIP Code screen for the
ZIP Code that is displayed on line <line
number>.
This command is only valid from the Cities in a
ZIP Code screen.
Type the desired line
number in the Command
field and press F4.
or
Position your cursor on the
desired line and press F4.
SZ <ZIP Code>
Move to the Streets in a ZIP Code screen for the
ZIP Code entered as <ZIP Code>
None.
ZC <line number>
Display all ZIP Codes for the city locality
displayed on line <line number> on the City
Information and Cities in a State screens.
Type the desired line
number in the Command
field and press F2.
or
Position your cursor on the
desired line and press F2.
Address Match Commands
INQUIRY
Go to the database inquiry function. If you had
previously used the database inquiry function
during this session, the screen that appeared
when you left the database inquiry function
reappears.
Press F9.
AS
Display address stack entries for the address
you entered.
None.
ASM
Turn on or off All Street Matching function.
DB
Display current CODE-1 Plus database vintage
and expiration date.
None.
ESM
Turn on or off Enhanced Street Matching
function.
None
SUITE
Invokes SuiteLink processing.
None
LACS
Invokes LACSLink processing.
None
LTO
Invoke Line of Travel processing.
None
RC
Go to the Return Codes screen.
None.
DS
Go to the Delivery Sequence Footnotes screen.
None.
PE
Go to the Parsed Elements screen.
None.
ME
Go to the Multiple Elements screen.
None.
ST
Go to the Statistics screen.
None.
DI
Go to the Miscellaneous Address Values screen.
None.
ER
Go to the Expanded Return Codes screen.
None.
GC
Go to the Geographic Coding Information
screen.
This command is only valid if you have
Geographic Coding Plus installed.
None.
Release 4.1.0
81
User’s Guide - Open Systems
Function Keys
Valid Entries in the Command Field (Part 5 of 5)
Command
Description
Alternate Method
MS
Go to the Match Settings screen, and unprotect
the match control fields on the Address Match
screen.
Press F4.
REFRESH
Clear all fields on all address match function
screens.
Press F5.
Using Concatenated Commands
You can concatenate commands at the command line or the initial G1CP transaction in CICS. A
combination of the primary screen commands CI, CS, CZ, or SZ; a locate command; and “FLIP” can
be concatenated, or delimited by the semicolon (;) character. From a blank CICS screen, the
following string would produce a full screen display positioned at “Baltimore” on a “cities in state”
screen (with the state of Maryland):
G1CP, CS MD;L BALTIMORE;FLIP
This command is separated from the transid by a comma, and semicolons delimit the portions of the
command string. From the command line on any split screen, the same result would be achieved by
the following command:
CS MD;L BALTIMORE;FLIP
If this command were entered on a full inquiry screen display, the final result would be a split screen
(match and inquiry) display.
Function Keys
There are certain environmental considerations for the function keys that appear on the screens in
this chapter. These screens are shown as they appear under CICS, IMS, or Unix.
Function Keys (Part 1 of 2)
Function Key
Name
Description
F1
HELP
Obtain online help.
F2
ZC
List ZIP Codes in City screen.
ALIAS
Show the base street name for the house range shown.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F4
SC
Go to the Streets in a City screen.
MS
Go to the Match Settings screen.
SZ
Go to the Streets in a ZIP Code screen.
AH
Go to the Apartments on a Street screen.
HS
Go to the Houses on a Street screen.
CZ
Go to the Cities in a ZIP Code screen.
F5
Release 4.1.0
82
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Function Keys
Function Keys (Part 2 of 2)
Function Key
Name
Description
RE
Refresh (erase) all of the input and output data from the
screen.
FM
Go to the Firms on a Street screen.
SAVE
Save current entries after validation. Remain on screen after
save.
GEO
Go to the Geographic Coding Interface (you must have
purchased and installed Geographic Coding Plus
separately).
BACK
Return to the previous screen.
F7
UP
If the top of the list of DSF2 codes is displayed, return to the
previous match results screen. If the top of the list of DSF2
codes is not currently displayed, page up the list of codes.
F8
DOWN
Go to the next screen.
F9
MAT
Go to the Return Codes screen.
INQ
Go to the database inquiry function.
RESET
Restore screen values to current database entries (at last
update to customization file).
FLIP
Expand the database inquiry function to fill the entire screen.
EXIT
Return to the previous screen without modifying the match
settings.
VERIFY
Validate the fields. If the validation is unsuccessful, the
screen is redisplayed, an error message is displayed, and
the first field in error is indicated.
F6
F10
Enter
If you are a Unix user with a terminal that does not have function keys, you must select a function
using three key strokes, as follows:
1. Press the ESCAPE key.
On some terminals, you must combine the CNTRL key with the left bracket [ key.
2. Press the numeric digit of the function.
For example, for function key 10, you must type 1-0.
3. Press the Enter or RETURN key.
On some terminals, you must combine the CONTROL key with the M key.
Release 4.1.0
83
User’s Guide - Open Systems
Address Matching Screens
Address Matching Screens
The screens shown in this section support the address matching function. The screens are listed in
alphabetical order.
Entering the name of a key in the Command field is the same as pressing the function key (for
example, to access online help, you could either press F1 or, in the Command field, type HELP and
press Enter.)
Address Match Screen
The Address Match screen occupies the top half of the physical screen in the Interactive CODE-1
Plus System, unless you have entered the FLIP command to cause the database inquiry function to
be displayed on the entire physical screen. Use this screen to enter an input address for CODE-1
Plus to match against the database. CODE-1 Plus returns the matched, standardized address.

If you attempt to use the DPV option without having a license to do so, the following message
will appear at the bottom of this screen:
or
DPV UNAVAILABLE - NO LICENSE FOUND
DPV UNAVAILABLE - LICENSE INVALID.
Address Match Screen Fields
Field Name
Description
Firm Name
Optional. Name of the firm for the record you want to match.
Secondary Addr
Optional. Secondary address line for the record you want to match.
Primary Addr
Required. Primary address for the record you want to match.
City, ST
Required. Optional if ZIP Code is entered. City and state for the record
you want to match. You can enter the state name or abbreviation.
ZIP Code
Required. Optional if City, St is entered. ZIP Code for the record you
want to match.
USPS County Name or Urb.
Name
If the address matches to a Puerto Rican address that has an
urbanization name associated with it, this field contains that urbanization
name. Otherwise, the field contains the USPS county name where the
matched address is located. If Geographic Coding Plus is installed, you
can optionally display the Geographic Coding county name.
Matched Addr.
Matched standardized address, including apartment number.
City, State ZIP
Matched standardized city/state/ZIP Code line.
CRRT (Carrier Route)
Matched standardized Carrier Route Code. If the CRRT field displays
“R777”, the ZIP+4 was suppressed because the record matched to an
R777 (phantom) carrier route. For more information, refer to"Z4OUT" in
your CODE-1 Plus Reference Guide.
DPBC + Check
Matched delivery point barcode (DPBC) and check digit.
Release 4.1.0
84
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Address Matching Screens
Delivery Sequence Footnotes Screen
Use the Delivery Sequence Footnotes screen to view the Delivery Sequence Footnotes (DSF2
codes) that applied to your match attempt. To access this screen:
•
•
•
Enter DS in the Command field
Press F8 from the Return Codes screen
Press F7 from the Parsed Elements screen.
Delivery Sequence Footnotes Screen Fields (Part 1 of 2)
DSF2 Code
Description
AA
Record matched the ZIP+4 database (the CODE-1 Plus database).
A1
No match was found.
A2
Alias street name was matched to a base street name on the database.
A3
A match was made to an alternate record on the database.
BB
Record was matched to the DSF2 file.
B1
No acceptable match was made to the DSF2 file.
B2
An alias street name matched a base street name on the DSF2 file.
B3
A match was made to an alternate record on the DSF2 file.
CC
Record matched the DSF2 file, but is missing secondary information.
C1
Input record matched but is missing secondary information.
D
City name or state was changed.
E
Primary address was changed.
F
Secondary address was changed.
G
The delivery point is vacant.
H
ZIP Code was changed.
I
Input address could not be parsed.
J
City, state, and ZIP Code could not be validated.
K
Multiple matches in primary address.
K1
Multiple matches due to missing or incorrect directionals.
K2
Multiple matches due to missing or incorrect suffix.
L
Multiple matches in secondary address.
M1
Missing street number.
M2
Address not found.
M3
No such primary number.
Release 4.1.0
85
User’s Guide - Open Systems
Address Matching Screens
Delivery Sequence Footnotes Screen Fields (Part 2 of 2)
DSF2 Code
Description
M4
Firm name not matched.
N1
Missing secondary address number.
N2
Secondary address number not found on file.
P1
Missing rural route/highway contract box number.
P2
Rural route/highway contract box number not found on file.
PB
Input address matched to a PBSA address.
Q1
Missing PO Box number.
Q2
PO Box number not found on file.
Miscellaneous Information/Base Address Screen
Use the Miscellaneous Information/Base Address screen to view the base address for the street that
was matched (if applicable) and additional information about the matched address. To access this
screen, enter the DI command or press F8 from the Statistics screen.
Miscellaneous Information/Base Address Screen Fields (Part 1 of 2)
Field Name
Description
Base Address
Base street address for the alias street that the input record matched.
Preferred Alias
Preferred Alias Processing Indicator.
Abbreviated Alias
Abbreviated Alias Processing Indicator.
Line of Travel Results
5-character sequence code plus 2-character alternate sequence code.
Finance Number
USPS finance number.
Last Line Number
Alphanumeric, cross-reference value between the CODE-1 Plus City/
State file and the ZIP Code file.
Standardized Firm Name
Firm name that was returned during the matching process.
USPS County Name
County where the address resides.
USPS County Number
USPS-assigned number for the county name.
Congressional District
USPS-assigned, 2-digit number representing the address congressional
district.
Season
12-byte code indicating when mail can be delivered to a specific
address.
Release 4.1.0
86
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Address Matching Screens
Miscellaneous Information/Base Address Screen Fields (Part 2 of 2)
Field Name
Description
LACS
Location for the Locatable Address Correction Service indicator on the
output record. This indicator flags any rural addresses that changed to
urban addresses, such as RR 4 BOX 1 changing to 2200 MAIN ST. The
next time you process the file, you can identify and process only those
records on the ZIP+4 database with rural address changes. One of the
following codes is stored:
• Blank — Address was not LACS converted (no change).
• L — Address was LACS converted (changed to an urban address).
Matching Primary
Range Low
Low house range used for the matching process.
Range High
High house range used for the matching process.
Parity
Even or odd numbers in range.
Matching Secondary
(If present)
Range Low
Low unit range used for the matching process.
Range High
High unit range used for the matching process.
Parity
Even or odd numbers in range.
Expanded Return Codes
Use the Expanded Return Codes screen to view text descriptions of each return code that displays
on the Return Codes screen. To access this screen, enter the ER command in the Command Field.
There are no entry fields on the Expanded Return Codes screen.
Geographic Coding Information
Use the Geographic Coding Information screen to view the geographic coding data for your matched
address. To access this screen, enter the GC command in the Command Field.
Geographic Coding Information Screen Fields (Part 1 of 2)
Field Name
Match Level
Description
Level of match obtained against the Geographic Coding Master File:
• 9 — ZIP Code and ZIP+4 Code matched the Master File.
• 5 — Input ZIP Code matched. ZIP+4 Code did not match.
• X — Geographic Coding Master File data has expired.
State
FIPS state code of the matched address.
County
FIPS county number and name of the matched address.
MSA
Metropolitan Statistical Area that encompasses this address.
Census Tract
6-digit number representing the census tract division within the county.
Release 4.1.0
87
User’s Guide - Open Systems
Address Matching Screens
Geographic Coding Information Screen Fields (Part 2 of 2)
Field Name
Description
Census Block Group
Single-digit numeric code indicating the block group division of the
census tract.
Lat/Long Level
Level of latitude and longitude determined for the matched address:
• Z — Latitude and longitude represent the area center of the matched
address.
• T — Latitude and longitude represent the population center of the
census tract determined for the matched address.
• B — Latitude and longitude represent the population center of the
census block group determined for the matched address.
Latitude
Latitude of the standardized address.
Longitude
Longitude of the standardized address.
Match Settings Screen
Use the Match Settings screen to tailor your processing requirements and specify whether CODE-1
Plus should perform ZIP Code correction. For each of the matching algorithms, you can change the
default tightness/looseness settings. These settings indicate how close the data on the database
must be to the input address in order for a match to occur. The tighter the setting, the more closely
the input address must match the database information. To access this screen, enter MS in the
Command field or press F4 from any match results screen.
You can modify the fields on the top half of the physical screen, along with the address matching
fields. When the Match Settings screen displays, you can only enter data in the settings fields on the
upper right portion of the screen. To save your new settings and return to the previous screen, press
Enter. Once changed, the settings stay changed for subsequent matches until you change the
settings again or exit.

Although this screen allows you to change the default matching algorithm settings, we
suggest that you maintain the default settings: (M)edium for all matching, and Y(es) for ZIP
correction.
Match Settings Screen Fields (Part 1 of 2)
Field Name
Algorithms
Description
1-character code indicating the tightness/looseness of the firm name,
directional and suffix, and street name match:
• E — Only equal matches are accepted.
• T — Only tight matches are accepted.
• M — Medium Matches are accepted (default).
• L — Loose matches are accepted.
(V)anity City
1-character code indicating whether or not a vanity city name should be
returned if it is the best match (i.e., it most closely matches the input).
Type one of the following codes:
• X — Yes, return the vanity city name if it is the best match.
• S — No, return the standard city name (default).
Release 4.1.0
88
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Address Matching Screens
Match Settings Screen Fields (Part 2 of 2)
Field Name
Description
Correct ZIP
1-character code indicating whether or not you want CODE-1 Plus to
attempt to correct incorrect ZIP Codes (optional). Type one of the
following codes:
• Y — Attempt ZIP Code correction, if necessary (default).
• N — No, don't attempt ZIP Code Correction.
Output Case
1-character code indicating whether or not the matched address should
be presented in mixed case or upper case:
• C — Mixed case
• L — Lower case
• U — Upper case
Mult Secondary
1-character code indicating whether to attempt multiple secondary
component processing:
• Y — Attempt secondary match.
• N — Assign default ZIP+4 Code.
Override City
1-character code indicating whether the preferred last line city name
should be stored:
• C — Store the city name from USPS City/State File (default city
name)
• P — Store the Primary City Name from the USPS City/State File.
• Z — Store the ZIP+4 File Preferred Last Line City Name (override city
name).
Multiple Elements Screen
Use the Multiple Elements screen to determine whether multiple match elements were found during
the match attempt. To access this screen:
•
•
•
Enter the ME command
Press F8 from the Parsed Elements screen
Press F7 from the Statistics screen
Multiple Elements Screen Fields (Part 1 of 2)
Field Name
Was the city standardized?
Description
Code indicating whether or not the input city name was standardized:
• Blank — No match was found, or the input city name was the same
as either the long or short city name on the database.
• C — The input city name was standardized to either the long or short
city name.
Was the state standardized?
Code indicating whether or not the input state was standardized:
• Blank — No match was found, or the input state was the same as the
state abbreviation on the database.
• S — The input state was standardized to the appropriate
abbreviation.
Was apartment detected in
input?
1-character code indicating whether or not CODE-1 Plus detected an
apartment (or unit) in the input record:
• Y — An apartment was detected in the input.
• N — No apartment was detected in the input.
Release 4.1.0
89
User’s Guide - Open Systems
Address Matching Screens
Multiple Elements Screen Fields (Part 2 of 2)
Field Name
Was “default record”
matched?
Description
Code indicating whether or not the default record was matched:
• Blank — The record matched was not the default record, or no match
was obtained.
• H — Highrise default.
• R — Rural Route default.
• M — Military default.
Were multiple input elements
found?
Code indicating whether multiple input elements were found for the
leading directional segment of the standardized address:
• Blank — Only one value was found.
• M — Multiple values were found.
Alternate addressing scheme
Code indicating the type of alternate address scheme to use to obtain a
match:
• Blank — No alternate address scheme used.
• D — Delivery point alternate logic used.
• S — Small town default logic used.
• U — Unique ZIP Code logic used.
Leading dir
Code indicating whether or not multiple leading directional matches
were found:
• Blank — Only one leading directional was found.
• M — Multiple leading directionals were found.
Street name
Code indicating whether or not multiple street name matches were
found:
• Blank — Only one street name was found.
• M — Multiple street names were found.
Suffix
Code indicating whether or not multiple suffix matches were found:
• Blank — Only one suffix was found.
• M — Multiple suffixes were found.
Trailing dir
Code indicating whether or not multiple trailing directional matches were
found:
• Blank — Only one leading directional was found.
• M — Multiple trailing directionals were found.
Parsed Elements Screen
Use the Parsed Elements screen to view the individual elements that make up the standardized
address. If no address match was found, the fields on this screen are blank. To access this screen:
•
•
•
Release 4.1.0
Enter the PE command
Press F8 from the Delivery Sequence Footnotes screen
Press F7 from the Multiple Elements screen
90
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Address Matching Screens
Parsed Elements Screen Fields
Field Name
Description
Lead Dir
Returned leading directional
House
Returned house number
Street
Returned street name
Suffix
Returned suffix
Trail Dir
Returned trailing directional
RR/HC #
Returned rural route or highway contract route number
RR/HC Box
Returned rural route or highway contract box number
PO Box
Returned post office box number
Apt. Information
Returned apartment designator (i.e., STE, APT) and number
Short City
Returned short city name
ZIP Code
Returned 9-digit ZIP Code
Private Mail Box
Returned Private Mailbox information
Return Codes Screen
Use the Return Codes screen to view the return codes that correspond to your match attempt. To
access this screen, enter the RC command in the Command field or press the F7 function key from
the Delivery Sequence Footnotes screen.

If you hit a “seed record” during DPV processing, a message displays similar to:
DPV KEY IS: S06430475462316207
To continue DPV processing, contact Pitney Bowes Technical Support for a new permanent
key. For more information on DPV processing, “seed records,” and license keys, refer to
"Getting Started With Interactive Processing” on page 65.
Release 4.1.0
91
User’s Guide - Open Systems
Address Matching Screens
Return Codes Screen Fields (Part 1 of 5)
Field Name
General RC
Description
1-character return code indicating the success or reason for failure of the
match attempt:
• Blank — The address match attempt was successful.
• A — Unit number missing or not found on database.
• B — Insufficient (or blank) address in formation for a match.
• E — External match—auxiliary file processing.
• H — House/box number not found on street.
• M — Multiple matches were found.
• S — Street name not found in ZIP Code.
• X — The CODE-1 Plus Master File has expired.
• Z — ZIP Code not found on database.
City RC
1-character return code indicating the success or reason for failure of the
city match attempt:
• Blank — No address match was found, or the input city was correct.
• B — No input city and state were found.
• C — Mismatched city for valid input state/ZIP.
• I — The input city was used; no cities available for the ZIP Code.
• N — The input city name was not used.
• S — Spelling errors in the input were corrected.
Firm RC
1-character return code indicating the success or reason for failure of the
firm name match attempt:
• Blank — The firm name match was successful, or no firm name was
indicated in the input record.
• F — The input firm name does not match the firm name on the
database.
• M — A firm name was in the input, but there were no firm names on
the database for the matched address.
Address Prob
Single digit that indicates the probable correctness of the address
match:
• Blank — No address match was found.
• 0 — The address match is most likely to be correct.
• 1-8 — These values represent intermediate values on a sliding scale.
• 9 — The address match is least likely to be correct.
Overall Prob
Single digit that indicates the probable correctness of the address and
firm name match:
• Blank — No match was found.
• 0 — The match is most likely to be correct.
• 1-8 — These values represent intermediate values on a sliding scale.
• 9 — The match is least likely to be correct.
Release 4.1.0
92
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Address Matching Screens
Return Codes Screen Fields (Part 2 of 5)
Field Name
USPS Rec. Type
Description
USPS-defined type code of the ZIP+4 record used for matching:
• Blank — No match was obtained.
• F — Firm record
• G — General delivery record
• H — High rise (apartment complex) record
• P — PO Box record
• R — Rural route or highway contract record
• S — Normal street address record.
City Type
1-character code describing the input city type:
• P — Primary city
• S — Secondary city
• V — Vanity city.
Dir. RC
1-character return code indicating the success or reason for failure of the
directional match attempt:
• Blank — No address match was found, or the directional was correct.
• D — The directional does not match the database.
• F — The directional was correct, but was in the wrong location (i.e.,
trailing directional should have been a leading directional).
• N — No directional was found on the input address, but a directional
was present on the database.
Suffix RC
1-character return code indicating the success or reason for failure of the
suffix match attempt:
• Blank — No address match was found, or the suffix was correct.
• S — The suffix does not match the database.
• N — No suffix was found on the input address, but a suffix was
present on the database.
Unit RC
1-character return code indicating the success or reason for failure of the
unit (or apartment) match attempt:
• Blank — No address match was found, or the input unit was correct.
• A — The unit does not match the database.
• N — No unit was found on the input address, but a unit was present
on the database.
• F — Suite number appended due to a firm name match.
Firm Score
Single digit that indicates the probable correctness of the firm name
match:
• Blank — No match was obtained.
• 0 — The input firm name matched the output firm name exactly.
• 1-9 — These represent intermediate values on a sliding scale.
Street Score
Single digit that indicates the probable correctness of the street name
match:
• Blank — No match was obtained.
• 0 — The input street name matched the output street name exactly.
• 1-9 — These represent intermediate values on a sliding scale.
Release 4.1.0
93
User’s Guide - Open Systems
Address Matching Screens
Return Codes Screen Fields (Part 3 of 5)
Field Name
Source of Addr.
Description
1-character code indicating whether the output street address was
matched from the primary address line or the secondary address line:
• M — A combination of information from the two lines.
• P — Primary line
• S — Secondary line
Alias RC
1-character return code indicating whether or not the input address
matched an alias street name, as follows:
• Blank — The address matched a base street, or no match was found.
• A — The address matched an alias street.
ZIP Status
1-character code specifying the status of the output ZIP Code:
• A — The output ZIP Code is different from the original ZIP Code.
• B — The output ZIP Code is blank.
• C — The original ZIP Code is the output ZIP Code.
• I — Invalid -- No match could be obtained; the output ZIP code
contains blanks because the input ZIP code was invalid.
• O — The original ZIP Code is in the output location because no match
was obtained.
• U — Blank—A unique address match could not be obtained and there
was no correlation between the input unique ZIP Code and the city/
state. The original ZIP Code was blanked.
Source of ZIP
1-character code indicating the source of the final ZIP Code:
• B — No ZIP Code was determined.
• C — The final ZIP Code was determined from the city-based locality.
• F — The final ZIP Code was determined from the ZIP-based locality.
• M — The final ZIP Code was determined from the ZIPMOVE file.
• Z — The original ZIP Code was retained.
POB ZIP Code
1-character code indicating whether the address is located in a P. O.
Box-only delivery zone. P. O. Box-only delivery zone addresses can only
receive postal delivery through the use of a P. O. Box. No other postal
delivery method is available for these addresses.
• Y — P. O. Box-only ZIP Code.
• N — Not a P. O. Box-only ZIP Code.
“best fit” ZIPs
Number of “best fit” ZIP Codes found during the match attempt.
PBSA Ind
1-character code indicating whether this address was found in the PBSA
Table. DPV processing uses the PBSA Table to identify P. O. Box™
Street Addresses (PBSA). PBSA addresses are street addresses that
really represent a USPS P. O. Box™.
• Blank — Not presented
• Y — Found in the DPV PBSA Table.
• N — Not found in the DPV PBSA Table.
Release 4.1.0
94
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Address Matching Screens
Return Codes Screen Fields (Part 4 of 5)
Field Name
Alt. Adr. Scheme
Description
1-character code indicating the type of alternate address scheme that
was used to obtain a match:
• Blank — No alternate address scheme used.
• D — Delivery point alternate logic used.
• E — Enhanced high rise alternate match logic
used.
• S — Small town default logic used.
• U — Unique ZIP Code logic used.
Alias Type
1-character code indicating the alias type:
• Blank — Street record matched was not an alias street.
• A — Abbreviation street name. This USPS abbreviation is for streets
that are over 30 characters long.
• C — Official street name change (Chamber of Commerce action.
• O — Street record matched was a USPS “other” alias.
• P — Street record matched was a USPS “preferred” alias.
Line of Travel RC
1-character code describing the Line of Travel match obtained:
• Blank — Invalid data passed to matcher
• 9 — 9-digit ZIP+4 match was successful
• C — Call to LOT matcher failed.
• F — Master file access failure.
• V — Incompatible Master file.
• D — 9-digit ZIP+4 match was unsuccessful (default coded).
DPV Flag
1-character return code indicating the result of your DPV processing:
• D — Valid primary number; input missing secondary number (primary
RR).
• M — Unable to resolve the Multiple Condition.
• N — No Delivery Point Validation.
• S — Valid primary number; but secondary number (primary for RR)
present and is not confirmed.
• Y — Delivery Point validated. Primary number valid and second
number (when present) valid.
• Blank — Address not presented to DPV table.
NoStat Flag
1-character code indicating the presence of statistics for this address. A
“Y” indicates that the address is not a valid delivery address even though
it has been validated by DPV.
• Blank — Not presented.
• Y — Found match to ‘No Stat’ DPV hash table.
• N — No match found to “No stat” DPV hash table.
Vacant Table Flag
1-character code indicating that this address was found in the Vacant
table.
• Blank — Not presented.
• Y — Indicates that the address has been vacant for at least last 90
days.
• N — Indicates that the address is not vacant.
Release 4.1.0
95
User’s Guide - Open Systems
Address Matching Screens
Return Codes Screen Fields (Part 5 of 5)
Field Name
CMRA Flag
Description
1-character code indicating whether a CMRA look-up has occurred:
• Y — Yes, this is a CMRA.
• N — No, this is not a CMRA.
• Blank — Not presented.
NOTE: This code will only be presented if the DPV flag is Y, S, or D.
RDI Flag
1-character code describing the Residential Delivery File (RDI) match
obtained:
Blank — RDI match not attempted or not found.
B — Business confirmed.
M — Address is mixed business and residential.
R — Residence confirmed.
First Four Additional ZIPs
The first four additional ZIP Codes that matched the input record but
were not used as the output ZIP Code.
Dropped Information Type
1-character code indicating the type of information, if any, that was
dropped by the matcher during the match attempt:
• Blank — Either no match was obtained, or no information was
dropped.
• A — A street address was dropped in order to obtain an RR/HC or PO
Box match.
• R — An RR/HC or PO Box address was dropped in order to obtain a
street address match.
• W — One or more characters were dropped during the address
parsing process.
Data

Any miscellaneous characters that were dropped during the address
matching process.
The Dropped Information Type code refers to the type of information that was dropped by the
matcher during the match attempt. The Data field contains characters dropped during the
address analysis process, before the matcher even attempts a match. Therefore, it is
possible to have a Dropped Information Type that is not blank, but a blank Data field.
Statistics Screen
Use the Statistics screen to view execution statistics about the number of calls made to the matcher
while processing an address. This screen is particularly useful if you are encountering a problem
with Interactive CODE-1 Plus. These statistics can help Pitney Bowes Technical Support
Representatives solve your problem. To access this screen:
•
•
•
Release 4.1.0
Enter the ST command
Press F8 from the Multiple Elements screen
Press F7 from the Dropped Information/Base Address screen
96
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Address Matching Screens
Statistics Screen Fields (Part 1 of 2)
Field Name
City-based locality match
results
Description
1-character code indicating the results of the match attempt in the citybased locality:
• Blank — Not attempted.
• I — Attempted, improved (a match was found).
• N — Attempted, no match found.
Finance number-based
locality match results
1-character code indicating the results of the match attempt in the
finance number-based locality:
• Blank — Not attempted.
• I — Attempted, improved (a match was found).
• N — Attempted, no match found.
Original ZIP-based match
results
1-character code indicating the results of the match attempt in the
original ZIP Code-based locality:
• Blank — Not attempted.
• I — Attempted, improved (a match was found).
• N — Attempted, no match found.
Number of match attempts
The number of attempts that were made to obtain the match results.
Std. Address RC
1-character return code indicating the success or reason for failure of the
standardized address match attempt:
• Blank — The address match attempt was successful.
• A — Unit number missing or not found on database.
• B — Insufficient (or blank) address information for a match.
• H — House/Box number not found on street.
• M — Multiple matches were found.
• S — Street name not found in ZIP Code.
• Z — ZIP Code not found on database.
ZIP RC
1-character return code indicating the success or reason for failure of the
14-digit ZIP Coding attempt (i.e., was an output ZIP Code returned? If
not, why not):
• Blank — The match attempt was successful.
• A — Unit number missing or not found on database.
• B — Insufficient (or blank) address information for a match.
• H — House/Box number not found on street.
• M — Multiple matches were found.
• S — Street name not found in ZIP Code.
• Z — ZIP Code not found on database.
Release 4.1.0
97
User’s Guide - Open Systems
Address Matching Screens
Statistics Screen Fields (Part 2 of 2)
Field Name
ZIP+4 RC
Description
1-character return code indicating the success or reason for failure of the
ZIP+4 Coding attempt (i.e., was an output ZIP+4 Code returned? If not,
why not):
• Blank — The match attempt was successful.
• A — Unit number missing or not found on database.
• B — Insufficient (or blank) address information for a match.
• H — House/Box number not found on street.
• M — Multiple matches were found.
• S — Street name not found in ZIP Code.
• V — The input matched a non-deliverable street address.
NOTE: A non-deliverable ZIP+4 Range is typically a new ZIP range
where the USPS has not finalized assignments of ZIP+4 codes, thus
not permitting assignment of postal code information at this time.
• Z — ZIP Code not found on database.
CR-RT RC
1-character return code indicating the success or reason for failure of the
Carrier Route coding attempt:
• Blank — The match attempt was successful.
• A — Unit number missing or not found on database.
• B — Insufficient (or blank) address information for a match.
• H — House/Box number not found on street.
• M — Multiple matches were found.
• S — Street name not found in ZIP Code.
• Z — ZIP Code not found on database.
ZIP Index
Number of database reads done on the ZIP Index file in order to obtain
the match.
City Details
Number of database reads performed on the City Details file in order to
obtain the match.
Locality
Number of database reads performed on the Locality file in order to
obtain the match.
Street Details
Number of database reads performed on the Street Details file in order
to obtain the match.
County
Number of database reads performed on the County file in order to
obtain the match.
Address Stack Screen
Use the Address Stack screen to view information related to as many as 10 addresses that have
been identified by the matcher as multiples for the address entered on the match portion of the
screen. The displayed data and headers are variable in length. Up to three screens of information
can be accessed by the Left and Right commands (showing additional information) and up to two
screens with the Up and Down commands (showing additional addresses).
Release 4.1.0
98
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Address Matching Screens
Address Stack Screen Fields
Field Name
Description
Address
Street name along with directionals, prefix/suffix, and house number
City
City name
St
State name
ZIP
ZIP Code and ZIP+4
DPC
Delivery point code and check digit
C-Rt
Carrier Route Code (Cnnn, blank if none)
RTP
Three-digit combination of codes:
• USPS record type of record matched:
– F — Firm
– G — General delivery
– H — High rise (apartment complex)
– P — PO Box
– R — Rural route/Highway contract
– S — Normal Street Address
• “Default” match:
– H — High Rise Default
– R — Rural Route Default
– M — Military Default
– blank — Not a default record.
• Overall probability of match correctness:
–
0-9 — 0 is most probably correct
Cnty/CD
County number
Primary
Primary range information (and parity)
Secondary
Secondary range information (and parity)
LL#
Last line number
Fin-Nr
Finance number
Urbanization
Puerto Rican urbanization
Firm
Firm name

Release 4.1.0
By typing SELECT and the appropriate line number in the Command field, you can choose
which record of the displayed multiple addresses you would like in the input address field.
99
User’s Guide - Open Systems
Database Inquiry Screens
Database Inquiry Screens
This section describes screens that support the database inquiry function.
Apartments at a House Range
The Apartments at a House Range screen shows you all of the apartments at a particular house
number. For each number (house), CODE-1 Plus displays the address, ZIP Code range, apartment
number ranges, ZIP Codes, ZIP+4 Code ranges, carrier route codes, USPS record types (indicating
the type of apartment), and number of firms.
To access this screen, enter the AH <line number> command or press F4 from the Houses on a
Street screen.
Apartments at a House Range Screen Fields
Field Name
Description
LN
Line number assigned to this apartment range.
Apt Range
Apartment number range.
ZIP
ZIP Code for the apartments in this range.
Z+4 Range
Range of ZIP+4 Codes that are valid for this apartment range.
Rte
Carrier or rural route number for the apartments in this range.
Record Type
USPS record type for the ZIP+4 records in this apartment range.
Apt Type
Unit designator for the apartments in this range (i.e., APT, STE).
Firms
Number of firms in this apartment range.
Cities in a State Screen
Use the City Information screen to view an alphabetical listing of all of the city names in a particular
state. For each city, this screen also displays the valid state abbreviation and the ZIP Code (or range
of ZIP Codes). To access this screen, enter the CS <state abbr.> command. You can enter this
command from any screen in the system.

As a short cut to entering a Locate command after the CS command, you can enter CS
<state abbr.> <location string> as a single command
Cities in a State Screen Fields (Part 1 of 2)
Field Name
Description
LN
Line number of the city.
City
City name.
State
Abbreviations for the state in which the city is located.
Release 4.1.0
100
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Database Inquiry Screens
Cities in a State Screen Fields (Part 2 of 2)
Field Name
Description
ZIP Range
Range of ZIP Codes that are valid for the city.
Type
Code indicating the type of city. One of the following codes appear:
• P — Primary city.
• S — Secondary city.
• V — Vanity city.
Urb
Code indicating whether the city is a Puerto Rican urbanization area.
One of the following codes appear:
• Blank — The city is not a Puerto Rican urbanization area.
• Y — The city is a Puerto Rican urbanization area.
Unique ZIP
Code indicating whether the ZIP Code for the city is unique to that city
or resides in multiple cities. One of the following codes appear:
• Blank — The ZIP Code is not unique to the city.
• Y — The ZIP Code is unique to the city.
Cities in a ZIP Code Screen
Use the Cities in a ZIP Code screen to view all cities in a given ZIP Code. For each city, CODE-1
Plus displays the long city names, short city names, and city type. To access this screen:
•
•
•
Enter the CZ <line number> or the CZ <ZIP Code> command
Press F5 from the Cities in the Database screen
Press F5 from the Cities in a State screen
The USPS allows city names to be up to 28 characters long. However, if a city name is longer than
13 characters, a USPS short city name is provided. Typically, long city names are shortened by
removing vowels.
In cases where a ZIP Code has more than one city name, the screen shows these city names, and
their accompanying city type. These city types indicate the USPS-preferred city name, and any
alternate city names associated with the same ZIP Code. Preferred city names have a city type of
“primary;” alternate city names have city types of “secondary” or “vanity.”
For example, ZIP Code 70510 is associated with the three city names Abbeville, Cow Island, and
Meaux. Abbeville is preferred and has a city type of primary. All other city names have a city type of
secondary.
Cities in a ZIP Code Screen Fields
Field Name
Description
LN
Line number for this city name.
Long City Name
Full name for the city.
State
Two-character state abbreviation for the city.
Short City Name
USPS shortened city name.
City Type
USPS designated city type. One of the following city types appears:
Primary, Secondary, Vanity.
Release 4.1.0
101
User’s Guide - Open Systems
Database Inquiry Screens
City Information Screen
Use the City Information screen to view an alphabetical listing of all city names in the CODE-1 Plus
database. For each city, this screen also displays the state abbreviation and the ZIP Code (or range
of ZIP Codes), the type urbanization name, and the unique ZIP Code that applies to the city.
The City Information screen displays when you first access the CODE-1 Plus Interactive System. If
you switch to any of the address match results screens, you can return to this screen by typing CI in
the Command field.

As a short cut to entering a Locate command after the CI command, you can enter CI
<location string> as a single command. <location string> on this screen may be either a city
name or a city state combination.
City Information Screen Fields
Field Name
Description
LN
Line number of the city.
City
City name.
State
Abbreviations for the state in which the city is located.
ZIP Range
Range of ZIP Codes that are valid for the city.
Type
Code indicating the type of city. One of the following codes appear:
• P — Primary city.
• S — Secondary city.
• V — Vanity city.
URB
Code indicating whether the city is a Puerto Rican urbanization area.
One of the following codes appear:
• Blank — The city is not a Puerto Rican urbanization area.
• Y — The city is a Puerto Rican urbanization area.
Unique ZIP
Code indicating whether the ZIP Code for the city is unique to that city
or resides in multiple cities. One of the following codes appear:
• Blank — The ZIP Code is not unique to the city.
• Y — The ZIP Code is unique to the city.
Firms in a House Range Screen
Use the Firms in a House Range screen to view all firms located on a particular house range on a
street. The firm information includes the house number ranges, apartment number ranges within a
dwelling, the name of the firm located at each apartment/suite, ZIP Codes, ZIP + 4 Codes, and
carrier route codes. To access this screen, enter the command FM <line number> (or by pressing
F5) from the Streets in a City or Streets in a ZIP Code, Houses on a Street, or Apartments at a House
Range screens.
Release 4.1.0
102
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Database Inquiry Screens
Firms on a House Range Screen Fields
Field Name
Description
LN
Line number for this firm.
House Range
House number ranges that are valid for this firm.
Apt Range
Apartment number ranges that are valid for this firm.
Firm Name
Firm name.
ZIP Code
9-digit ZIP Code assigned to this firm.
C-Rt
Carrier route number for this firm.
Houses on a Street Screen
Use the Houses on a Street screen to view a listing of all of the house number ranges on a particular
street. In addition to even/odd house number ranges, CODE-1 Plus displays ZIP and ZIP+4 Code
ranges, carrier routes, and firm/alias name. To access this screen, enter the command HS <line
number> (or press F4) from the Streets in a City or Streets in a ZIP Code screens.


As a short cut to entering a Locate command after the HS command, you can enter HS <line
number> <location string> as a single command.To view more lines of data, in the Command
field, type FLIP and press Enter, or press F10.
House ranges that are on an alias portion of the street appear with an “A” in the left-most
column next to the house range. To see the base name for the house range, position your
cursor on the alias house range and press F2, or enter the ALIAS <line number> command.
The base street name appears on the bottom line of the screen.
The ZIPMove Record Indicator appears in the example above as a “Z” and uses the same
field location as the alias street range indicator. The ZIPMove Record Indicator supersedes
the alias indicator.
Houses on a Street Screen Fields
Field Name
Description
LN
The line number of the house range.
House Range
The house number range.
E/O
An E or an O indicating whether this is a range of only even- numbered
or only odd-numbered houses.
ZIP
The ZIP Code for the houses in this range.
Z+4 Range
The range of ZIP+4 Codes that are valid for this house range.
Release 4.1.0
103
User’s Guide - Open Systems
Database Inquiry Screens
Houses on a Street Screen Fields
Field Name
Description
Rte
The carrier or rural route number for the houses in this range.
Typ
The USPS record type for the ZIP+4 records in this house range.
Firm/Alias Name
Firm name or range street alias name.
Streets in a City or Streets in a ZIP Code Screen
Use the Streets in a City or Streets in a ZIP Code screen to view an alphabetical listing of all street
names in a given city or ZIP Code. For each street listed, CODE-1 Plus displays directionals, such
as NE and SW, and suffixes, such as ST and BLVD.
To access this screen:
•
Enter the SC or SL command (or press F4) from the Cities in the Database screen, or Cities in a
State screen.
Press F4 from the Cities in a ZIP Code screen.
Enter the SZ command from any database inquiry screen.
•
•

As a short cut to entering a Locate command after the SC, SZ, or SL command, you can
enter SC <line number> <location string> as a single command.
Streets in a City or Streets in a ZIP Code Screen Fields
Field Name
Description
LN
Line number of the street.
Dir
Leading directional for the street.
Street Name
Name of the street.
Sfx
Suffix for the street.
Dir
Trailing directional for the street.
ZIP Codes
Valid ZIP Code(s) for this street. This field only displays if you accessed
this screen from the Cities in the Database screen (not the Cities in a ZIP
Code screen).
Geographic Coding Plus Interface
If you have purchased Geographic Coding Plus from Pitney Bowes, you can access that product
directly from CODE-1 Plus by typing the command GEO in the Command field on any CODE-1 Plus
screen. The Geographic Coding Interface screen displays. If you do a match attempt before you
enter the GEO command, your matched ZIP Code and ZIP + 4 Code appear in ZIP Code fields on
the Geographic Coding Interface screen. This is the first screen of geographic coding data for your
matched address. Please refer to your Geographic Coding Plus User's Guide for further reference
on the fields and function keys on this screen.
Release 4.1.0
104
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Database Inquiry Screens

In a Unix environment, you must source the Geographic Coding Plus setup file before you
access the Geographic Coding Interface. This procedure sets up the environment variables
for the Geographic Coding Plus database.
First Geographic Coding Interface Screen Fields (Part 1 of 2)
Field Name
Description
ZIP Code
5-digit ZIP Code for the entered address.
ZIP+4 Code
4-digit ZIP+4 Code for the entered address.
DPBC
Delivery Point Barcode for the entered address.
House#
House Number for the entered address.
Match Level
Code indicating the level of match obtained against the Geographic
Coding Master File. One of the following codes appears:
• 5 — The input ZIP Code matched, but the ZIP+4 Code did not.
• 9 — Both the ZIP Code and ZIP +4 Code matched the Master File.
• X — The Geographic Coding Master File data has expired.
State Code
2-character FIPS state code of the matched address.
FIPS County Code
2-character FIPS county number and 20-character county name of the
matched address.
Census Tract
6-digit number representing the census tract division within the county.
Block Group
1-digit numeric code indicating the block group division of the census
tract.
MSA Code
The 4-character Metropolitan Statistical Area that encompasses this
address.
MSA Name
The 50-character Metropolitan Statistical Area name.
Lat/Long Level
Code indicating the level of latitude and longitude determined for the
matched address. One of the following codes displays.
• B — Latitude and longitude represent the population center of the
census block group determined for the matched address.
• T — Latitude and longitude represent the population center of the
census tract determined for the matched address.
• Z — Latitude and longitude represent the area center of the matched
address.
Latitude
9-digit number (with six decimal places implied) followed by a 1character directional (N or S) that occupy the first eight bytes of this area.
Longitude
9-digit number (with six decimal places implied) followed by a 1character directional (E or W) that occupy the last eight bytes of this
area.
Software Vintage
Indicates the version of Geographic Coding you are using.
Release 4.1.0
105
User’s Guide - Open Systems
Database Inquiry Screens
First Geographic Coding Interface Screen Fields (Part 2 of 2)
Field Name
Description
File
Indicates the expiration date of the Geographic Coding File that you are
using.
Distance in Miles
Number of miles between the two specified addresses, if necessary.
The following table describes the fields on the second and last screen of geographic coding data for
your matched address.
Second Geographic Coding Interface Screen Fields (Part 1 of 2)
Field Name
Description
ZIP Code
5-digit ZIP Code for the entered address.
ZIP+4 Code
4-digit ZIP+4 Code for the entered address.
DPBC
Delivery Point Barcode for the entered address.
House#
House Number for the entered address.
MCD/CCD Code
MCDs (Minor Civil Divisions) are the primary political or administrative
divisions of a county, representing many kinds of legal entities with a
variety of governmental and administrative functions. CCDs (Census
County Divisions) are established in states where there are no legally
established MCDs.
Confidence
1-character code that indicates the confidence code source. One of the
following codes appears:
• Z — ZIP level.
• 0 — ZIP default.
• 1 — ZIP sector method.
• 2 — 5-digit household default method.
• 3 — 5-digit boundary method.
PRIZM Cluster
2-character PRIZM cluster code and a 20-character PRIZM cluster
name. PRIZM codes are lifestyle segment codes and definitions
enabling for more precise information about the lifestyle and
demographic features of a population.
Cluster Group
2-character PRIZM cluster social group code and a 20-character group
name.
Place Code
5-character FIPS place code.
Incorporated
1-character code indicating whether the entered address is in an
incorporated area.
• Y — Incorporated.
• N — Not incorporated.
Class Code
2-character class code.
Place Name
30-character place name.
Release 4.1.0
106
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Screens that Support Site Customization
Second Geographic Coding Interface Screen Fields (Part 2 of 2)
Field Name
Description
GeoTAX Key
NOTE: This field is only available to GeoTAX customers who are also
licensed users of the Vertex Quantum or ComTax21 products.
Up to 9 digits can be displayed in this field. The first 2 digits of this
number represent the Vertex state code, the next 3 digits are the FIPS
county code, and the next 4 digits, a Vertex city code.
This information will only be displayed for those GeoTAX customers who
have a subscription to the MATCHMST file from Vertex. Additional
information on this subject can be found in the GeoTAX User’s Guide.
GeoTAX Key Return Code
1-character code indicating the match results for the GeoTAX Key:
• Blank — No matching GTMASTR GeoTAX record found.
• E — Exact match using state/county/place/ZIP Code/place name.
• P — Partial match using state/county/place.
• A — Alternate match using ZIP Code and place name.
• N — Record is default coded based on valid state code.
Date Annexed
Place last annexed date.
Updated
Place last updated date.
Verified
Place last verified date.
Screens that Support Site Customization
The screens shown in this section all support the interactive site customization function.
Administration Sign-on Screen
Use the Administration Sign-on screen to type in, and optionally update, the password required to
access the site default update screens. You can access this screen by typing “ADMIN” on the
Command: line from any match or database inquiry screen. If a new password is typed in, the
screen returns with an area to “Confirm New Password.” If you do not have your initial password,
contact Pitney Bowes Technical Support at 1-800-367-6950.
Release 4.1.0
107
User’s Guide - Open Systems
Screens that Support Site Customization
The password change process can be stopped by pressing the space bar through both new
password fields, or by selecting Quit or Cancel.
CODE-1 Plus Coding System
------------------------------------------------------------------------Command:
CODE-1 Plus Administration Sign-on Screen
Password:
New Password:
G1M01I Enter Current Password and optional New Password
1=Help
3=Quit
10=Exit
Fields on the Administration Sign-On Screen
Field Name
Description
Password
Area to type in current password
New Password
Area to type in a new password. The new password must be 1-8
alphanumeric characters with no leading or embedded spaces.
Confirm New Password
Area to re-type the new password for confirmation. This field will only be
displayed if a new password has been entered.
Interactive Customization Screens
Use the Interactive Customization screens to view, and optionally update, the site-specific values
you choose for your system. You can access these screens by successfully entering the existing
system password on the Administration Sign-on screen (accessed by the “ADMIN” command).
Values on these screens are not updated unless F5 is pressed (or “Save” on the command line is
selected), and the changed values are not validated until either the Enter key or “Save” are pressed.
Release 4.1.0
108
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Screens that Support Site Customization
First Interactive Customization Screen Fields (Part 1 of 2)
Field Name
Initial Screen
Description
Indicates Split or Full Screen display on entry to system
• S — Split screen display
• F — Full screen display
Expiration Warning
Display or suppress database warning
• D — Display database warning
• S — Suppress database warning
Firm
Firm Match Setting Value. Refer to the “Match Settings Screen” section
earlier in this chapter for an explanation of these values.
• T — Tight
• M — Medium
• L — Loose
• E — Equal
Dir/Suffix
Directional/Suffix Match Setting Value. Refer to the “Match Settings
Screen” section earlier in this chapter for an explanation of these values.
• T — Tight
• M — Medium
• L — Loose
• E — Equal
Street
Street Match Setting Value. Refer to the “Match Settings Screen” section
earlier in this chapter for an explanation of these values.
• T — Tight
• M — Medium
• L — Loose
• E — Equal
Vanity City
Match Setting for Vanity Cities. Refer to the “Match Settings Screen”
section earlier in this chapter for an explanation of these values.
• X — Allow vanity city names in standardized output.
• S — Only allow primary/secondary city names in standardized output.
Correct Input ZIP
Match Setting for ZIP correction. Refer to the “Match Settings Screen”
section earlier in this chapter for an explanation of these values.
• Y — Correct input ZIP Codes.
• N — Do not correct input ZIP Codes.
Output Case
Returned address settings. Refer to the “Match Settings Screen” section
earlier in this chapter for an explanation of these values.
• C — Display matched address in mixed case.
• L — Display matched address in lower case only.
• U — Display matched address in upper case only.
Multiple Secondary
Match Setting for Multiple Secondary Components. Refer to “Match
Settings Screen” section earlier in this chapter for an explanation of
these values.
• Y — Attempt secondary match.
• N — Assign default ZIP+4 Code.
Release 4.1.0
109
User’s Guide - Open Systems
Screens that Support Site Customization
First Interactive Customization Screen Fields (Part 2 of 2)
Field Name
Description
Preferred City Name
Match Setting for Preferred City Name. Refer to Override City Name in
the table from the “Match Settings Screen” section earlier in this chapter
for an explanation of these values.
• C — Store the city name from USPS City/State File (default city
name).
• Z — Store the ZIP+4 File Preferred Last Line City Name (override city
name).
Perform DPV Process
Here you can select whether or not you wish to perform DPV processing:
• X — Perform DPV processing.
• Blank — Do not perform DPV processing.
NOTE: This can also be selected by entering DPV on the command line
of the Address Match screen.
Perform LTO Process
Here you can select whether or not you wish to perform Line of Travel
Option (LOT) processing:
• X — Perform LTO processing.
• Blank — Do not perform LTO processing.
NOTE: This can also be selected by entering LTO or LOT on the
command line of the Address Match screen.
Perform RDI Process
Here you can select whether or not you wish to perform Residential
Delivery File (RDI) processing:
• X — Perform RDI processing.
Blank — Do not perform RDI processing.
NOTE: This can also be selected by entering RDI on the command line
of the Address Match screen.
Initial Command
Command to be invoked upon entry of the system. Can be a
combination of screen (CI, CS, CZ, or SZ) and locate commands
separated by a semicolon. If ‘FLIP’ is entered, ‘Initial Screen’ is set to ‘F’.
The following table describes the fields on the second Interactive Customization screen.
Second Interactive Customization Screen Fields (Part 1 of 2)
Field Name
Geographic Coding Available
Description
Indicates whether Geographic Coding Plus is installed on the system or
whether the legacy Geographic Coding System is installed.
• N — Geographic Coding Plus is not installed on the system.
• Y — Geographic Coding Plus is installed on the system.
• L — Legacy Geographic Coding System is installed.
GEO Lat/Long Data source
Indicates which GEO file to use.
• B — Use base master file.
• A — Use advanced file.
• F — Get finest granularity available on either base or advanced file.
Use GEO County
Indicates whether to return the Geographic Coding county on the
CODE-1 Plus Match screen on a successful match.
• Y — Use Geographic Coding county.
• N — Use USPS county.
Release 4.1.0
110
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Screens that Support Site Customization
Second Interactive Customization Screen Fields (Part 2 of 2)
Field Name
ZIP Match Centroid
Description
Indicates centroid to return on a ZIP Code match.
• C — Census tract centroid
• Z — ZIP Centroid
Return Alias Base on Match
Indicates whether to change an alias street name displayed on a match
to the base street name.
• Y — Display base street name.
• N — Retain alias street name.
Seed Violation Bypass
You can determine if the system should bypass any seed record
violations during processing. To activate this option, enter
“STOPBYPASS” on the command line of the admin function screen.
Once you have entered “STOPBYPASS” on the command line, the
following text will appear on that line: SEED STOP BYPASS IS ON.
Enter “STOPBYPASS” to disable the option.
NOTE: You will be required to have knowledge of the ADMIN
password to access this process. If you enter “STOPBYPASS” on the
command line on other screens you will receive an error message.
Custom Page Title
The interactive system page title (for all screens) can be customized
using this option.
Use Navigation
The default setting for Intelligent Navigation can be set here.
• Y — Navigation on.
• N — Navigation off.
Enhanced/All Street Matching
Enhanced/All Street Matching Indicator
Preferred Alias Processing
Abbreviated Alias Processing Indicator
Abbreviated Alias Processing
Abbreviated Alias Processing Indicator
Return Transid
Indicates Transid to be invoked upon exit from system (CICS only)
TS Queue Utilization
Indicates whether Auxiliary or Main Storage is to be used for TS Queues
(CICS only).
• A — Auxiliary storage is to be used.
• M — Main storage is to be used.
Definition of PFKEYS
The third and last customization screen allows you to define your program function keys (PFKEYS)
to maintain any in-house standards for PFKEY usage within the CODE-1 Plus system.
Working within this third screen, you can change the assigned PFKEY of a certain function or the
text associated with a particular PFKEY. For example, you can tab down to PFKEY 01 and change
the text from “Help” to “Info.”

Release 4.1.0
You CANNOT assign one PFKEY to have several functions. If you do, a message displays
that “Key designation conflicts with a Multi-Screen Key.” Any errors in defining PFKEYS
displays in red when you hit the Enter key after making your changes.
111
User’s Guide - Open Systems
Database Information Screen
Database Information Screen
The Database Information screen shows information related to the software and database installed
for CODE-1 Plus. Specific fields included in the screen are the software release and modification
numbers, the CASS expiration date of the software, the database vintage date and expiration date
(after which inquiry but not matching is permitted) and the days remaining until expiration.

The DPV database vintage date displays only if you have performed a match with DPV
turned on.
Customization File Administration
The site customization file (G1CPFDF) is an updateable indexed file for the interactive system. If you
plan on modifying default initialization and processing values for your site, you need to install the
customization file. Otherwise, the interactive system will function with the default match settings and
processing on entry to and exit from the CODE-1 Plus software.

The customization file is required for accessing the Geographic Coding Interface screen. If
the customization file is not available, the Geographic Coding Interface is not available.
File Backup and Security
Because the site customization file can be modified any time the interactive system is available, it is
critical to perform regular backups of the file at your site. This ensures ease of recovery of the
current site settings in case the file is accidentally lost.
You should limit update access to the interactive system, because the settings in this file apply to all
users. Online access to this file is controlled through a password screen; however, security
precautions may be appropriate.
File Repair, Re-Initialization, and Password Display
If a backup copy of the customization file is not available and recovery is required, the following
options exist using program G1CPDFL.
1. The first option is to physically delete the file and re-run the initialization job, DEFCUSTM.
2. A second option involves the same customization utility, but using job CUSTMUTL. In this case
the utility can be used to repair the G1CPFDF file or display the encrypted password. This job
performs the following tasks:
a. If an error is detected on the open to the customization file, the program attempts to create
the file.
b. If the attempt is not successful, the program issues an error message and terminates.
c. If the file is opened successfully, a read is attempted for the control record.
d. If the read for the control record fails, the customization utility adds the control record to the
file.
e. If the read for the control record is successful, the customization utility searches for the
admin (password) record.
Release 4.1.0
112
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Batch Uncoded Records Interface (G1CPBNC)
f. If the admin (password) record is found, the customization utility displays the encrypted
password stored on the record.
g. If the admin record is not found, the initial install password is written to the file.
If required, a decrypting of the password can be obtained by calling Pitney Bowes Technical
Support. The Technical Support Representative can use the 16-character hexadecimal
representation of the password to provide you with the current text value of the password.
Batch Uncoded Records Interface (G1CPBNC)
The Interactive CODE-1 Plus System includes a user exit that you can use to correct records that
were not coded by the batch product. The interface, G1CPBNC, reads an encoded records file
produced by batch CODE-1 Plus (C1BMNCO).The user exit is designed so that you can pull one
record at a time into the screen input area, correct the record, and then write the corrected record
out to a corrected file.

To take advantage of the batch non-coded records interface to Interactive CODE-1 Plus, you
or someone at your site must have modified the sample program, called G1CPBNC, to read
records from the C1BMNCO file, pass them to Interactive CODE-1 Plus, wait for the user to
correct the record, receive the records back from Interactive CODE-1 Plus, and then write the
corrected records to an output file. This is discussed later in this section.
Once you modify a G1CPBNC user exit program, refer to "How it Works” on page 113 to use the UR
and UW commands from the CODE-1 Plus Interactive screen.
Type the UR (User Read) command in the Command field. An address is pulled from the input file
and placed in the address input area.
How it Works
When you enter the UR command, the user exit program G1CPBNC is invoked and the functionality
supplied by the UR command is contained within this program. The same situation applies to the
UW command. You must customize the G1CPBNC to suit the need of your specific environment. A
sample user exit program that you can customize is supplied as part of the product.
In addition to the input and output addresses, the complete Command field containing the UR or
UW command is passed to the user exit so that additional command parameters can be required as
part of the UR or UW commands (for example, record number of the address being corrected). You
can specify several screen presentation options to control how the screen appears upon command
completion. These screen presentation options control:
•
•
•
•
•
Message that appears
Clearing of the Command field to blanks
Sounding of an audible alarm
Clearing of the address area to blanks
Cursor position upon the completion of the UR and UW commands
A sample program, G1CPBNC, is supplied with the CODE-1 Plus software. The program is written
to read the supplied IVPFILE and write the coded records to a user-defined output file. Your input file
may have different attributes (for example, record length or address element location) and will need
to be modified accordingly.
Release 4.1.0
113
User’s Guide - Open Systems
Batch Uncoded Records Interface (G1CPBNC)
In the following section, the required functionality for both the UR and UW commands is described,
the calling interface for G1CPBNC is explained, and excerpts from the sample G1CPBNC program
are shown. The UR and UW commands are enabled simply by making G1CPBNC available in the
run-time environment.

The remaining sections in this chapter are intended for programmers writing the G1CPBNC
user-exit program.
UR COMMAND
When you enter a UR (User Read) command, the G1CPBNC user exit program is invoked with
UXIT-FUNCTION set to UXIT-READ-FILE. The available functionality includes the following:
•
•
•
•
•
•
•
Select and read a record from a user file containing addresses which are to be supplied when
the UR command is entered. The selected address is passed to the calling program through the
UXIT-P9IN field. The user exit must enable for multiple terminal operators working at the same
time.
The entire Command field containing the UR command is available to the G1CPBNC program
so that additional user-defined parameters can be defined as part of the UR command. The
Command field is passed from the calling program through the UXIT-COMMAND-LINE field.
Specify the message that appears on the terminal screen at the completion of the UR command
in the UXIT-PROMPT-MESSAGE field.
Specify whether or not the Command field on the terminal screen is to be blanked-out upon
completion of execution for the UR command. This is specified via the UXIT-COMMAND field.
Specify whether or not an audible alarm is to sound at the completion of execution for the UR
command. This is specified via the UXIT-ALARM field.
Specify whether the cursor on the terminal screen is to be positioned on the address input lines
or the Command field at the completion of execution for the UR command. Since CODE-1 Plus
automatically performs an attempted match subsequent to a UR command, UXIT-CURSORCMD-ON-MTCH can be used to position the cursor on the command line (for an anticipated UW
command) on a match or in the address area on a non-match or multiple. This is specified via
the UXIT-CURSOR field.
In order to coordinate the execution of UR and UW commands, an area of statically allocated
memory is made available that is specific to one individual terminal user. This area is UXITSAVE-AREA.
UW COMMAND
When you enter a UW (User Write) command, the G1CPBNC user exit program is invoked with
UXIT-FUNCTION set to UXIT-WRITE-FILE.
The results from attempting to match the address currently on the terminal screen are passed to the
user exit in the UXIT-P9OUT and UXIT-P9AUDT fields. The user exit should determine whether to
accept the address and write it to a user file containing corrected addresses or reject the address
and display an error message on the terminal screen. The user exit must enable for multiple terminal
operators working at the same time.
•
•
Release 4.1.0
The entire Command field containing the UW command is available to the G1CPBNC program
so that additional user-defined parameters can be defined as part of the UW command. The
Command field is passed from the calling program through the UXIT-COMMAND-LINE field.
Specify the message which appears on the terminal screen at the completion of the UW
command in the UXIT-PROMPT-MESSAGE field.
114
User’s Guide - Open Systems
Chapter 4: Getting Started With Interactive Processing
Batch Uncoded Records Interface (G1CPBNC)
•
•
•
•
•
Specify whether or not the Command field on the terminal screen is to be blanked out upon
completion of execution for the UW command. This is specified via the UXIT-COMMAND field.
Specify whether or not an audible alarm is to sound at the completion of execution for the UW
command. This is specified via the UXIT-ALARM field.
Specify whether or not to clear the address input fields on the terminal screen at the completion
of execution for the UW command. This is specified via the UXIT-ADDRESS field.
Specify whether the cursor on the terminal screen is to be positioned on the address input lines
or the Command field at the completion of execution for the UW command. This is specified via
the UXIT-CURSOR field.
In order to coordinate the execution of UR and UW commands, an area of statically allocated
memory is made available that is specific to one individual terminal user and common to both the
UR and UW commands. This area is UXIT-SAVE-AREA.
Program Parameters
Eleven logical parameters are passed in a single 01 level. These eleven parameters are as follows:
The G1CPBNC Option Call Areas (Part 1 of 2)
Position
1-2
Name
EXITFUNCTION
Length
in Bytes
2
Contents
Function code for this call. Your program must pass one
of the following function codes:
• CL — Close the file.
• OP — Open the file.
• UR — Perform a read.
• UW — Perform a write.
3-42
UXITCOMMANDLINE
40
Command line from the Interactive CODE-1 Plus
Command field.
43-121
UXIT-PROMPTMESSAGE
79
Message prompt that appears on the online screen after
the return from this program.
122
UXITCOMMAND
1
Indicates whether or not to clear the command after
completion of the UR or UW command.
• Y — Clear the Command field after completion of the
UR or UW command.
• N — Do not clear the Command field.
123
UXIT-ALARM
1
Indicates whether or not to sound an audible alarm at the
completion of the UR or UW command.
• Y — Sound an audible alarm at the completion of the
UR or UW command.
• N — Do not sound an alarm.
124
UXIT-ADDRESS
1
Indicates whether or not to clear the address upon
completion of the UW command. Not used during the
processing for a UR command.
• Y — Clear the address area upon completion of the UR
or UW command.
• N — Do not clear the address area.
Release 4.1.0
115
User’s Guide - Open Systems
Batch Uncoded Records Interface (G1CPBNC)
The G1CPBNC Option Call Areas (Part 2 of 2)
Position
Name
125
UXIT-CURSOR
Length
in Bytes
1
Contents
Indicates whether or not to place the cursor in the address
fields at the completion of the UR or UW command.
• Y — Place the cursor in the address area.
• N — Place the cursor at the Command field.
• M — Place the cursor at the Command field on a
match, or in the address area on a non-match or
multiple.
126-221
UXITRESERVED
96
Reserved.
222-721
UXIT-P9IN
500
During the processing for a UR command, this program
should place the address which it is preparing to enter
onto the online screen into this area. This field is not used
during the processing of a UW command.
722-5721
UXIT-P9OUT
5,000
During the processing for a UW command, this area
contains the P9OUT area for the current address at the
time the UW command was invoked. Not used during the
processing of a UW command.
5722-6121
UXIT-P9AUDT
400
During the processing for a UW command, this area
contains the P9AUDT area for the current address at the
time the UW command was invoked. Not used during the
processing of a UR command.
6122-6621
UXIT-SAVEAREA
500
Memory that is statically allocated and preserved
between invocations of the user exit.
Description of Supplied Sample G1CPBNC
When the UR command is invoked, this sample program sequentially reads an address record from
the G1CPIVP file. As each address is displayed in response to each UR command, the Command
field on the terminal screen is cleared to blanks, a message is displayed on the terminal screen
indicating a successful read, no audible alarm is given, and the cursor is positioned to the address
input area on the terminal screen. If at the end of the file (“end of file”), the Command field is not
cleared to blanks, an error message is displayed on the terminal screen, an audible alarm is
sounded, and the cursor is positioned to the Command field on the terminal screen.
When the UW command is invoked, the program first checks to ensure that a UR command
preceded the UW command. If it did, then it next checks to see if an address match was successful
for the current address. The corrected address could then be written to an user file. If the UW
command was successful, then the Command field on the terminal screen is cleared to blanks, a
message is displayed on the terminal screen indicating a successful write, and no audible alarm is
given. If the UW command was not successful, then the Command field is not cleared to blanks, an
error message is displayed on the terminal screen, and an audible alarm is sounded. In either case,
the cursor is positioned to the Command field on the terminal screen.

Release 4.1.0
The delivered version of G1CPBNC is set up to perform file I/O against the IVP output
unmatched records file C1BMNCO. In CICS, the program reads and writes to extra partition
datasets. The transient data queues are “G1IV” (read) and “G1OV” (write). On all other
platforms, the input sequential dataset is “G1CPIVP,” and the output is to “G1CPOVP”. All
datasets have LRECL=256, and BLKSIZE is determined by the job control language.
116
User’s Guide - Open Systems
Generating CODE-1 Plus
Reports
In this chapter:

















Understanding the CODE-1 Plus Reports . . . . . . . . . . . . . . . . . .118
Address-Match Execution Statistics Report . . . . . . . . . . . . . . . .119
Control Totals Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Execution Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Parameter Record Listing Report . . . . . . . . . . . . . . . . . . . . . . . . .121
Analysis of Matched Records Report. . . . . . . . . . . . . . . . . . . . . .121
Build Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Coding by State Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Coding by List Code Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Coding by 3-Digit ZIP Code Reports. . . . . . . . . . . . . . . . . . . . . . .126
Processing Summary Reports . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Delivery Point Validation Processing Summary Report . . . . . . .128
Delivery Point Validation Processing by List Code Report . . . .128
Residential Delivery File Build Report . . . . . . . . . . . . . . . . . . . . .128
Residential Delivery File Build Execution Log . . . . . . . . . . . . . .128
National Deliverability Index (NDI) Report . . . . . . . . . . . . . . . . . .128
USPS Form 3553. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
5
Understanding the CODE-1 Plus Reports
Understanding the CODE-1 Plus Reports
Required Reports
CODE-1 Plus automatically generates the following reports for all jobs:
•
•
•
•
Address-Match Execution Statistics
Control Totals Report
Execution Log
Parameter Record Listing
Optional Reports
In addition to the automatically generated required reports, you can generate the following optional
reports:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Analysis of Matched Records
Build Report
Carrier Coding by 3-Digit ZIP
Carrier Coding by List Code
Carrier Coding by State
Delivery Point Validation Processing Summary.
Delivery Point Validation by List Code
Line of Travel Coding by 3-Digit ZIP
Line of Travel Coding by List Code
Line of Travel Coding by State
National Delivery Index (NDI)
Processing Summary by 3-Digit ZIP
Processing Summary by List Code
Processing Summary by State
Residential Delivery File Build Execution Log
Residential Delivery File Build Report
USPS Form 3553
ZIP + 4 Coding by State
ZIP + 4 Coding by List Code
ZIP + 4 Coding by 3-Digit ZIP
Report Parameter
You can use the REPORT parameter to define the reports to generate when you submit a batch job.
For more information on the REPORT parameter, please refer to the section “REPORT” in your
CODE-1 Plus Reference Guide.
Build Parameter
You can use the BUILD parameter to generate the BUILD report. For more information on the BUILD
parameter, please refer to the section “BUILD” in your CODE-1 Plus Reference Guide.
Release 4.1.0
118
User’s Guide - Open Systems
Chapter 5: Generating CODE-1 Plus Reports
Address-Match Execution Statistics Report
Address-Match Execution Statistics Report
The Address-Match Execution Statistics Report provides information on the reads and calls CODE-1
Plus makes to the various database files and program modules during job execution. This report
prints automatically when your job runs and cannot be suppressed. This report includes the
following information.
Address-Match Execution Statistics Report
Field
Description
Number of CODE-1 Plus
Database Reads
Number of database reads CODE-1 Plus did to each logical file in the
database.
Total CODE-1 Plus
Database Reads
Total number of database reads CODE-1 Plus did to the entire CODE-1
Plus database.
Number of Database
Read Requests
Number of database read requests CODE-1 Plus did to each logical file.
Total CODE-1 Plus
Database Read Requests
Total number of database read requests CODE-1 Plus did to the entire
CODE-1 Plus database.
Address-Match Calls
Number of records requiring address match calls, broken down by the
number of records requiring 1 call, 2 calls, 3 calls, and 4 calls.
Total analyzer invocations
Number of times the CODE-1 Plus driver program called the C1ANZADR
module.
ZIP Code setup
operations
Number of times CODE-1 Plus determined a locality.
Match Attempts and
Matches Obtained
Statistics for the different types of matches attempted and maintained
(Original ZIP, city-based locality, Finance-NR-based locality, etc.).

Release 4.1.0
A database read request is a request for data that can be satisfied either with information on
disk or information already in memory. A database read cannot be satisfied with the
information in memory. CODE-1 Plus must access the database on disk to satisfy the read
request.
119
User’s Guide - Open Systems
Control Totals Report
Control Totals Report
This Control Totals Report provides statistics on processed, matched, and unmatched records for a
job. The top of the Control Totals Report displays the CODE-1 Plus release and the vintage dates of
the installed databases. This report prints automatically when your job is run and cannot be
suppressed. Counts and percentages print for the following fields.
Control Totals Report
Field
Description
Input Name/Address
Records Read
Number of records read from the input name-and-address file C1BMNAM.
Name/Address Records
Processed
Number of records processed. If you used the Z4CHANGE option, the
Bypassed by Z4CHANGE Option entry appears after the Input Name/
Address Records Read, File C1BMNAM entry. The Z4CHANGE entry
shows how many input records did not have to be processed based on the
Z4CHANGE Master File.
Total Records for Which
Address Match Attempted
Number of records for which a record match was attempted against the
database. The subcategories for this field are the following:
• Original ZIP Code Confirmed—the input ZIP Code matched the
database.
• New ZIP Code Determined—the ZIP Code was changed from the input
as the result of a database match.
• Multiple New ZIP Codes Determined—these records were not
matched because the input ZIP Code was not correct and there were
multiple possible new ZIP Codes.
• Original ZIP Code Retained—(No Address Match Possible)—these
records were not matched, but since the input ZIP Code was a valid
USPS ZIP Code, it was retained.
• No ZIP Code Available—these records were not coded and the input
ZIP Code could not be retained because it was invalid.
Total Unmatched Records
Statistics for the records that could not be matched against the USPS
database, broken down by result code. This category is a breakdown of the
records indicated in the last three sub-categories listed above.
Total Records
Successfully Matched
Total number of records that were successfully matched and stored on the
output file.
ZIP + 4 Code Stored
Successfully
Number of records that were stored with valid ZIP + 4 Codes.
Carrier Route Code
Stored Successfully
Number of records that were stored with valid carrier route codes.
Standard Address Stored
Successfully
Number of records that were stored with valid standardized addresses.
Line of Travel Coding
Attempts
Number of records for which an attempt was made to retrieve a LOT Code.
Address Match Yielding
Street Alias
Number of records that were matched, and which contained a street alias.
Records Matching USPS
Record Types
Number of records that were matched, broken down by USPS Record type.
Records Receiving Bnnn,
Cnnn, Hnnn, and Rnnn
Number of records receiving each type of carrier route code.
Release 4.1.0
120
User’s Guide - Open Systems
Chapter 5: Generating CODE-1 Plus Reports
Execution Log
Execution Log
This Execution Log provides information on the steps that CODE-1 Plus executes when processing
your name-and-address file. This report generates automatically while your job is running and
cannot be suppressed. The Execution Log is helpful if your job ends by providing details on how far
CODE-1 Plus processed the job got before terminating the job. If you call Technical Support, please
have this report available for reference.
Parameter Record Listing Report
This Parameter Record Listing shows all of the parameters that are used to define a particular job.
The Parameter Record Listing prints automatically when a job is run and cannot be suppressed. If
you need to call Pitney Bowes Technical Support about a problem with any of your jobs, please have
this report available for reference.
Analysis of Matched Records Report
The Analysis of Matched Records Report provides information on:
•
•
•
•
•
Total number of records that were processed
Number of processed records successfully matched
Match details on input directionals, suffixes, and apartment numbers
Quality of the input file using “Probable Correctness” values
Combined probable correctness percentage for the entire input file
If any report field contains 0, the field does not print on the report.
Build Report
The Build Report displays the release version information for major batch programs. To generate the
Build Report, define the BUILD parameter for your batch job. For more information on the BUILD
parameter, please refer to the section “BUILD” in your CODE-1 Plus Reference Guide.
Release 4.1.0
121
User’s Guide - Open Systems
Coding by State Reports
Coding by State Reports
This section provides information for the coding by state reports.
ZIP + 4 Coding by State Report
The ZIP + 4 Coding by State Report shows the results of ZIP + 4 coding for each state and provides
the following information.
Field
Description
ZIP Code Mismatch
ZIP Code could not be determined.
Insufficient Address
Not enough address information was provided.
Street Mismatch
Street name could not be determined.
House Number Mismatch
House number could not be determined.
Apartment Number Mismatch
Apartment number could not be determined.
Matched
Number of records matched with ZIP + 4 Codes or
carrier route codes (depending on the report).
Multiple Matches
Number of records for which multiple matches were
found for ZIP + 4 Codes or carrier route codes
(depending on the report).
Address Information Dropped
Number of records that had address information
dropped.
Probable Correctness Too High
Number of records that exceeded the maximum
probable correctness values you specified for the job.
Stored
Number of records stored with ZIP + 4 Codes.
Percent Stored
Percentage of the input file stored that was ZIP + 4
coded.
Carrier Coding by State Report
The Carrier Coding by State Report shows the results of carrier route coding for each state and
provides the following information.
Field
Description
ZIP Code Mismatch
ZIP Code could not be determined.
Insufficient Address
Not enough address information was provided.
Street Mismatch
Street name could not be determined.
House Number Mismatch
House number could not be determined.
Apartment Number Mismatch
Apartment number could not be determined.
Matched
Number of records matched with carrier route codes
(depending on the report).
Release 4.1.0
122
User’s Guide - Open Systems
Chapter 5: Generating CODE-1 Plus Reports
Coding by State Reports
Field
Description
Multiple Matches
Number of records for which multiple matches were
found for carrier route codes (depending on the report).
Address Information Dropped
Number of records that had address information
dropped.
Probable Correctness Too High
Number of records that exceeded the maximum
probable correctness values you specified for the job.
Stored
Number of records stored with carrier route codes.
Percent Stored
Percentage of the input file stored that was carrier route
coded.
Line of Travel Coding by State Report
The Line of Travel Coding by State Report is broken down differently. After the number of records
processed for each state, the report is broken down as follows.
Field
Description
State
State for which Line of Travel coding statistics are
listed.
Number Processed
Number of records processed for the state.
ZIP + 4 Level LOT Coded
Number of records for which a LOT code was assigned
at the ZIP + 4 level.
Pct of Nr Processed
Percentage of records that were LOT coded at the
ZIP + 4 level.
Default LOT Coded
Number of records coded with a default LOT code.
Pct of Nr Processed
Percentage of records that were default LOT coded.
Uncoded
Number of records that were not LOT coded.
Pct of Nr Processed
Percentage of records that were not LOT coded.
Total
Total for each field on report.
Release 4.1.0
123
User’s Guide - Open Systems
Coding by List Code Reports
Coding by List Code Reports
This section provides information for the coding by list code reports.
ZIP + 4 Coding by List Code Report
The ZIP + 4 Coding by List Code Report lists the input list code, followed by the number of input
records for that code and provides the following information.
Field
Description
ZIP Code Mismatch
ZIP Code could not be determined.
Insufficient Address
Not enough address information was provided.
Street Mismatch
Street name could not be determined.
House Number Mismatch
House number could not be determined.
Apartment Number Mismatch
Apartment number could not be determined.
Matched
Number of records matched with ZIP + 4 Codes
(depending on the report).
Multiple Matches
Number of records for which multiple matches were
found for ZIP + 4 Codes.
Address Information Dropped
Number of records that had address information
dropped.
Probable Correctness Too High
Number of records that were not stored because they
exceeded the maximum probable correctness values
you specified for the job.
Stored
Number of records stored with ZIP + 4 Codes or carrier
route codes,
Percent Stored
Percentage of the input file stored that was ZIP + 4
coded or carrier route coded.
Carrier Route Coding by List Code Report
The Carrier Route Coding by List Code Report lists the input list code, followed by the number of
input records for that code and provides the following information.
Field
Description
ZIP Code Mismatch
ZIP Code could not be determined.
Insufficient Address
Not enough address information was provided.
Street Mismatch
Street name could not be determined.
House Number Mismatch
House number could not be determined.
Apartment Number Mismatch
Apartment number could not be determined.
Release 4.1.0
124
User’s Guide - Open Systems
Chapter 5: Generating CODE-1 Plus Reports
Coding by List Code Reports
Field
Description
Matched
Number of records matched with carrier route codes
(depending on the report).
Multiple Matches
Number of records for which multiple matches were
found for carrier routes.
Address Information Dropped
Number of records that had address information
dropped.
Probable Correctness Too High
Number of records that were not stored because they
exceeded the maximum probable correctness values
you specified for the job.
Stored
Number of records stored with carrier route codes.
Percent Stored
Percentage of the input file stored that was carrier route
coded.
Line of Travel Coding by List Code Report
The Line of Travel Coding by List Code Report is broken down differently. After the number of
records processed for each state, the report is broken down as follows.
Field
Description
List Code
List code for which Line of Travel coding statistics are
listed.
Number Processed
Number of records processed for the list code.
ZIP + 4 Level LOT Coded
Number of records for which a LOT code was assigned
at the ZIP + 4 level.
Pct of Nr Processed
Percentage of records that were LOT coded at the
ZIP + 4 level.
Default LOT Coded
Number of records coded with a default LOT code.
Pct of Nr Processed
Percentage of records that were default LOT coded.
Uncoded
Number of records that were not LOT coded.
Pct of Nr Processed
Percentage of records that were not LOT coded.
Total
Total for each field on report.
Release 4.1.0
125
User’s Guide - Open Systems
Coding by 3-Digit ZIP Code Reports
Coding by 3-Digit ZIP Code Reports
This section provides information for the Coding by 3-Digit reports.
ZIP + 4 Coding by 3-Digit ZIP Code Reports
The ZIP + 4 Coding by 3-Digit ZIP Code Report provides the following information.
Field
Description
ZIP Code Mismatch
ZIP Code could not be determined.
Insufficient Address
Not enough address information was provided.
Street Mismatch
Street name could not be determined.
House Number Mismatch
House number could not be determined.
Apartment Number Mismatch
Apartment number could not be determined.
Matched
Number of records matched with ZIP + 4 Codes.
Multiple Matches
Number of records for which multiple matches were found for
ZIP + 4 Codes.
Address Information Dropped
Number of records that had address information dropped.
Probable Correctness Too High
Number of records that were not stored because the records
exceeded the maximum probable correctness values specified
for the job.
Stored
Number of records stored with ZIP + 4 Codes.
Percent Stored
Percentage of the input file stored that was ZIP + 4 coded.
Carrier Coding by 3-Digit ZIP Code Reports
The Carrier Coding by 3-Digit ZIP Code Report provides the following information.
Field
Description
ZIP Code Mismatch
ZIP Code could not be determined.
Insufficient Address
Not enough address information was provided.
Street Mismatch
Street name could not be determined.
House Number Mismatch
House number could not be determined.
Apartment Number Mismatch
Apartment number could not be determined.
Matched
Number of records matched with carrier route codes.
Multiple Matches
Number of records for which multiple matches were
found for carrier route codes.
Address Information Dropped
Number of records that had address information
dropped.
Release 4.1.0
126
User’s Guide - Open Systems
Chapter 5: Generating CODE-1 Plus Reports
Processing Summary Reports
Field
Description
Probable Correctness Too High
Number of records that were not stored because the
records exceeded the maximum probable correctness
values specified for the job.
Stored
Number of records stored with carrier route codes.
Percent Stored
Percentage of the input file stored that was ZIP + 4
coded or carrier route coded.
Line of Travel Coding by 3-Digit ZIP Code Report
The Line of Travel Coding by 3-Digit ZIP Code Report provides the following information.
Field
Description
3-Digit
3-Digit code for which Line of Travel coding statistics
are listed.
Number Processed
Number of records processed for the 3-Digit ZIP Code.
ZIP + 4 Level LOT Coded
Number of records for which a LOT code was assigned
at the ZIP + 4 level.
Pct of Nr Processed
Percentage of records that were LOT coded at the ZIP
+ 4 level.
Default LOT Coded
Number of records coded with a default LOT code.
Pct of Nr Processed
Percentage of records coded with a default LOT code.
Uncoded
Number of records that were not LOT coded.
Pct of Nr Processed
Percentage of records that were not LOT coded.
Total
Total for each field on report.
Processing Summary Reports
The Processing Summary reports show—by state, list code, or 3-digit ZIP Code—totals for the
following categories:
•
•
•
•
•
•
•
•
•
•
•
Release 4.1.0
Records Processed—number of records processed for this job
Address Mismatches—number of records for which no address could be determined
Multiple Matches—number of records for which multiple matches were found
Unique Matches—number of records for which there was only a single, unique match
determined
Number of ZIP Codes Stored—number of records that were stored with ZIP Codes
Percentage of ZIP Codes Stored
Number of Records Stored with ZIP + 4 Codes
Percentage of Records Stored with ZIP + 4 Codes—Percentage of total number of records
stored with ZIP + 4 Codes
Number of Records Stored with Carrier Route Codes
Percentage of Records Stored with Carrier Route Codes
Number of Records Stored with Standardized Addresses
127
User’s Guide - Open Systems
Delivery Point Validation Processing Summary Report
•
•
•
Percentage of Records Stored with Standardized Addresses
Number of Records Stored with City and State—Number of records stored with matched city and
state information
Percentage of Records Stored with City and State
Delivery Point Validation Processing Summary Report
This report shows you statistics about processed, matched, and unmatched records for a job. This
report is printed automatically when your job is run. You cannot turn this feature off.
Delivery Point Validation Processing by List Code Report
This report shows you statistics about processed, matched, and unmatched records for a job. This
report is printed automatically when your job is run; you cannot turn this feature off.
Residential Delivery File Build Report
You will find the following information on this report:
•
•
Parameter given
Control totals for your RDI File build job
Residential Delivery File Build Execution Log
You will find the following information on the execution log:
•
•
•
Date and time of the RDI File build
Number of 9-digit input records
Number of 11-digit input records
National Deliverability Index (NDI) Report
The National Deliverability Index System (NDI) measures and improves address quality through
seven quality indicators. The NDI Report shows how many records fulfill each criteria required for
each quality indicator. The categories are represented by the number of addresses:
•
•
•
•
•
Release 4.1.0
Matched and standardized against the ZIP + 4 file
Containing apartment numbers
Containing rural route and box number information
Containing correct 5-digit ZIP Codes
Containing carrier route codes
128
User’s Guide - Open Systems
Chapter 5: Generating CODE-1 Plus Reports
USPS Form 3553
USPS Form 3553
The USPS Form 3553 is a facsimile of the Postal Form 3553. This form is produced automatically
when you are using a CASS-certified configuration in CODE-1 Plus and is required by the Postal
Service.
•
•
•
•
•
Section A of the form contains the name of the CASS-certified vendor (Pitney Bowes), the name
of the software, the release number, and the configuration used. For Z4CHANGE and LOT
processing, the form contains the Z4CHANGE and LOT vendor name, the name of the
Z4CHANGE or LOT software, the release number, and the configuration used.
Section B of the form contains information about your name-and-address list, including the date
you processed your list against the Master file, Z4CHANGE option, or LOT database. It also
contains the date (month and year) of the ZIP + 4 (Master file), Z4CHANGE, and LOT
databases. Additional list information is also provided, including the total number of records
processed.
Section C of the form contains information about your output file, including information about the
number of records ZIP + 4 Coded, delivery point coded, 5-digit ZIP Coded, carrier route coded,
LOT coded, and processed by the Z4CHANGE option, and the dates through which the file is
valid.
Section D of the form contains information about the mailer.
Section E of the form contains the Qualitative Statistical Summary and information regarding
high rise, military, and rural route defaults, LACS data, DPV, and EWS.

Pages 2 and 3 of the USPS Form 3553 contain detailed descriptions of each field on the
form.
For more information, please see http://about.usps.com/forms/ps3553.pdf.
Release 4.1.0
129
User’s Guide - Open Systems
USPS Form 3553
Release 4.1.0
130
User’s Guide - Open Systems
Using Z4CHANGE
In this chapter:




What is the Z4CHANGE Option?. . . . . . . . . . . . . . . . . . . . . . . . . .132
Using Z4CHANGE Option Processing . . . . . . . . . . . . . . . . . . . . .133
Calling Z4CHANGE From Your Own Driver . . . . . . . . . . . . . . . . .134
Generating Reports for Z4CHANGE Processing . . . . . . . . . . . . .135
6
What is the Z4CHANGE Option?
What is the Z4CHANGE Option?
The Z4CHANGE Option is a product provided by the USPS that can save you a considerable
amount of processing time. The Z4CHANGE Option is extremely useful if you have large name-andaddress files that you use frequently. The Z4CHANGE Option enables you to run that file through
CODE-1 Plus and attempt to match:
•
•
Only those records with ZIP + 4 Codes changed by the USPS since the file was last processed.
Records that were not successfully coded on previous CODE-1 Plus runs.
In other words, if you have a list that you already processed using CODE-1 Plus, you can run the list
each month using the Z4CHANGE Option processing, and attempt to match those records with new
ZIP + 4 Codes.

Before you use the Z4CHANGE Option, you must run your entire file through CODE-1 Plus
one time without using Z4CHANGE Option. Then, each time you want to mail records from
your file, run the file again using Z4CHANGE Option processing. Your list stays current, but
you do not expend processing time confirming records that were already correct.
The Z4CHANGE Option Database
Included with your CODE-1 Plus software is a Z4CHANGE Option database. The database is
published by the USPS every month and contains all of the ZIP+4 Codes that the USPS changed in
the previous 12-month period.
Rules for Using the Z4CHANGE Option
The USPS instituted the following rules regarding Z4CHANGE Option processing:
•
•
•
You must initially run your entire mailing list through CASS-certified software.
Subsequently, it is sufficient to use Z4CHANGE Option processing on that list to maintain its
compliance with CASS rules.
You must run the entire file again at the end of the third year following initial Z4CHANGE Option
certification. (This means that you do not need to run the file through CASS-certified software
every year, as long as you are using Z4CHANGE Option processing.)

If the USPS determines that significant changes were made to the CASS requirements, you
must reprocess your entire list using recently-certified software.
Activating the Z4CHANGE Option
To activate and use Z4CHANGE (C1P430), you can either pass, as parameters, the names of predefined call areas, or use the CS ZIP parameter and the Z4 OUT parameter to provide all the
information necessary to perform the function accurately and return the appropriate information. For
more information on these parameters and call areas, please refer to your CODE-1 Plus Reference
Guide.
Release 4.1.0
132
User’s Guide - Open Systems
Chapter 6: Using Z4CHANGE
Using Z4CHANGE Option Processing
Using Z4CHANGE Option Processing
This section describes the changes to make to your CODE-1 Plus jobs to use Z4CHANGE Option
processing (C1P430).
Parameters
To use Z4CHANGE Option processing, add fields to the CS ZIP and Z4 OUT parameters from a
standard job. Follow the instructions below to perform Z4CHANGE Option processing in your batch
job.
Process Your Entire List Through CODE-1 Plus
To write the database vintage date in the output records:
1. In position 26-28 of the Z4 OUT parameter, specify the location for the database vintage date.
2. In position 30 of the Z4 OUT parameter, specify one of the following codes to indicate the format
of the vintage date:
•
•
•
•
•
•
C — 4-byte character format (YYMM) (default)
P — 3-byte packed decimal format (YYMM)
B — 2-byte binary format (YYMM)
3 — 3-byte binary format (YYYYMM)
6 — 6-byte character format (YYYYMM)
4 — 4-byte packed decimal format (YYYYMM)
Each Month, Process Your File Again
If the vintage date is stored in your input records:
1. In positions 44-46 of the CS ZIP parameter, write the location of the master file vintage date in
the input records.
2. In position 48 of the CS ZIP parameter, write one of the following format codes to tell CODE-1
Plus the format of the vintage date in the input records:
•
•
•
•
•
•
C — 4-byte character format (YYMM) (this is the default)
P — 3-byte packed decimal format (YYMM)
B — 2-byte binary format (YYMM)
3 — 3-byte binary format (YYYYMM)
6 — 6-byte character format (YYYYMM)
4 — 4-byte packed decimal format (YYYYMM)
3. In positions 32-34 of the Z4 OUT parameter, write the location for the output Z4CHANGE Option
Return Code. One of the following codes will be stored in the position you specify:
•
•
•
0 — Address matching was not required for this record (the USPS has not changed this ZIP
+ 4 Code since the database vintage date).
4 — Address matching was required for this record (the USPS has changed this ZIP + 4
Code since the database vintage date).
8 — A fatal error occurred during processing.
If the vintage date is not stored in your input records:
1. In positions 50-55 of the CS ZIP parameter, specify the vintage date of the master file that was
used to process this list the last time the list was processed. Write the date in YYYYMM format.
Release 4.1.0
133
User’s Guide - Open Systems
Calling Z4CHANGE From Your Own Driver
2. In positions 32-34 of the Z4 OUT parameter, write the location for the output Z4CHANGE Option
return code. One of the following codes is stored in the position you specify:
•
•
•
0 — Address matching was not required for this record (the USPS has not changed this
ZIP+4 Code since the database vintage date).
4 — Address matching was required for this record (the USPS has changed this ZIP+4 Code
since the database vintage date).
8 — A fatal error occurred during processing.
Calling Z4CHANGE From Your Own Driver
If you are using your own batch driver for CODE-1 Plus and you want to use the Z4CHANGE
processing, use the following call area to invoke C1P430. A COBOL copy book of this area is
included on your software distribution media as Z4CPARM.

The C1PRPT callable report program does not print a USPS Form 3553 that reflects
Z4CHANGE Option processing. If you want an automated Form 3553 facsimile, you must
use the C1BM00 batch driver to run CODE-1 Plus.
The Z4CHANGE Option call area layout follows.
Z4CHANGE Call Areas (Part 1 of 2)
Position
1
Name
PARM-FUNCTION
Length
Contents
1
Function code for this call. Your program must pass
one of the following function codes:
• O — Open the Z4CHANGE Option database and
(optionally) check dates.
• P — Process ZIP check request.
• C — Close the Z4CHANGE Option database.
2-6
PARM-5-DIGIT ZIP
5
5-digit ZIP Code.
7-10
PARM-4-DIGIT ZIP
4
4-digit ZIP+4 Code.
11-16
PARM-DATECODED-VINTAGE
YYYYMM format
6
If PARM-FUNCTION is set to O, your program must
pass the date of the CODE-1 Plus database being used
for this CODE-1 Plus run. This date will be compared to
the date of the Z4CHANGE Option database to ensure
that they are the same. CODE-1 Plus will then pass the
vintage date on the Z4CHANGE Option database back
to your calling program through this field.
If PARM-FUNCTION is set to P, your program must
pass the date (in YYYYMM format) of the master file
that was last used to match the record whose ZIP Code
is now being checked.
If PARM-FUNCTION is set to C, this field is ignored.
NOTE: This field uses a four-digit year in YYYY format.
If leading zeroes are passed in lieu of century, century
will be calculated using the 80/20 rule. That is, YY less
than 80 will assume century=20, otherwise will assume
century=19.
17-29
N/A
13
Reserved.
30-39
PARM-DBLIB
10
Name of the library that holds the Z4CHANGE Option
master file. Used for AS/400 only.
Release 4.1.0
134
User’s Guide - Open Systems
Chapter 6: Using Z4CHANGE
Generating Reports for Z4CHANGE Processing
Z4CHANGE Call Areas (Part 2 of 2)
Position
40
Name
PARM-RETURNCODE
Length
Contents
1
This 1-character field is filled by C1P430 after the ZIP
Code is checked. One of the following codes is written
to this field.
• 0 — If PARM-FUNCTION is O, this means the file
has been successfully opened and the dates match.
If PARM-FUNCTION is P, this means the 9-digit ZIP
Code has not been changed by the USPS since the
last time the record was checked.
If PARM-FUNCTION is C, this means the file has
been closed.
• 4 — If PARM-FUNCTION is O, this means the
database was already opened.
If PARM-FUNCTION is P, this means either the 9digit ZIP Code has changed since the last time the
record was checked, or the ZIP Code was not
numeric.
If PARM-FUNCTION is C, this means the file wasn't
open, and therefore could not be closed.
• 8 — If PARM-FUNCTION is O, this means the
database could not be opened successfully, or the
dates don't match.
If PARM-FUNCTION is P, this means that the
database was not open.
If PARM-FUNCTION is C, this code is never
returned.
41-65
Reserved
25
Reserved.
Generating Reports for Z4CHANGE Processing
When you run a Z4CHANGE job, you can also generate reports about the Z4CHANGE job run.
These reports contain important processing information and include a Parameter Record Listing,
CASS Form, Control Totals, Analysis of Matched Records, and Address Execution Statistics
Reports. For more information on each of these reports, refer to "Generating CODE-1 Plus Reports”
on page 117.
z/OS Environment
The mainframe environment generates the Z4CHANGE reports automatically when you specify
Z4CHANGE options in your batch job.
UNIX Environment
To generate the Z4CHANGE Report in a Unix environment, follow these instructions.
1. Edit the /data/samz4c.c1bmprm file for your site’s needs.
2. Change your working directory to the product directory:
cd $g1dir/c1p
Release 4.1.0
135
User’s Guide - Open Systems
Generating Reports for Z4CHANGE Processing
3. Setup the verification job (sample) environment variables by sourcing the sample with the
following command:
bin/samz4c
source bin/samz4c.csh
(for Bourne shells)
(for C-Shell)
4. Next, submit the sample job by entering the following command:
bin/runc1bm00
The job runs in the background and takes up to 15 minutes to complete. You may monitor its
progress using the ps command.
Windows Environment
To generate the Z4CHANGE Report in a Windows environment:
1. Copy the SAMZ4C.BAT file.
2. Modify the file to meet your needs.
3. Run the file.
Pitney Bowes provides the SAMZ4C.BAT file in your CMDS directory. To edit this file:
1. Double-click on the Edit Job File icon.
2. Specify SAMZ4C as the job to edit.
Release 4.1.0
136
User’s Guide - Open Systems
Using Delivery Point
Validation
In this chapter:







What is Delivery Point Validation? . . . . . . . . . . . . . . . . . . . . . . . .138
Using the Delivery Point Validation Database . . . . . . . . . . . . . . .139
Activating Delivery Point Validation . . . . . . . . . . . . . . . . . . . . . . .143
Understanding DPV Return Information . . . . . . . . . . . . . . . . . . .143
DPV Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
DPV Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
What If My Mailing Generates a Seed Violation? . . . . . . . . . . . .146
7
What is Delivery Point Validation?
What is Delivery Point Validation?
The USPS introduced Delivery Point Validation (DPV) to validate the accuracy of address data to the
physical delivery point.

The USPS regulations require Delivery Point Validation (DPV) processing for CASS
certification.
CODE-1 Plus does not validate addresses at the specific delivery-point level. CODE-1 Plus only
confirms whether an address falls within the low-to-high address range encoded for the named
street. CODE-1 Plus uses the DPV option to determine whether the actual address exists to the
apartment or suite information level. The DPV option reduces your undeliverable-as-addressed
(UAA) mail volume that results from inaccurate addresses to reduce postage costs and costs
associated with the handling of inaccurate address information.
Delivery Point Validation processing also confirms whether an address is a commercial mail
receiving agency (CMRA) that uses private mail boxes (PMB). You can use DPV to determine the
potential validity of PMB information on an input address.
Although DPV can validate the accuracy of an existing address, it cannot be used to create address
lists. The DPV product is a secure dataset of USPS addresses and does NOT contain addresses
that are not delivered by the USPS.
Resolving Multiple Matches
Delivery Point Validation processing can also resolve multiple matches from the ZIP + 4 database to
increase the number of ZIP + 4 coded records in your address list.
The DPV option processes every ZIP + 4 coded record against the DPV files to resolve multiple
matches to the ZIP + 4 database. Resolving ZIP + 4 multiple matches increases your ZIP + 4 match
rate, but also increases processing time. For this reason, you may wish to turn off some of these
options.
Use the DPVIN parameter to define the options for multiple match conditions. When verifying proper
candidates for DPV processing, the multiple match condition is first checked at the ZIP Code level,
carrier route, directional, and then suffix. Multiple match conditions can occur in multiple categories.
The DPVIN parameter includes options for unique ZIP Code and small town default assignments
and multiple secondary components. The following figure provides examples of multiple matches
that can be Delivery Point Validated.
For more information on setting up multiple match options, refer to “DPVIN” in your CODE-1 Plus
Reference Guide.
Release 4.1.0
138
User’s Guide - Open Systems
Chapter 7: Using Delivery Point Validation
Using the Delivery Point Validation Database
Figure 1: Multiple Match Examples
Using the Delivery Point Validation Database
Delivery Point Validation requires a separate database. Pitney Bowes provides an updated DPV
database every month. The DPV database must be kept in synch with the USPS ZIP + 4 data. To
use DPV processing, you must license the DPV option from Pitney Bowes and install a License
Management key as required by the USPS. Please refer to your License Management Guide for
more information on obtaining your permanent license key for DPV.
The following table describes the DPV database 120-day expiration cycle.
DPV Database Expiry Cycle (Part 1 of 2)
Database Month
Release 4.1.0
Expiration
January
April 30
February
May 31
March
June 30
April
July 31
139
User’s Guide - Open Systems
Using the Delivery Point Validation Database
DPV Database Expiry Cycle (Part 2 of 2)
Database Month
Expiration
May
August 31
June
September 30
July
October 31
August
November 30
September
December 31
October
January 31
November
February 28
December
March 31
Windows
After product installation and the appropriate variables have been defined, you are ready to load the
database files. The following steps describe how to load the DPV Database.

To expedite the installation of Link product databases Pitney Bowes recommends you unzip
each Link product – Split DPV, Full DPV, Flat DPV, LACSLink and SuiteLink files into separate
subfolders before loading them into DB folder. Otherwise all Link products will be loaded
simultaneously which may delay Link product database installation.
1. To install your DPV database from internet download, follow these steps.
a.
b.
c.
d.
e.
f.
Log in to the Technical Support website at http://www.g1.com/support.
Click My Products.
Click the product link to access the appropriate databases to install.
Click View Available Downloads for your platform.
Click Databases and download the database file(s) for your product.
Proceed to Step 3.
2. To install your DPV database from DVD, place the Database DVD into your DVD drive.
3. From the CODE-1 Plus program group (from Start/Programs), double click on the Database
Load icon found in the CODE-1 Plus program group window. This will launch the Database Load
process.
4. Select “DPV Flat,” “DPV Full,” or “DPV Split,” whichever is appropriate, from the choices
indicated by radio buttons on the Database Load Utility dialog box or select the Browse button to
locate your file(s) if necessary. Select the Next button.
The database load process will inspect your system and place the DPV files into your designated
%G1DB% directory. If you have other Pitney Bowes products and have a G1DB variable already
defined, CODE-1 Plus will use this value for the destination location of the database files.
5. If the load completed without errors, you may proceed and run your CODE-1 Plus jobs. If there
were errors, please contact Technical Support.
Release 4.1.0
140
User’s Guide - Open Systems
Chapter 7: Using Delivery Point Validation
Using the Delivery Point Validation Database
Unix
Perform the following steps to install your DPV database from the DVD.

Our DVDs are formatted as UDF with Rockridge extension.
1. To install your DPV database from internet download, follow these steps.
a.
b.
c.
d.
e.
f.
Log in to the Technical Support website at http://www.g1.com/support.
Click My Products.
Click the product link to access the appropriate databases to install.
Click View Available Downloads for your platform.
Click Databases and download the database file(s) for your product.
Proceed to Step 3.
2. To install your DPV database from DVD, follow these steps.
a. Place the DVD in the drive and close the drive door. If your system auto-mounts, go to Step 4
now.
b. Issue the appropriate mount command to indicate that the DVD device is a file system:
mount
/dev/xxx
...where xxx is the DVD device name.
c. If necessary, you must issue the /etc/filesystem command to update your system so
that it recognizes this file system. Specify the correct device name for the DVD device on
your system.

Your system must allow DVDs created under the ISO 9660 format to be mounted as a
file system.
d. Proceed to Step 3.
3. Issue the appropriate source command to setup the environment:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)
4. Execute the script for installing the database by typing the following command:
$G1DIR/g1bin/installdb
or
cd to $G1DIR/g1bin and type installdb
5. Select CODE-1 Plus from the menu options, and a sub-menu will appear listing your file install
options.
6. At the prompt on the bottom of the screen, select the Delivery Point Validation file you want to
install; Split, Flat, or Full.
7. When the DPV file is installed, continue to follow the steps to verify the product installation.
Verify the Unix Installation Procedures
Once you have installed the software and databases, you should run the verification procedures to
ensure that everything works properly.
1. Issue the appropriate source command to set up the environment:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)
Release 4.1.0
141
User’s Guide - Open Systems
Using the Delivery Point Validation Database
You must issue this command every time you establish a new environment by either logging in or
exiting the shell in which the source command was issued. Normally you will do this as soon as
you have logged on so all subshells you create will have the product environment variables
defined. Pitney Bowes strongly recommends that you add the source command to your .profile
or .cshrc file, but this is optional.
If you installed the ready-to-run version of this product, you can proceed to the next step for DPV
processing. If you are using a compiler to build CODE-1 Plus programs, please follow these
steps to build your DPV-aware programs and runtime system:
2. Change directory (cd) to the $G1C1P/bin subdirectory.
3. Source the setup script:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)
4. Run the DPV build script, dpvbuild.
The dpvbuild script creates a dpvrts for your system. This executable will be located in
$G1C1P/pgms.

You MUST have an ANSI C compiler to build the DPV runtime system. Also, your
environment MUST include the path to the C compiler on your PATH and
LD_LIBRARY_PATH (SHLIB_PATH or LIBPATH). If either of these requirements are not
met, the dpvrts cannot be built, and you may experience errors during this build
process.
After the dpvrts runtime environment is built, proceed to the next step in DPV processing.
z/OS/IMS
To install the DPV database in an z/OS or IMS environment:
1. Locate DASD space to accommodate the DPV Database.
2. If installing from media or the Internet locate the following members in your INSTALL library/
sublibrary.
Member
Database
DPFALOCF.JCM
DPFDBIND.JCM
DPFDBINS.JCM
Flat DPV Database
DPHALOCF.JCM
DPHDBIND.JCM
DPHDBINS.JCM
Full DPV Database
DPVALOCF.JCM
DPVDBIND.JCM
DPVDBINS.JCM
Split DPV Database
3. Edit the appropriate member(s) based on your type of installation following the directions
outlined in the JCL member(s).
4. To create the database, submit the appropriate JCL member(s) for execution. Check the output
of the job(s) to ensure that all steps end with the return codes documented.
Release 4.1.0
142
User’s Guide - Open Systems
Chapter 7: Using Delivery Point Validation
Activating Delivery Point Validation
Activating Delivery Point Validation
Activating DPV in Batch Mode
To activate DPV in batch mode, you must define:
•
•
•
DPVIN parameter
DPVOUT parameter
Five MAILER parameters

To process DPV on mainframe, the JCL must have DD statements for the DPV DB you
intend to use. CODE-1 Plus customers should be aware that batch jobs running with DPV
Split, LACSLink, and SuiteLink may require up to 377M of GETVIS.
DPVIN Parameter
The DPVIN parameter activates DPV processing and provides processing options based on
matches to the ZIP + 4 database. For more information on the DPVIN parameter, please refer to
“DPVIN” in your CODE-1 Plus Reference Guide.
DPVOUT Parameter
Use the DPVOUT parameter to define your DPV processing output requirements. For more
information on the DPVOUT parameter, please refer to “DPVOUT” in your CODE-1 Plus Reference
Guide.
Activating DPV in Callable Mode
To use DPV when calling C1MATCHx from your own driver, pass an X to the P9IDPV field in the
P9IN call area.
Understanding DPV Return Information
Use the DPVOUT parameter to define the options and location in the output record for the following
Delivery Point Validation processing return information:
•
•
•
•
•
•
•
•
Return Codes
Footnote Codes
CMRA Flags
False/Positive Flag
Footnote Codes
No Stat Flag
Vacant Table Flag
PBSA Flag
For more information on the DPVOUT parameter, please refer to “DPVOUT” in your CODE-1 Plus
Reference Guide.
Release 4.1.0
143
User’s Guide - Open Systems
DPV Reports
DPV Reports
This section describes the reports generated by DPV processing.
DPV by List Code Report
The DPV by List Code Report shows you the results of your DPV processing by list code. This report
prints automatically when your job is run, unless you have an N in column 40 of the REPORT
parameter. If you need to call Technical Support, please have this report available. This report
includes the following information:
•
•
•
•
•
•
•
•
•
•
•
All of the list codes used in DPV processing
Total number of records presented for DPV processing
Total number of DPV validated records
Total number of streets DPV validated
Total number of high rises DPV validated
Total number of PO Boxes DPV validated
Total number of Rural Routes/Highway Contractors DPV validated
Total number of Firms DPV validated
Total number of General Delivery DPV validated
Total number of primary number errors
Total number of secondary number errors
DPV Processing Summary Report
The DPV Processing Summary Report prints automatically when your job is run, unless you have an
N in column 38 of the REPORT parameter. If you need to call Technical Support, please have this
report available. This report includes the following information:
•
•
•
•
•
•
•
•
•
•
•
•
•
Delivery Point Validation attempts with percentages
Multiple attempts confirmed
Unique/Small Town Default ZIP + 4 confirmed
Number of ZIP+4 coded records
Street records validated
High Rise records validated
PO Box records validated
Rural Route/Highway Contract records validated
Firm records validated
Primary Number errors
Secondary Number errors
False Positives
Total Residential/Business (RDI) attempts

Release 4.1.0
A zero in the false-positive (seed violation) section indicates that you did not hit any seed
records during your DPV processing. A one indicates that you hit a seed record, which halted
your DPV processing.
144
User’s Guide - Open Systems
Chapter 7: Using Delivery Point Validation
DPV Error Messages
DPV Error Messages
This section describes the error messages you may receive during DPV processing.

Although DPV processing may cease during an execution of CODE-1 Plus, processing will
continue to end-of-file. Any DPV errors you encounter will NOT affect your CODE-1 Plus
processing.
Expiration of DPV Processing
The DPV option stops working the fourth month from the release of the database.
If you have an expired DPV database, this message displays:
****************************************************************************
*DELIVERY POINT VALIDATION SUPPRESSED DUE TO DATABASE EXPIRATION DATE CHECK*
****************************************************************************
Another example is:
****************************************************************************
*Database error on DHFDPV -> EXPIRED
*
****************************************************************************
Open/Read Failure
If you have an open/read failure on the DPV database, this message displays:
****************************************************************************
*OPEN/READ FAILURE ON DPV DATABASE
*
****************************************************************************
Seed Records and Stop DPV Processing
Seed records are artificially manufactured addresses provided as part of the DPV option. There are
approximately 5 million seed records residing in a false-positive (seed violation) table to prevent list
creation. For each negative response that occurs during DPV processing, a query must be made to
the false-positive (seed violation) table. A match to this table stops DPV processing with the
following error message:
****************************************************************************************
*DPV PROCESSING WAS TERMINATED DUE TO THE DETECTION OF WHAT IS DETERMINED
*
*TO BE AN ARTIFICIALLY CREATED ADDRESS. NO ADDRESS BEYOND THIS POINT HAS
*
*BEEN DPV VALIDATED. IN ACCORDANCE WITH THE LICENSE AGREEMENT BETWEEN USPS
*
*AND PITNEY BOWES, DPV SHALL BE USED TO VALIDATE LEGITIMATELY OBTAINED
*
*ADDRESSES ONLY, AND SHALL NOT BE USED FOR THE PURPOSE OF ARTIFICIALLY
*
*CREATING ADDRESS LISTS. THE WRITTEN AGREEMENT BETWEEN PITNEY BOWES AND
*
*ANY CUSTOMER OF PITNEY BOWES SHALL ALSO INCLUDE THIS SAME RESTRICTION
*
*AGAINST USING DPV TO ARTIFICIALLY CREATE ADDRESS LISTS. CONTINUING USE OF
*
*DPV REQUIRES COMPLIANCE WITH ALL TERMS OF THE LICENSE AGREEMENT. IF YOU
*
*BELIEVE THIS ADDRESS WAS IDENTIFIED IN ERROR, PLEASE CONTACT PITNEY BOWES.
*
*DPV LICENSE UPDATE URL:HTTP://WWW.G1.COM/SUPPORT/LICENSE/DPV.ASP THE FOLLOWING
*
*CODE IS NEEDED WHEN ACCESSING THE ABOVE-NOTED PITNEY BOWES WEBSITE TO OBTAIN YOUR NEW *
*DPV LICENSE KEY.S9999999999999999
*
****************************************************************************************

Release 4.1.0
To continue DPV processing, you must provide the Seed Code listed in the error message to
the Pitney Bowes website. When you provide this Seed Code you will receive another
permanent License Management key which will allow you to continue your DPV processing.
145
User’s Guide - Open Systems
What If My Mailing Generates a Seed Violation?
Software Incompatibility
If your software is not compatible with ZIP+4 database (or masterfile), this error message displays:
************************************************************************
*DPV MASTER FILE IS NOT COMPATIBLE WITH THE DPV SOFTWARE. DPV DISABLED.*
************************************************************************
DPV File Load or Location Definition
If your DPV database has not been loaded or the location definition for the DPV database has been
improperly defined, this type of error message displays:
*************************************************************************************
*SPLIT DPV ERROR# 00005, ON FUNCTION: INIT, ERROR DESC: Problem opening dph.hsc file
--------|
|
|
Error number
DPV Data Base Type
*************************************************************************************
What If My Mailing Generates a Seed Violation?
Seed records are artificially manufactured addresses provided as part of the DPV option. There are
a number of seed records residing in a false-positive (seed violation) table to prevent list creation.
For each negative response that occurs in a DPV query, a query must be made to the false-positive
(seed violation) table. A match to this table will stop DPV processing, but CODE-1 Plus processing
will continue to the end of your job.
DPV Seed Record Reporting
If you encounter a DPV seed, you must:
•
•
Report the seed record match to Pitney Bowes Technical Support.
Get a new DPV key from Pitney Bowes Technical Support to turn DPV processing back on.
Reporting a Seed Record Match
If you get a match to the false-positive (seed violation) table, you have matched a seed record, and
you are required to report it to Pitney Bowes per your DPV license agreement. Pitney Bowes is then
required to report it to the USPS. Seed record matches are identified by individual codes, which you
provide to Pitney Bowes when you report a seed match. The seed code can be found in your
execution log, as well as in the DPV Processing Summary report. Your execution log might say, for
example:
THE FOLLOWING CODE IS NEEDED WHEN ACCESSING THE ABOVE-NOTED
PITNEY BOWES WEBSITE TO OBTAIN YOUR NEW DPV LICENSE KEY.
S0000000000000000
The alphanumeric in bold above is the code you need to report to Pitney Bowes.
Release 4.1.0
146
User’s Guide - Open Systems
Chapter 7: Using Delivery Point Validation
What If My Mailing Generates a Seed Violation?
As of the September 2004 CASS Cycle, all customers using DPV must keep information and
statistics on the use of the DPV data and report on this data upon encountering a false-positive
(seed violation) seed record. The following information must be maintained:
•
•
•
•
•
•
•
Mailer’s Company Name
Mailer’s Address
Mailer’s City Name
Mailer’s State Name
Mailer’s ZIP Code
Total Records Processed
Total Records DPV Matched
Batch
CODE-1 Plus Batch DPV customers must use the MAILER parameter records in each batch
(C1BM00) job to indicate the mailer’s Company Name, Address, City Name, State Name, and ZIP
Code. Total Records Processed, Total Records DPV Matched, and other statistical information will
be maintained and reported to the DPVSEED file.
The DPVSEED — DSF False-Positive File contains all of the necessary information for reporting a
false-positive (seed violation) record. The layout of the header and detail records of that file are
shown in Tables 6-1 and 6-2. The header record contains the mailer’s information from the MAILER
Parameter Record and statistics gathered by CODE-1 Plus. The detail record contains DPV falsepositive (seed violation) record information.
DPVSEED Header Record
Position
Release 4.1.0
Length
Description
Format
1-40
40
Mailer’s company name
alphanumeric
41-98
58
Mailer’s address line
alphanumeric
99-126
28
Mailer’s city name
alphanumeric
127-128
2
Mailer’s state abbreviation
alphabetical
129-137
9
Mailer’s 9-digit ZIP code
numeric
138-146
9
Total records processed
numeric
147-155
9
Total records DPV matched
numeric
156-164
9
% match rate to DSF
numeric
165-173
9
% match rate to ZIP+4
numeric
174-178
5
Number of ZIP codes on file
numeric
179-180
2
Number of false positives
numeric
147
User’s Guide - Open Systems
What If My Mailing Generates a Seed Violation?
DPVSEED Detail Record
Position
Length
Description
Format
1-2
2
Street pre-directional
alphanumeric
3-30
28
Street name
alphanumeric
31-34
4
Street suffix abbreviation
alphanumeric
35-36
2
Street post-directional
alphanumeric
37-46
10
Address primary number
alphanumeric
47-50
4
Address secondary abbreviation
alphanumeric
51-58
8
Address secondary number
numeric
59-63
5
Matched ZIP code
numeric
64-67
4
Matched ZIP+4
numeric
68-180
113
Filler
Interactive
CODE-1 Plus Interactive DPV customers who use the CODE-1 Plus Interactive screens must run
the G1CPDPS job to create the required DPVSEED file after a DPV Seed Record is encountered.
CODE-1 Plus will automatically log the information needed to create the DPVSEED file if a DPV
Seed Record is encountered while invoking DPV from the CODE-1 Plus Interactive screens. This
information will be stored in the Customization File. Users must then run the batch job G1CPDPS in
order to extract the seed information from the Customization File and create the DPVSEED file. The
Interactive Screens will prompt the user when a DPV Seed Record has been encountered. Because
the Interactive Screens do not have the ability to record the mailer name and address data, the user
will need to manually insert this information into the DPVSEED file header record after the file has
been created. Please refer to the CODE-1 Plus batch section for detailed information on the
DPVSEED header record.
Callable
CODE-1 Plus Callable DPV customers who call CODE-1 Plus from their own application must
capture the information above in their application interfacing with the API and write this information
to a file.
DPV customers who call CODE-1 Plus from their own application must record certain information to
report to the USPS when a seed record is encountered; this information must be tracked within the
customer’s calling application. This information includes the house number, street name, and ZIP
Code, among others. Table 3 indicates which fields on the P9OUT call area need to be used in order
to properly create the Detail Record of the DPVSEED file.
In order to determine if a DPV Seed Record has been encountered, customers should examine the
field P9ODPVF (P9OUT position 46). If the value in this field is a ‘Y’, a DPV Seed Record has been
encountered and the DPVSEED file will be generated.
Release 4.1.0
148
User’s Guide - Open Systems
Chapter 7: Using Delivery Point Validation
What If My Mailing Generates a Seed Violation?
DPVSEED/P9OUT Map
DPVSEED
DPVSEED
P9OUT
P9OUT
Position
Description
Position
Field Name
1-2
Street pre-directional
813-814
P9ODI1
3-30
Street name
815-842
P9OSTR
31-34
Street suffix abbreviation
843-846
P9OSFX
35-36
Street post-directional
847-848
P9OD12
37-46
Address primary number
803-812
P9OHS-LB
47-50
Address secondary abbreviation
938-941
P9OATP
51-58
Address secondary number
942-949
P9OAP-LB
59-63
Matched ZIP code
1720-1724
P9OCZP
64-67
Matched ZIP+4
29-32
P9ODPBC
68-180
Filler
N/A
N/A
DPV Seed Record Reporting
If you encounter a DPV seed, you must report it to the USPS. Follow these steps to report seed
violations to the USPS and obtain a reactivation license key.
1. Login to the Pitney Bowes Support site at http://www.g1.com/support.
2. Select “DPV and LACSLink False-Positive”.
3. The DPV™ and LACSLink™ False-Positive (Seed Violation) Recovery screen displays.
4. Scroll down to your processing platform. Under your processing platform, click the “Get Delivery
Point Validation Database” link.
5. The Get DPV License/Report Seed Violation screen displays.
6. Click “Seed Violation Restart”.
7. Under Seed/Contact Information:
a. Use Browse to locate and attach your DPV Seed File.
b. Enter your email address.
8. Contact Pitney Bowes Technical Support to receive a new license file. For example:
G1LicensePBDPV.txt
9. Open the file provided by Pitney Bowes Technical Support to retrieve your new DPV key.
10. Replace your existing DPV key with the new DPV key provided in the license file. In some cases,
there may be more than one key in the downloaded license file. All keys in the downloaded
license file are functionally identical. You only need to enter one key. Do not enter more than one
key.
Release 4.1.0
149
User’s Guide - Open Systems
What If My Mailing Generates a Seed Violation?
Release 4.1.0
150
User’s Guide - Open Systems
Link
Using LACS
In this chapter:




What is LACSLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Using the LACSLink Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
How Do I Install the LACSLink Option? . . . . . . . . . . . . . . . . . . . .153
How Do I Activate LACSLink?. . . . . . . . . . . . . . . . . . . . . . . . . . . .156



Understanding LACSLink Return Information . . . . . . . . . . . . . . .160
LACSLink Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
What If My Mailing Generates a Seed Violation? . . . . . . . . . . . .161
8
What is LACSLink?
What is LACSLink?
You can use LACSLink to implement the USPS Locatable Address Conversion System (LACS)
service. LACS is used to provide computerized address list correction for addresses in areas
affected by rural route and box numbers to city-style address conversion, and city-style to city-style
address conversions.
LACS provides mailers an automated method of obtaining new addresses when a 911 emergency
system has been implemented. The 911 address conversions normally involve changing rural-style
addresses to city-style addresses. In some instances, conversions may result in the renaming or
renumbering of existing city-style addresses.

USPS regulations require LACSLink processing for CASS certification.
What are the Benefits of LACSLink?
LACSLink provides the following benefits:
•
•
•
•
•
•
Complies with USPS CASS regulations. LACSLink processing is a USPS CASS requirement.
Prepares you for future USPS CASS regulations. In future CASS cycles, the USPS may expand
LACSLink processing requirements.
Reduces undeliverable mail by providing the most current address information for matches
made to the LACS file.
Prevents the need for duplicate mailpieces or re-mailings after address corrections are received
since the address correction is applied prior to the mailing.
Lowers your costs by reducing the number of undeliverable and/or duplicate mailpieces by using
the most current address information.
Provides the opportunity for faster marketing through accurate mail delivery.
Who is Eligible to Use LACSLink?
All CODE-1 Plus customers operating in the United States are eligible to use LACSLink.

The USPS has specific export rules that regulate the distribution of postal databases. At this
time, DPV, LACSLink, and SuiteLink databases are not available to customers operating
outside of the United States. For more information on the USPS rules, go to http://
ribbs.usps.gov.
How Does LACSLink Work?
The following steps describe the sequence of CODE-1 Plus LACSLink processing:
1. Standardizes input address information to conform with USPS requirements including the
ZIP + 4 Code.
2. Matches the address against the LACS file.
Release 4.1.0
152
User’s Guide - Open Systems
Chapter 8: Using LACSLink
Using the LACSLink Option
3. If an exact match is made with the old address information on the LACS file, processing updates
the address.
4. If a match is found, CODE-1 Plus returns the following information:
•
•
•
•
Original input address from the mailer
Input address as standardized and appended with the ZIP + 4 Code (if possible)
Standardized new address when the standardized input address matches the old address on
the LACS file
National Delivery Index (NDI) report that includes a breakdown of deliverable address
information
5. If no match is found, CODE-1 Plus returns the following information:
•
•
•
•
Original input address
Standardized ZIP + 4 coded version of the input address
USPS Form 3553
NDI report
Using the LACSLink Option
This section provides information on how to perform LACSLink processing.
LACSLink Processing Requirements
LACSLink processing requires a LACSLink security file. There are two versions of this file for z/OS:
•
A flat file for batch processing. This file is created during the base/initial installation, using
XXL.SU$ as input. In the mainframe the DD name is:
//LLKSUD
•
DD
DSN=yourhlq.LACSSUD,DISP=SHR
A VSAM file for CICS processing. The VSAM file, lacssud.80E, is an 80-byte file that is
packaged with JCL (LLSUDLOD) that creates the VSAM version of the LACSLink security file.
Revised C1PCSD JCL is also included to define the security file LLKSUD in CICS.
DEFINE FILE (LACSSUD)
BROWSE (YES)
DISPOSITION (SHARE)
DESCRIPTION (LACS LINK - LACSSUD)
DSNAME (yourhlq.LACSSUD)
RECORDFORMAT (F)
RECORDSIZE (80)
LSRPOOLID (NONE)
UPDATE (YES)
GROUP (G1CPRDO)
How Do I Install the LACSLink Option?
The LACSLink Option is installed as part of your standard CODE-1 Plus installation. The distribution
media sent to you in your release package contains all data needed to perform LACSLink processing
(e.g., the security key and the security file). After installing CODE-1 Plus, you must activate the
LACSLink Option to perform LACSLink processing.
Release 4.1.0
153
User’s Guide - Open Systems
How Do I Install the LACSLink Option?
How Do I Install the LACS Database?
In this section, we provide platform-specific instructions for installing your LACSLink database. The
LACSLink data must be kept in synch with the USPS ZIP + 4 data. Please note that the LACSLink
database has a 120-day expiration cycle. Databases expire on the following schedule.
LACSLink Database Expiry Cycle
Database Month
Expiration
January
April 30
February
May 31
March
June 30
April
July 31
May
August 31
June
September 30
July
October 31
August
November 30
September
December 31
October
January 31
November
February 28
December
March 31
Windows
After product installation and the appropriate variables have been defined, you are ready to load the
database files. You must have a downloaded LACSLink database from our website or a LACSLink
Database DVD (only available from the Pitney Bowes eStore for an additional cost). Follow these
steps to load the LACSLink Database:

For files downloaded from our web site, to expedite the installation of Link product databases
Pitney Bowes recommends you unzip each product – Split DPV, Full DPV, Flat DPV,
LACSLink and SuiteLink files – into separate subfolders before loading the files into the DB
folder. Otherwise, all products will be loaded simultaneously which may delay product
database installation.
1. To install your LACSLink database from internet download, follow these steps.
a.
b.
c.
d.
e.
f.
Release 4.1.0
Log in to the Technical Support website at http://www.g1.com/support.
Click My Products.
Click the product link to access the appropriate databases to install.
Click View Available Downloads for your platform.
Click Databases and download the database file(s) for your product.
Proceed to Step 3.
154
User’s Guide - Open Systems
Chapter 8: Using LACSLink
How Do I Install the LACSLink Option?
2. To install your LACSLink database from DVD, place the Database DVD into your DVD drive.
3. From the CODE-1 Plus program group (from Start/Programs), double click on the Database
Load icon found in the CODE-1 Plus program group window. This will launch the Database Load
process.
4. Select the LACSLink radio button on the Database Load Utility dialog box or select the Browse
button to locate your file(s) if necessary (for files downloaded from our website, point to the
location of the unzipped LACSLink file you downloaded). Select the Next button.
The database load process will inspect your system and place the LACSLink files into your
designated %G1DB% directory. If you have other Pitney Bowes products and have a G1DB
variable already defined, CODE-1 Plus uses this value for the destination location of the
database files.
5. If the load completed without errors, you may proceed and run your CODE-1 Plus jobs. If you
encountered errors, please contact Technical Support.
Unix
1. To install your LACSLink database from internet download, follow these steps.
a.
b.
c.
d.
e.
f.
Log in to the Technical Support website at http://www.g1.com/support.
Click My Products.
Click the product link to access the appropriate databases to install.
Click View Available Downloads for your platform.
Click Databases and download the database file(s) for your product.
Proceed to Step 3.
2. To install your LACSLink database from DVD, follow these steps.
a. Place the DVD in the drive and close the drive door. If your system auto-mounts, go to Step 4
now.
b. Issue the appropriate mount command to indicate that the DVD device is a file system:
mount
/dev/xxx
...where xxx is the DVD device name.
c. If necessary, you must issue the /etc/filesystem command to update your system so
that it recognizes this file system. Specify the correct device name for the DVD device on
your system.
d. Proceed to Step 3.
3. Issue the appropriate source command to setup the environment:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)
4. Execute the script for installing the database by typing the following command:
$G1DIR/g1bin/installdb
or
cd to $G1DIR/g1bin and type installdb
5. Select CODE-1 Plus from the menu options, and a sub-menu will appear listing your file install
options.
6. At the prompt on the bottom of the screen, select LACSLink database as the file you wish to
install. When the LACSLink file is installed you are ready to process records using the LACSLink
option.
Release 4.1.0
155
User’s Guide - Open Systems
How Do I Activate LACSLink?
z/OS/IMS
To install the LACSLink database on z/OS or IMS, follow these steps:
1. Locate DASD space to accommodate the LACSLink database.
2. If installing from media locate the LLDBINS member in your INSTALL library/sublibrary. If
installing from the Internet, locate the LLALOCF and LLDBIND members in your INSTALL
library/sublibrary.
3. Edit the appropriate member(s) according to the instructions located within the member(s).
4. To create the database, submit the appropriate JCL member(s) for execution. Check the output
of the job(s) to ensure that all steps end with the return codes documented.


Please refer to the IVPFILE JCL in the Installation Library on the product tape for examples
of what DD names are required.
Beginning with the CODE-1 Plus 3.7.0 release, IMS batch processing JCL with LACSLink
option invoked now requires LLKSUD and LACSKEY DD statements similar to the ones
provided in IVPFILE.
How Do I Activate LACSLink?
To activate LACSLink processing, follow the steps for your environment.

Batch jobs running with DPV Split, LACSLink, and SuiteLink may require up to 377M of
GETVIS.
Activating LACSLink in Batch Mode
To activate LACSLink using batch processing, create the LACS parameter record as shown below.
Fields on the LACS Parameter (Part 1 of 2)
Position
Field Name
Description
Comments
1-4
KEYWORD
LACS is the only acceptable entry.
Required.
8
LACSLink Processing
Type
The type of LACSLink processing to be performed:
• Z — Perform the ZIP+4 processing prior to
LACSLink.
Required.
Default is
blank.
Release 4.1.0
156
User’s Guide - Open Systems
Chapter 8: Using LACSLink
How Do I Activate LACSLink?
Fields on the LACS Parameter (Part 2 of 2)
Position
10
Field Name
TERMINATE LACS
Description
Comments
This option allows LACSLink to stop batch jobs
when a false-positive (seed record) has been
encountered:
• S — Shuts down CODE-1 Plus processing
when a false-positive (seed record) is
encountered.
Optional.
Default is W.
• W — Allows CODE-1Plus to continue
processing to completion of the entire job,
generating form 3553.
NOTE: CODE-1 Plus will output to the execution
log the seed record information necessary to
reactivate the LACSLink license.
12
LACSLink Limited
This option allows LACSLink to return output
Standardized Address Field, City Field, and State
Field instead of the LACS Converted Address
information:
• L — Invoke limited LACSLink subsystem
processing. Provides the CODE-1 Plus nonLACS converted street address, city, and state
data to the output standardized address and
parsed elements fields.
Optional.
Default is R.
• R — Invoke full LACSLink subsystem
processing. Provides all LACS converted
address information to the output standardized
address and parsed element fields.
NOTE: Per CASS Regulations, the output ZIP,
ZIP+4 Code, and the Delivery Point Barcode must
be maintained for the LACS Converted Address.
14
LACSLink Seed
Processing
• Y — Do not produce “99” return code for LACS
seed record processing.
• N — LACS seed record processing results in
“99” return code.
16
LACSLink Memory
Module Size Indicator
This option allows you to specify size of LACSLink
module.
• Blank — LACS process will be using Medium
memory model (default).
Required.
• P — Pico memory model (no files in memory).
• U — Micro memory model (no files in memory,
only indexes).
• S — Small memory model (Rv9 expansion in
memory).
• M — Medium memory model.
• L — Large memory model.
• H — Huge memory model (all files in memory).

Release 4.1.0
Positions 52-54 and 56-58 of the AM2OUT parameter record store LACSLink processing
return codes.
157
User’s Guide - Open Systems
How Do I Activate LACSLink?
Activating LACSLink in Interactive Mode
To active LACSLink processing, be sure the LACS database is allocated to the region and enter
“LACS” in the command line.
Activating LACSLink in Callable Mode
To use LACSLink when calling C1MATCHI from your own driver, one of three conditions must be
returned from C1MATCHI:
•
•
•
The matched P9O output address has a LACS indicator from the database (P9OLACS)
The P9O General Return Code is not set to blank, B, or X in the output area (P9OGRC)
The P9O default record indicator and the USPS record type are returning a value of “R” in the
output area (P9ODFR and P9ORTP).
Additionally, you must link to LACSLink using the following COBOL statement:
EXEC CICS LINK
PROGRAM (WS-G1CPDLA)
COMMAREA (WS-LACS-AREA)
LENGTH
(LENGTH OF WS-LACS-AREA)
END-EXEC
<-- "G1CPDLA"
<-- See LACCOMM
If you get a match back from LACSLink, you need to re-invoke the matcher with the new data.


The CICS interactive matcher, C1MATCHI, does not directly call LACSLink due to memory
constraints. Instead, C1MATCHI returns information to the interactive driver and initiates a
new transaction to do the LACSLink lookup. However, an issue occurs when there is a "stack"
of addresses to process as a result of a multiple match. In that case, the LACS indicator is
not passed on with these addresses. In this instance, where LACSLink might provide a
different address, that address is not provided.
You can find the P9COMM copybook (a combination of P9IN, P9OUT, and P9AUDIT for use
with CICS) with other copybooks delivered from Pitney Bowes.
The following table describes the P9IN input call area for LACSLink. To activate LACSLink in callable
mode, call the CODE-1 Plus matcher and set the LACSLink indicator as shown below.
The P9IN Input Call Area for LACSLInk
Position
40
Name
P9I-ZLACS
Length
1
Contents
This field allows you to specify if you want to perform LACSLink
processing.
• Blank — Do not attempt to perform LACSLink processing
(default).
• Y — Perform LACSLink processing.
• L — Invoke limited LACSLink subsystem processing.
Provides the CODE-1 Plus non-LACS converted street
address, city, and state data to the output standardized
address and parsed elements fields.
Release 4.1.0
158
User’s Guide - Open Systems
Chapter 8: Using LACSLink
How Do I Activate LACSLink?
The following table describes the LACSLink fields in the P9OUT call area structure.
The P9OUT Output Call Area
Position
1215
Field Name
P9OLACSLINK-IND
Length
1
Comments
Indicates if a table was matched:
• Blank — No LACS processing occurred.
• F — LACS seed violation has occurred.
• N — No match occurred or a new address would not
convert at run time.
• S — Input address contained both primary and
secondary information but match occurred using
only primary information.
• Y — Full match occurred.
1216-1217
P9OLACSLINK-RC
2
Indicates the success of the LACSLink process:
• Blank — No LACS processing occurred.
• A — LACS record match.
• 00 — No match.
• 0 — Address was passed to LACS process, but
could not be coded by LACS.
• 1 — Address was successfully coded through the
LACS process.
• 2 — A LACS False/Positive record was
encountered, but software is operating in a NCOA/
No Stop Capacity. As such, NCOA/No Stop
Capacity allows for the LACS function to continue
processing when a seed record is encountered.
• 09 — LACSLink was able to find the input address on
its internal tables but for some reason did not return
the new (converted) address.
• 14 — Match found LACS record but would not
convert.
• 92 — Match with secondary information.
1218-1226
P9OLACSLINK-DBINFO
9
Indicates the date of the database in YYYYMM format.
Also contains error codes for LACSLink. If the value of
P9OERR is “K” then the first five bytes of this field
contain the error code.
20120: LACS DB EXPIRATION
20121: CAN'T OPEN SECURITY FILE
20122: CORRUPTED SECURITY FILE
20123: CHECK DIGIT VIOLATION ON SECURITY
KEY
20124: PREVIOUS SEED VIOLATION, SYSTEM
LOCKED
20126: RESTART KEY OR SECURITY FILE NOT
CORRECT
20127: UNKNOWN
30000: LACS SEED VIOLATION
31000: LACS SYSTEM ERROR
32000: UNKNOWN (as due to missing or corrupted
LACSLink security file or key file)
1227-1239
P9OLACSLINKVERSION
13
Version number of the LACSLink database.
Release 4.1.0
159
User’s Guide - Open Systems
Understanding LACSLink Return Information
Understanding LACSLink Return Information
This section describes the LACSLink generated return information.
LACSLink Processing Codes
The following return codes indicate the success of LACS processing:
LACS Processing Return Codes
Return Code Name
Return Code
Description
LACS_SEED_NCOA
2
Seed, but NCOA
LACS_SUCCESS
1
Successfully coded
LACS_FAIL
0
Failed to code
LACS_ERROR
-1
System error
LACS_SEED_VIOLATION
-2
LACS False/Positive record encountered - LACS
function stopped
LACS_DB_EXPIRED
-3
LACS database expired.
LACS_KEY_ERROR
-4
User defined LACSKEY is invalid.
LACS_ERROR_DATA
-5
Data file read error
LACS_ERROR_HINT
-6
Error in set table
LACS_ERROR_DBASE0
-70
Database open error
LACS_ERROR_DBASE1
-71
Database open error
LACS_ERROR_DBASE2
-72
Database open error
LACS_ERROR_DBASE3
-73
Database open error
LACS_ERROR_DBASE4
-74
Database open error
LACS_ERROR_DBASE5
-75
Database open error
LACS_ERROR_PLAT
-8
Error in platform detection
LACS_ERROR_INFO
-9
Error in LACS information
LACS_ERROR_INIT
-10
Error in LACS initialization
LACS_ERROR_STATS
-11
Error in LACS statistics
LACS_ERROR_SECDE
-12
Error in LACS Secde
LACS_ERROR_SECIN
-13
Error in LACS Sedin
LACS_ERROR_PARSE
-14
Error in LLPARSE
LACS_ERROR_RV9
-15
Error in rv9esd
Release 4.1.0
160
User’s Guide - Open Systems
Chapter 8: Using LACSLink
LACSLink Reports
LACS Processing Return Codes
Return Code Name
Return Code
Description
LACS_ERROR_STMEM
-16
Error getting st. member
LACS_TEST_BREAK
-17
Break for test
LACSLink Return Codes
:
LACS Return Codes
Return Code Name
Return Code
Description
LACSRTN_MATCH
A
LACS record match.
LACSRTN_NOMATCH
00
No match.
LACSRTN_NOCONV
14
Match found LACS record but would not convert.
LACSRTN_UNIT
92
Match with secondary information.
LACSRTN_HRD
09
LACSLink was able to find the input address on its internal
tables but for some reason did not return the new
(converted) address.
LACSLink Reports
This section describes the reports generated by LACSLink processing.
LACSLink Information on USPS Form 3553
The Qualitative Statistical Summary (QSS) section of the USPS Form 3553 (CASS Summary
Report) displays as shown below if you are processing with the LACSLink Option.
: HIGH RISE :HIGH RISE :RURAL RTE :RURAL RTE : LACS/
:
EWS
:SUITELINK :
: DEFAULT : EXACT
: DEFAULT : EXACT
: LACSLINK :
:
:
:___________:__________:__________:__________:__________:__________:__________:
:
2 :
17 :
0 :
0 :
0 :
0 :
0 :
:_____________________________________________________________________________:
PS FORM 3553, August 2011
See DMM Sec 708 for more information
What If My Mailing Generates a Seed Violation?
If your mailing generates a false-positive result during CODE-1 Plus processing, you are required to:
1. Report the seed record match to Pitney Bowes Technical Support.
2. Get a new LACS key from Pitney Bowes Technical Support to turn LACSLink processing back on.
Release 4.1.0
161
User’s Guide - Open Systems
What If My Mailing Generates a Seed Violation?
Batch
1. If you encounter a LACSLink Seed Violation with your CODE-1 Plus batch job, you must enter the
current LACSLink Key and attach the Seed File to be issued a reactivation key.
a. The LACSLink Key can be obtained from your LACSKEY file, which is defined to CODE-1
Plus using the LACSKEY DD statement that exists in the JCL for Mainframe platforms. The
table below details the location LACSKEY file by platform.
Locations of LACS File by Platform
Platform
Location
Required Name
Windows
The directory where your environment variable LACSKEY is
set. The default is %G1C1P%/data.
lacslk
Unix/Linux
The directory where your environment variable LACSKEY is
set. The default is $G1C1P/data.
lacslk
IMS & z/OS
DD Statement within flat file:
//LACSKEY DD DSN=yourhlq.LACSKEY,DISP=SHR
NOTE: Replace “yourhlq” with your own high-level qualifier.
LACSKEY

The LACSLink Key file can be opened with any text editor, and contains only the 16-byte
alpha-numeric LACSLink Key (not including hyphens) used by CODE-1 Plus.
b. The Seed File is defined to CODE-1 Plus using the DPVSEED DD statement that also exists
in the JCL, Job Script or Batch file that is used to submit the batch job.
Interactive
1. If you encounter a LACSLink Seed Violation using the Matcher-Inquiry/G1CP Transaction, you
must enter the current LACSLink Key and attach the Seed File to be issued a reactivation key.
a. The LACSLink Key can be obtained from your LACSKEY file, which is defined to CODE-1
Plus using the LACSKEY DD statement that exists in the JCL for Mainframe platforms.
b. The Seed File contains all of the necessary information for reporting a false-positive record.
You must create this file using any text editor, reporting the following information in the
specified record position:
LACSLink SEED File Detail Record (Part 1 of 2)
Position
Release 4.1.0
Length
Description
Format
1-2
2
Street pre-directional
alphanumeric
3-30
28
Street name
alphanumeric
31-34
4
Street suffix abbreviation
alphanumeric
35-36
2
Street post-directional
alphanumeric
37-46
10
Address primary number
alphanumeric
47-50
4
Address secondary abbreviation
alphanumeric
51-58
8
Address secondary number
numeric
59-63
5
Matched ZIP code
numeric
162
User’s Guide - Open Systems
Chapter 8: Using LACSLink
What If My Mailing Generates a Seed Violation?
LACSLink SEED File Detail Record (Part 2 of 2)
Position
Length
Description
Format
64-67
4
Matched ZIP+4
numeric
68-180
113
Filler
Reserved
Once the key and Seed File have been entered, you can select the Download License button
to acquire your LACSLink reactivation key. To apply your reactivation key, edit your
LACSKEY file and replace the existing key with the reactivation key.

LACSLink does not have a New License option for processing, as the initial license
key is packaged and delivered with the installation of the CODE-1 Plus software
application.
LACSLink Seed Record Reporting
If you encounter a LACSLink seed, you must report it to the USPS. Follow these steps to report seed
violations to the USPS and obtain a reactivation license key.
1. Login to the Pitney Bowes Support site at http://www.g1.com/support.
2. Select “DPV and LACSLink False-Positive”.
3. The DPV™ & LACSLink™ False-Positive (Seed Violation) Recovery screen displays.
4. Scroll down to your processing platform. Under your processing platform, click the “Get LACSLink
Database” link.
5. The Get LACSLink License/Report Seed Violation screen displays.
6. Click the appropriate processing method.
7. Under Seed/Contact Information:
a. Enter your old LACSLink license key
b. Use Browse to locate and attach your Seed File.
c. Enter your email address.
8. Contact Pitney Bowes Technical Support to receive a new license file. For example:
G1LicensePBLL.txt
9. Open the file to retrieve your new key.
10. Replace your existing LACSLink key with the new LACSLink key provided in the license file. In
some cases, there may be more than one key in the downloaded license file. All keys in the
downloaded license file are functionally identical. You only need to enter one key. Do not enter
more than one key.
Release 4.1.0
163
User’s Guide - Open Systems
What If My Mailing Generates a Seed Violation?
Release 4.1.0
164
User’s Guide - Open Systems
Link
Using Suite
In this chapter:







What is SuiteLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
How Does SuiteLink Work?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
How do I Install the SuiteLink Option?. . . . . . . . . . . . . . . . . . . . .167
How Do I Activate SuiteLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
SuiteLink Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Input and Output Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
SuiteLink Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
9
What is SuiteLink?
What is SuiteLink?
According to the USPS, 26% of all mail addressed to high-rise addresses (business and residential)
ZIP+4 Code to a high-rise default code. The purpose of SuiteLink is to improve business addressing
by adding known secondary (suite) numbers to allow delivery sequencing where it would otherwise
not be possible.
The USPS defines SuiteLink as: “a data-only product containing business addressing information
specifically identified as high-rise default records as a result of CASS processing. This product
provided by the USPS allows developers to create a software interface that will have the capability of
appending the secondary (suite) information to a business address, providing the input address is
determined to be a highrise default record.”

SuiteLink cannot be used as part of a standalone process; it must be used in conjunction with
CODE-1 Plus.

The USPS regulations require SuiteLink processing for CASS certification.

The FIRMNM parameter is required when you use the STELNK parameter for SuiteLink®
processing.
What are the Benefits of SuiteLink?
SuiteLink enables customers to provide improved business addressing information by adding known
suite information to business addresses, which will allow USPS delivery sequencing where it would
not otherwise be possible.
The SuiteLink Option provides you with the ability to improve deliverability for the business addresses
in your mailing list. SuiteLink improves business address information by adding accurate secondary
(suite) information to the business addresses in your mailing list. Adding this additional information
makes USPS delivery sequencing available for addresses in your mailing list that previously were
not eligible.
Some of the benefits available to CODE-1 Plus customers through SuiteLink processing are
described below.
•
•
•
Release 4.1.0
Improves the business address information in your mailing list by appending secondary (suite)
information to business addresses.
Ensures USPS delivery sequencing for the business addresses in your mailing list.
SuiteLink processing provides another method to ensure postal coding accuracy resulting in less
undeliverable mail.
166
User’s Guide - Open Systems
Chapter 9: Using SuiteLink
How Does SuiteLink Work?
Who is Eligible to Use SuiteLink?
SuiteLink is available to all CODE-1 Plus customers operating in the United States. Records that
have been processed through CASS-Certified ZIP+4 address-matching software and identified as
high-rise defaults are potential candidates for SuiteLink processing.

The USPS has specific export rules that regulate the distribution of postal databases. At this
time, DPV, LACSLink, and SuiteLink databases are not available to customers operating
outside of the United States. For more information on the USPS rules, go to http://
ribbs.usps.gov.
How Does SuiteLink Work?
CODE-1 Plus performs SuiteLink processing in the situations described below.
1. CODE-1 Plus calls SuiteLink when the following conditions are met:
•
•
SuiteLink has been activated via either batch mode, interactive mode, or callable mode and
all required SuiteLink parameters are defined with valid values
CODE-1 Plus successfully coded the address and the following information exists in the
address record:
– Firm name
– Valid ZIP code
– Valid ZIP+4 code
– Primary number exists
A match has been made to a high-rise default record
The CODE-1 Plus database is current
•
The SuiteLink database is current.
•
•
2. If SuiteLink returns secondary data, CODE-1 Plus performs another match attempt using the
corrected data.
3. CODE-1 Plus prints statistics at end of job.
How do I Install the SuiteLink Option?
The SuiteLink Option is installed as part of your standard CODE-1 Plus installation. The distribution
media sent to you in your release package contains all data needed to perform SuiteLink processing.
After installing CODE-1 Plus and the SuiteLink database, you must activate the SuiteLink Option to
perform SuiteLink processing.
Release 4.1.0
167
User’s Guide - Open Systems
How do I Install the SuiteLink Option?
How do I Install the SuiteLink Database?
In this section, we provide platform-specific instructions for installing your SLKDB database. The
SuiteLink data must be kept in synch with the USPS ZIP + 4 data. Please note that the SLKDB
database has a 120-day expiration cycle. Databases expire on the following schedule.
SuiteLink Database Expiry Cycle
Database Month
Expiration
January
April 30
February
May 31
March
June 30
April
July 31
May
August 31
June
September 30
July
October 31
August
November 30
September
December 31
October
January 31
November
February 28
December
March 31
In addition, for Windows and Unix, there are three additional index files used to support the small
memory model.
Windows
After product installation and the appropriate variables have been defined, you are ready to load the
database files. You must have a downloaded SuiteLink database from our website or a SuiteLink
Database DVD (only available from the Pitney Bowes eStore for an additional cost). Follow these
steps to load the SuiteLink database:

Release 4.1.0
For files downloaded from our web site, to expedite the installation of product databases
Pitney Bowes recommends you unzip each product – Split DPV, Full DPV, Flat DPV,
LACSLink and SuiteLink files – into separate subfolders before loading the files into the DB
folder. Otherwise, all products will be loaded simultaneously which may delay product
database installation.
168
User’s Guide - Open Systems
Chapter 9: Using SuiteLink
How do I Install the SuiteLink Option?
1. To install your SuiteLink database from internet download, follow these steps.
a.
b.
c.
d.
e.
f.
Log in to the Technical Support website at http://www.g1.com/support.
Click My Products.
Click the product link to access the appropriate databases to install.
Click View Available Downloads for your platform.
Click Databases and download the database file(s) for your product.
Proceed to Step 3.
2. To install your SuiteLink database from DVD, place the Database DVD into your DVD drive.
3. From the CODE-1 Plus program group (from Start/Programs), double click on the Database
Load icon found in the CODE-1 Plus program group window. This will launch the Database Load
process.
4. Select the SuiteLink radio button on the Database Load Utility dialog box or select the Browse
button to locate your file(s) if necessary (for files downloaded from our website, point to the
location of the unzipped SuiteLink file you downloaded). Select the Next button.
The database load process will inspect your system and place the SuiteLink files into your
designated %G1DB% directory. If you have other Pitney Bowes products and have a G1DB
variable already defined, CODE-1 Plus uses this value for the destination location of the
database files.
5. If the load completed without errors, you may proceed and run your CODE-1 Plus jobs. If you
encountered errors, please contact Technical Support.
Unix
1. To install your SuiteLink database from internet download, follow these steps.
a.
b.
c.
d.
e.
f.
Log in to the Technical Support website at http://www.g1.com/support.
Click My Products.
Click the product link to access the appropriate databases to install.
Click View Available Downloads for your platform.
Click Databases and download the database file(s) for your product.
Proceed to Step 3.
2. To install your SuiteLink database from DVD, follow these steps.
a. Place the DVD in the drive and close the drive door. If your system auto-mounts, go to Step 4
now.
b. Issue the appropriate mount command to indicate that the DVD device is a file system:
mount
/dev/xxx
...where xxx is the DVD device name.
c. If necessary, you must issue the /etc/filesystem command to update your system so
that it recognizes this file system. Specify the correct device name for the DVD device on
your system.
d. Proceed to Step 3.
3. Issue the appropriate source command to setup the environment:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)
4. Execute the script for installing the database by typing the following command:
$G1DIR/g1bin/installdb
or
cd to $G1DIR/g1bin and type installdb
Release 4.1.0
169
User’s Guide - Open Systems
How Do I Activate SuiteLink?
5. Select CODE-1 Plus from the menu options, and a sub-menu will appear listing your file install
options.
6. At the prompt on the bottom of the screen, select SuiteLink database as the file you wish to
install. When the SuiteLink file is installed you are ready to process records using the SuiteLink
option.
z/OS/IMS
To install the SuiteLink database on z/OS or IMS, follow these steps:
1. Locate DASD space to accommodate the SLKDB database.
2. If installing from media locate the SLKDBINS member in your INSTALL library/sublibrary. If
installing from the Internet, locate the SLKALOCF and SLKDBIND members in your INSTALL
library/sublibrary.
3. Edit the appropriate member(s) according to the instructions located within the member(s).
4. To create the database, submit the appropriate JCL member(s) for execution. Check the output
of the job(s) to ensure that all steps end with the return codes documented.
How Do I Activate SuiteLink?
To activate LACSLink processing, follow the steps for your environment.

Batch jobs running with DPV Split, LACSLink, and SuiteLink may require up to 377M of
GETVIS.
Activating SuiteLink in Batch Mode
To activate SuiteLink in batch mode, create the STELNK parameter record as shown below:
Fields on the STELNK Parameter (Part 1 of 2)
Position
Field Name
Description
Comments
1-6
KEYWORD
STELNK is the only acceptable entry.
Required.
8
SuiteLink Error
Shutdown Indicator
Determine s whether to shut down when
SuiteLink reports an error.
• I — Ignore error and continue to attempt
SuiteLink processing. CODE-1 Plus does
not generate a USPS Form 3553 (USPS
CASS Summary Report) if you specify the
value “I”.
Optional.
• S — Shutdown when SuiteLink reports an
error (default). Specify the value “S” if you
want to generate a USPS Form 3553
(USPS CASS Summary Report).
• W — Issue warning message and turn off
SuiteLink processing. CODE-1 Plus does
not generate a USPS Form 3553 (USPS
CASS Summary Report) if you specify the
value “W”.
Release 4.1.0
170
User’s Guide - Open Systems
Chapter 9: Using SuiteLink
How Do I Activate SuiteLink?
Fields on the STELNK Parameter (Part 2 of 2)
Position
10
Field Name
SuiteLink Memory Model
Flag
Description
Comments
This option allows you to specify size of
SuiteLInk memory module.
• Blank — SuiteLink process will use the
Medium memory model (default.)
Required.
• P — Pico memory model (no files in
memory).
• U — Micro memory model (no files in
memory, only indexes).
• S — Small memory model (slkhdr,
slknormal, slknoise in memory).
• M — Medium memory model (slknine file
also in memory.)
• L — Large memory model (lcd file also in
memory.)
• H — Huge memory model (slk file also in
memory.)
12-14
SuiteLink Return Code
Location
Location for SuiteLink return code:
• A — Business name matched.
Optional.
• 00 — Business name not matched.
16-18
SuiteLink Match Code
Location
Location for SuiteLink match code:
• A — Matched.
Optional.
• B — Not matched.
• C — Business name was all noise.
• D — Highrise default record not found.
• E — Database is expired.
20-22
SuiteLink Fidelity Code
Location
Location for SuiteLink match fidelity:
• 1 — Exact match.
Optional.
• 2 — Acceptable match (one word not
matched).
• 3 — Unacceptable match (more than one
word not matched).
24
Include/Exclude
Secondary
Use this options to call SuiteLink without
appending the secondary information to the
output address line. All other fields, ZIP + 4
value, DPC code, are determined using the
secondary information returned by SuiteLink.
• I — Include secondary information from
SuiteLink on the output address line.
Optional.
• E — Exclude secondary information from
SuiteLink from the output address line.
• blank — Defaults to I.
25
Include/Exclude
Extraneous Input
Secondary Information
Use this option to include or exclude any
invalid (extraneous) input secondary
information.
• I — Include the invalid input secondary
information.
Optional.
• E — Exclude the invalid input secondary
information.
• blanks — Defaults to I.
Release 4.1.0
171
User’s Guide - Open Systems
How Do I Activate SuiteLink?
Activating SuiteLink in Interactive Mode
To activate SuiteLink in Interactive mode, be sure the SuiteLink database is allocated to the region and
enter “SUITE” on the command line.
Activating SuiteLink in Callable Mode
To use SuiteLink when calling C1MATCHI from your own driver, five conditions must be returned from
C1MATCHI:
•
•
•
•
•
There must be a firm name in the P9I input area (P9IFRM) AND
There must be a house number in the P9O output area (P9OHS-LB) AND
The default record indicator must be returning a value of “H” in the P9O output area (P9ODFR)
AND
The USPS record type must be returning a value of “H” in the P9O output area (P9ORTP) AND
There must be spaces in both the P9O General Return Code and the 9-digit Return Code in the
output area (P9OGRC and P9O9RC)
Additionally, you must link to SuiteLink using the following COBOL statement:
EXEC CICS LINK
PROGRAM (WS-G1CPDSU)
COMMAREA (WS-STELNK-AREA)
LENGTH
(LENGTH OF WS-STELNK-AREA)
END-EXEC
<-- "G1CPDSU"
<-- See STECOMM
If you get a match back from SuiteLink, you need to re-invoke the matcher with the new data.
However, do not use the firm name that is returned; just use the secondary information.

You can find the P9COMM copybook (a combination of P9IN, P9OUT, and P9AUDIT for use
with CICS) with other copybooks delivered from Pitney Bowes.
You can also optionally perform the following:
•
•
Release 4.1.0
Determine whether an expired SuiteLink database can cause a job to terminate.
Set the Small Memory Model flag.
172
User’s Guide - Open Systems
Chapter 9: Using SuiteLink
How Do I Activate SuiteLink?
The P9IN Input Call Area for SuiteLink is shown as follows.
The P9IN Input Call Area for SuiteLInk
Position
29
Name
Length
P9ISTE
Contents
Determines whether to shut down when SuiteLink reports an
error.
• I — Ignore error and continue to attempt SuiteLink
processing. CODE-1 Plus does not generate a USPS Form
3553 (USPS CASS Summary Report) if you specify the
value “I”.
1
• S — Shutdown when SuiteLink reports an error (default).
Specify the value “S” if you want to generate a USPS Form
3553 (USPS CASS Summary Report).
• W — Issue warning message and turn off SuiteLink
processing. CODE-1 Plus does not generate a USPS Form
3553 (USPS CASS Summary Report) if you specify the
value “W”.
30
P9ISTE-BYP
This field allows you to specify if an expired SuiteLink database
will cause the job to terminate.
• N — Do not bypass SuiteLink database expiration date
processing (default).
1
• Y — Bypass SuiteLink database expiration processing.
31
P9ISTE-SMM
This field controls the SuiteLink memory module size to use for
processing.
• Blank — DPV process will be using Medium memory model
(default).
1
• P — Pico memory model (no files in memory).
• U — Micro memory model (no files in memory, only
indexes).
• S — Small memory model.
• M — Medium memory model.
• L — Large memory model.
• H — Huge memory model (all files in memory).

See positions 1863-1878 and 2121-2170 of the P9OUT callable area for SuiteLink output.
The output from the SuiteLink job posts as follows in the P9OUT call area:
The P9OUT Output Call Area for SuiteLInk
Position
1863
Name
P9OSTELNK-RC
Length
2
Contents
SuiteLink return code:
• A — Business name matched.
• 00 — Business name not matched.
1864
P9OSTELNKMATCH-RC
1
SuiteLink match code:
• A — Matched.
• B — Not matched.
• C — Business name was all noise.
• D — Highrise default record not found.
• E — Database is expired.
Release 4.1.0
173
User’s Guide - Open Systems
SuiteLink Return Codes
The P9OUT Output Call Area for SuiteLInk
Position
1865
Name
P9OSTELNKMATCH-FID
Length
Contents
SuiteLink match fidelity:
• 1 — Exact match.
1
• 2 — Acceptable match (one word not matched).
• 3 — Unacceptable match (more than one word not
matched).
1866
P9OSTELNK-RLSNUM
12
SuiteLink release number.
DD Name
The DD name for SuiteLink is SLKDB.
SuiteLink Return Codes
The following return codes indicate the success of SuiteLink processing.
SuiteLink Return Codes
Return Code
Description
00
No SuiteLink record match found.
A
SuiteLink record match found.
Input and Output Examples
The following examples show examples of potential input and output with SuiteLink.
Input:
1
2
3
4
5
6
----+----0----+----0----+----0----+----0----+----0----+---2070618524200
PITNEY BOWES
009269786300
RAMALLO BROS PKG
Output:
1
2
3
4
5
6
----+----0----+----0----+----0----+----0----+----0----+---STE 600
A 1PITNEY BOWES
STE 1
A 2BROTHERS PKG RAMALLO
SuiteLink Reporting
The USPS Form 3553 and the Control Reports are include SuiteLink information.
Release 4.1.0
174
User’s Guide - Open Systems
Chapter 9: Using SuiteLink
SuiteLink Reports
SuiteLink Reports
This section describes the reports generated by SuiteLink processing.
USPS Form 3553
SuiteLink information displays in the Qualitative Statistical Summary section of the USPS Form 3553.
Control Reports
The following line items for SuiteLink display on the Control Reports.
SuiteLink Database version: March 2016, Product Version: 0650
Total Number of SuiteLink Match Attempts
xxxxxxxxx
nn.nn%
Total Number of Successful SuiteLink Match Attempts
xxxxxxxxx
nn.nn%
Total Number of Successful SuiteLink Matches with Corrected Suites xxxxxxxxx
Release 4.1.0
175
nn.nn%
User’s Guide - Open Systems
SuiteLink Reports
Release 4.1.0
176
User’s Guide - Open Systems
Using Line of Travel
In this chapter:









What is Line of Travel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
Why Use Line of Travel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
Accessing Line of Travel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
Getting Started with Line of Travel . . . . . . . . . . . . . . . . . . . . . . . .179
Sorting Your LOT Coded Records . . . . . . . . . . . . . . . . . . . . . . . .179
Calling the LTO10 Subroutine . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
Line of Travel Exit Routine (LTO60) . . . . . . . . . . . . . . . . . . . . . . .184
Control Totals Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
Alternate Sequence Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
10
What is Line of Travel?
What is Line of Travel?
Line of Travel (LOT) is a feature that assigns a code to your address records, allowing you to qualify
your Standard letters and flats for USPS Enhanced Carrier Route rates. LOT is also referred to as
eLOT or Enhanced Line Of Travel. If you use Line of Travel, your mailing is eligible for the USPS
non-automation Basic Rate. To qualify for this rate, your mail must be in LOT sequence. Assigning a
LOT Code to your mailings saves you mailing time and money.
The Line of Travel code indicates the order in which delivery will be made within a given ZIP + 4
carrier route and whether delivery will be made in ascending or descending sequence. Line of Travel
appends a four digit number and a sequence code to all name and address records with a ZIP + 4
Code. This LOT code is then used for sortation purposes to simulate walk sequence mailing within
the number range associated with the ZIP + 4 Code. After the ZIP + 4 file is LOT-coded, the file is
then sorted sequentially by 5-byte ZIP Code, 4-byte carrier route, 4-byte LOT number, and a 2- or 1character sequence code.
The LOT-coded record includes:
•
•
•
•
•
•
ZIP + 4 Code
Delivery Point Code (DPC)
Carrier Route
Line of Travel number
Ascending/descending sequence code
Optional sequence codes used for sortation provided by the Line of Travel software

Per USPS regulations, records with missing (blank) or invalid (0000) LOT information are to
be sorted to the end of the CRRT.
Why Use Line of Travel?
Sorting your Standard letters and flats in line-of-travel sequence is the only way to qualify your
mailings for USPS Enhanced Carrier Route rates when your mail does not meet the non-automation
saturation and high-density rate requirements. The saturation and high-density categories require
that your mail be sorted in walk-sequence. Line of Travel simulates walk-sequence, but only for ten
or more pieces per carrier route.
Accessing Line of Travel
The following methods can be used to invoke Line of Travel:
•
•
•
Release 4.1.0
Matcher (C1MATCHB)—Line of Travel information can be returned by setting a switch in the
matcher.
LOTOUT parameter—Line of Travel information can be returned via the CODE-1 Plus batch
driver using the LOTOUT parameter.
Callable subroutine (LTO10)—You can call LTO10 as a subroutine from any program, as long
as you use the parameters defined in this chapter. The LTO10 callable subroutine determines a
4-digit number and a 1-character sequence code for a record. These parameters accept your
input and return a LOT code. Based on your output parameter, LTO10 returns the LOT code to
your executable program.
178
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Getting Started with Line of Travel
•
Exit Routine (LTO60)—The LTO60 exit routine posts Line of Travel information onto your nameand-address record when passed from any Pitney Bowes EXEC- level program. Batch driver
processing requirements are passed via the EXITOP parameter.

CODE-1 Plus does not use LTO60. LTO60 is used from other Pitney Bowes applications.
Getting Started with Line of Travel
Line of Travel derives a Line of Travel (LOT) code, which is comprised of a 4-digit Line of Travel
sequence number and a 1-character Line of Travel sequence code. The Line of Travel sequence
code is either “A” for ascending, or “D” for descending. Line of Travel then appends the LOT code to
all name and address records with a Delivery Point Barcode and a Carrier Route that matches the
Line of Travel Master File.

The option to load or not load the LOT database is provided during the installation process.
The LOT database must be loaded prior to attempting to use LOT processing. Processing
abends and generates the following error message in response to an attempt to access/use
LOT processing without first having loaded the LOT database:
Database error on ELOT for OPEN. FILE STATUS: 35
Sorting Your LOT Coded Records
To use Line of Travel to obtain the maximum discount, the USPS Line of Travel Technical Guide
requires you to sort your LOT-coded records in ascending order in the following sequence:
1. 5-digit ZIP Code
2. 4-byte Carrier Route Code
3. 4-digit Line of Travel Code

This includes only the numeric portion of the LOT code. It does not include the sequence
code.
4. 4-digit ZIP + 4 Code
5. 2-digit Delivery Point Barcode in ascending AND descending order depending on the Line of
Travel sequence code that is appended to each record

The Line of Travel sequence code (either “A” or “D”) is essential for this step.
Since sorting in ascending and descending order can be unwieldy, Line of Travel returns two types
of alternate codes that can be used for sortation. Rather than sorting your output file using the 2-digit
Delivery Point Barcode, you should sort it using either the alternate sequence code or the
hexadecimal sequence code.
Release 4.1.0
179
User’s Guide - Open Systems
Calling the LTO10 Subroutine
The alternate sequence code is a two-byte code used for final sortation in place of the DPC add-on.
It consists of an uppercase letter followed by a digit 0 through 9. Values range from “A0” (99
descending) through “J9” (00 descending), and “K0” (00 ascending) through “T9” (99 ascending).
The hexadecimal sequence code is a single-byte code, and it also allows you to sort your file in
ascending order only. The hexadecimal values range from 0 to FF ascending, then FF through 0
descending.
Both the hexadecimal and alternate sequence codes are determined from the DPC add-on and the
LOT sequence code. For more information on these codes, please refer to "Alternate Sequence
Codes” on page 189.

You must sort your output file as discussed above prior to presorting your mailing when using
the Pitney Bowes MailStream Plus software.
Calling the LTO10 Subroutine
The LTO10 callable subroutine determines a 4-digit sequence number and a 1-character sequence
code for a record. In order to call LTO10, you must pass two parameters:
•
•
Input Parameter — A 50-byte input area containing user-provided data passed from your
executable program to LTO10.
Output Parameter — A 100-byte output area containing information returned from LTO10.
Using the input parameter, you must pass a 5-digit ZIP Code, a 4-digit ZIP+4 Code, a 2-digit DPC,
and a 4-byte Carrier Route as input.
LTO10 then derives a Line of Travel (LOT) code, which is comprised of a 4-digit Line of Travel
sequence number and a 1-character Line of Travel sequence code. Based on your output
parameter, LTO10 returns the LOT code to your executable program.
The Line of Travel sequence code is either “A” for ascending, or “D” for descending. Since sorting in
ascending and descending order can be unwieldy, Line of Travel returns two types of alternate
codes that can be sorted in ascending order only.
The alternate sequence code is a two-byte code used for final sortation in place of the DPC add-on.
It consists of an uppercase letter followed by a digit 0 through 9. Values range from “A0” (99
descending) through “J9” (00 descending), and “K0” (00 ascending) through “T9” (99 ascending).
The hexadecimal sequence code is a single-byte code, and it also allows you to sort your file in
ascending order only. There are 200 values ranging from 99 descending through 00 descending,
then 00 ascending through 99 ascending. Both the hexadecimal and alternate sequence codes are
determined from the DPC add-on and the LOT sequence code. For more information on these
codes, please refer to "Alternate Sequence Codes” on page 189.
Release 4.1.0
180
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Calling the LTO10 Subroutine
Input Area — Parameter 1
The following table maps the positions in input area Parameter 1.
Parameter 1 Input Area Positions
Position
1
Name
FUNCTION TO
PERFORM
Length
1
Description
Enter one of the following codes:
• E — Perform end-of-job functions, for example,
closing the Line of Travel Master File and any
platform-specific functions.
This option will not free memory.
• Other — Perform match to the Master File.
2-10
RESERVED
9
Reserved.
11-15
ZIP CODE
5
Input ZIP Code to be matched against the Line of Travel
Master File.
16-19
ZIP+4 CODE
4
Input ZIP+4 Code to be matched against the Line of
Travel Master File.
20-21
DELIVERY POINT
CODE
2
Input Delivery Point Code (DPC) add-on.
22-25
CARRIER ROUTE
CODE
4
Input Carrier Route Code to be matched against the Line
of Travel Master File.
26-50
RESERVED
25
Reserved.
Release 4.1.0
181
User’s Guide - Open Systems
Calling the LTO10 Subroutine
Output Area — Parameter 2
The following table maps the positions in output area Parameter 2.
Parameter 2 Output Area Positions
Position
1
Name
MATCH LEVEL
Length
1
Description
Indicates the level of match obtained against the Line of
Travel Master File.
• 9 — Match against the Master File was successful.
• C — Call to matcher failed.
• D — Valid input was presented, but no match was
successful with the Master File. Records with valid
input contain numeric, non-zero data in the ZIP and
ZIP+4 Code fields, plus a numeric DPC, and a valid
formatted Carrier Route Code.
• F — Master file open/read failure.
• V — Master file not compatible with Line of Travel
software.
• Blank — Invalid input was presented. Records with
invalid input contain zeroes or non-numeric data in the
ZIP and/or ZIP+4 Code field or non-numeric DPC or
invalid Carrier Route Code.
2-5
LINE OF TRAVEL
(LOT) SEQUENCE
NUMBER
4
Four-digit Line of Travel (LOT) sequence number
generated from the input data defined in Parameter 1.
If valid input was presented, but no match was
successful with the Master File, the record is default
coded, and this field contains zeroes. Please note that
default-coded records are eligible for the basic enhanced
carrier route rate.
If invalid input was presented, this field is blank.
6
LINE OF TRAVEL
(LOT) SEQUENCE
CODE
1
One-character Line of Travel (LOT) sequence code
generated from the input data defined in Parameter 1.
• A — Ascending.
• D — Descending.
• Blank — No LOT number could be determined, due
to invalid input.
NOTE: If valid input was presented, but no match was
successful with the Master File, the record will be
default coded, and this code will be returned.
7-8
ALTERNATE
SEQUENCE CODE
2
Two-character code used for final sortation in place of
the DPC add-on, which allows you to sort your file in
ascending sequence only, instead of both ascending and
descending. This code is determined from the DPC addon field and the LOT sequence code. It consists of an
uppercase letter followed by a digit 0 through 9. Values
range from "A0" (99 descending) through "J9" (00
descending), and "K0" (00 ascending) through "T9" (99
ascending).
9
HEXADECIMAL
SEQUENCE CODE
1
Single-character code used for final sortation in place of
the DPC add-on, which allows you to sort your file in
ascending sequence only, instead of both ascending and
descending. This hexadecimal value is determined from
the DPC add-on field and the LOT sequence code. There
are 200 values ranging from 99 descending through 00
descending, then 00 ascending through 99 ascending.
Release 4.1.0
182
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Calling the LTO10 Subroutine
Parameter 2 Output Area Positions
Position
Name
Length
Description
NOTE: LTO10 returns both an alternate sequence code and a hexadecimal sequence code.
10-13
RESERVED
4
Reserved.
14-17
SOFTWARE
RELEASE NUMBER
4
Line of Travel release number, shown as nn.n.
18-19
SOFTWARE
MODIFICATION
NUMBER
2
Line of Travel modification number, shown as nn.
20-39
MASTER FILE
IDENTIFICATION
20
Line of Travel Master File version identification string.
40-79
MASTER FILE
CREATION
SOFTWARE
IDENTIFICATION
STRING
40
Identifies the version of Line of Travel software that
created the Master File.
80-100
RESERVED
21
COBOL Calling Example
An example for calling the Line of Travel subroutine can be found in your sample library in member
SMPLDLOT. This is a COBOL program that must be compiled before you run it. You can run this
program using the JCL in member RUNDLOT in your sample library.
Windows Calling Example
An example for calling LTO10 from a “C” routine follows.
#include .h
/* Typedef used to call the COBOL DLL - put this at the top o f the file */
typedef void (FAR *pLTO10) (char* LTIn, char* LTOut);
/*
Load the DLL - this section only needs to be performed once when this executable is run
*/
HINSTANCE hLibrary;
pLTO10 lpfnLTO10;
hLibrary = LoadLibrary("LTO10.dll");
if (hLibrary (HINSTANCE) HINSTANCE_ERROR) {
/*
Error - can't find the DLL - the DLL must be in the same directory as this executable, or it
must be in the path - put your error handling code here
*/
}
/*
Get a pointer to the LTP10() function within the LTO10 DLL This only needs to be performed once
when this executable is run
*/
lpfnLTO10 = (pLTP10) GetProcAddress(hLibrary, "LTO10");
if (lpfnLTO10 == NULL)
{
/*
Error - can't find the LTO10() function within the LTO10 DLL. This should never happen unless
the DLL is corrupted - put your error handling code here
*/
Release 4.1.0
183
User’s Guide - Open Systems
Line of Travel Exit Routine (LTO60)
}
/*
Call the LTO10 function as many times as you want here Prior to this, the LTIn and LTOut,
variables must be declared and initialized
*/
(*lpfnLTO10) (LTIn, LTOut);
Line of Travel Exit Routine (LTO60)
If you want to post the Line of Travel code to your output file, use the LTO60 exit routine. You have
access to this exit routine via the EXITOP parameter. The EXITOP parameter is available from most
Pitney Bowes EXEC-level programs.
The EXITOP parameter defines your input and locations for your output. You must pass a 5-digit ZIP
Code, a 4-digit ZIP+4 Code, a 2-digit DPC, and a 4-byte Carrier Route Code as input.
LTO10 then derives a Line of Travel (LOT) code, which is comprised of a 4-digit Line of Travel
sequence number and a 1-character Line of Travel sequence code, and returns it to the LTO60 exit
routine.
The Line of Travel sequence code is either “A” for ascending, or “D” for descending. Since sorting in
ascending and descending order can be unwieldy, Line of Travel returns two types of alternate
codes that can be sorted in ascending order only.
The alternate sequence code is a two-byte code used for final sortation in place of the DPC add-on.
It consists of an uppercase letter followed by a digit 0 through 9. Values range from “A0” (99
descending) through “J9” (00 descending), and “K0” (00 ascending) through “T9” (99 ascending).
The hexadecimal sequence code is a single-byte code, and it also allows you to sort your file in
ascending order only. There are 200 values ranging from 99 ascending through 00 descending, then
00 ascending through 99 ascending. Both the hexadecimal and alternate sequence codes are
determined from the DPC add-on and the LOT sequence code.
The LTO60 exit routine subsequently returns the information to your Pitney Bowes EXEC-level
program.
EXITOP Parameter for the LTO60 Exit Routine
The EXITOP parameter allows you to call the LTO60 exit routine.
Field-by-Field
The following table provides an overview of the EXITOP parameter fields used to access the LTO60
exit routine.
Fields on the EXITOP Parameter (Part 1 of 3)
Position
Field Name
Description
Comments
1-6
KEYWORD
EXITOP is the only acceptable entry.
Required.
8-15
EXIT ROUTINE
NAME
LTO60 is the only acceptable entry.
LTO60 is dynamically loaded when you enter
this parameter.
Required.
19-22
Location of
ZIP CODE
Location of the input record ZIP Code.
Required.
Release 4.1.0
184
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Line of Travel Exit Routine (LTO60)
Fields on the EXITOP Parameter (Part 2 of 3)
Position
23
Field Name
Format of
ZIP CODE
Description
Comments
Code indicating the format of your input record
ZIP Code. Enter one of the following:
• C — 5-digit ZIP Code in character format.
Required.
• P — 5-digit ZIP Code stored in a 3-byte
packed field.
• R — 9-digit ZIP+4 Code stored in a 5-byte
packed field.
• B — 5-digit ZIP Code stored in a 3- byte
binary field.
• 9 — 9-digit ZIP+4 Code stored in a 4-byte
binary field.
24-27
Location of
ZIP+4 Code
Location of the input record ZIP+4 Code.
Required.
28
Format of
ZIP+4 Code
Format of the input record ZIP+4 Code. Enter
one of the following:
• C — Character format.
Required.
• P — 3-byte packed field.
• B — 2-byte binary field.
29-32
Location of
DELIVERY POINT
CODE
Location of the input record Delivery Point
Code.
Required.
33-36
Location for
LOT CODE
Location for the 5-character Line of Travel
(LOT) code on the output record.
NOTE: If invalid input was presented, this field
will be left blank on the output record.
If valid input was presented, but no match was
successful with the Master File, the record is
default coded, and this field will contain four
zeroes followed by a descending flag (0000D).
Please note that default-coded records are
eligible for the basic enhanced carrier route
rate.
Required.
37-40
Location for
ALTERNATE
SEQUENCE CODE
Location for the 2-character Alternate
Sequence code on the output record.
41-44
Location for
HEXADECIMAL
SEQUENCE CODE
Location for the 1-character Hexadecimal
Sequence code on the output record.
Optional.
One of these
fields are required
if you want the
program to help
you sort your
records in the
sequence
required by the
USPS to obtain
the basic
enhanced carrier
route rate.
45-48
Location for
CARRIER ROUTE
CODE
Location for the input record Carrier Route
Code on the output record.
Release 4.1.0
185
Required.
User’s Guide - Open Systems
Line of Travel Exit Routine (LTO60)
Fields on the EXITOP Parameter (Part 3 of 3)
Position
Field Name
50
Description
REPORT
SUPPRESSION
CODE
Comments
Determines whether the Control Totals Report
will be printed. Enter one of the following codes:
• Blank — The report will be printed (default).
Optional.
• X — The report will not be printed.
51-66


RESERVED
These fields are reserved for future use.
To allow non-COBOL II driver programs to interface with Line of Travel, please refer to the
section “Calling C1PRPT” in your CODE-1 Plus Reference Guide for instructions on using
the COB2INIT and/or COB2INI programs provided.
For z/OS users only. Add the following to your JCL to define your file assignments:
//LTMASTR
//PRNTXOP
DD DSN=file name,DISP=disp
DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=133)
Example
For this example, the following is the input record for Line of Travel.
....+....1....+....2....+....3....+....4....+....5....+....6....+....7....
JOSEPH.BELL...18684.BLUE.BIRD.DRIVE.......GAITHERSBURG..MD20879-123084C001
The parameter below shows you how to define the EXITOP parameter for this input record.
....+....1....+....2....+....3....+....4....+....5....+....6....+....7..
EXITOP.LTO60.......059C.065C.069.256.261.263.072.X......................
•
•
•
•
•
•
•
•
•
•
Release 4.1.0
EXITOP is the name of the parameter.
LTO60 is the name of the exit routine to be called.
059 in columns 19-22 defines the location of the input record ZIP Code, and C in column 23
specifies a character ZIP Code format.
065 in columns 24-27 defines the location of the input record ZIP+4 Code, and C in column 28
specifies a character ZIP+4 Code format.
069 in columns 29-32 defines the location of the Delivery Point Code.
256 in columns 33-36 defines the location for the Line of Travel code on the output record.
261 in columns 37-40 defines the location for the Alternate Sequence Code.
263 in columns 41-44 defines the location for the Hexadecimal Sequence Code.
072 in columns 46-48 defines the location of the Carrier Route Code.
X in column 50 indicates that the Control Totals Report will not be printed.
186
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Control Totals Report
Line of Travel Exit Routine for Unix
This section explains how to use the LTO60 exit routine to access Line of Travel from the Unix
platform.
1. Source the setup of the product from which you are calling Line of Travel. For example, from the
CODE-1 Plus directory (i.e., /usr/g1/c1p/bin), type the following:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)

/usr/gl/c1p is an example directory structure. Your CODE-1 Plus directory may be
different.
2. Complete the EXITOP parameter in the C1P parameter file.
3. Source the job file of the product from which you are calling Line of Travel. For example, from the
CODE-1 Plus directory, type the following:
. ./job (for Bourne shells)
source ./”job” (for C shells)
4. Source the LTO setup file. For example, from the CODE-1 Plus directory, type the following:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)
This adds the $G1LTO/pgms directory to the COBPATH environment variable, enabling the RTS
(run-time system) to find the necessary LTO modules.
5. Run the job.
Line of Travel Exit Routine for Windows
This section describes how to use the LTO60 exit routine to access Line of Travel from the Windows
platform. The Line of Travel routines are LTO10 and LTO60. These routines are loaded into the
%G1LTO%\lib subdirectory when you install Line of Travel.
1. Complete the EXITOP parameter.
2. Place the LTO10.acu and LTO60.acu into the \lib area of the product from which you are calling
Line of Travel. For example, from CODE-1 Plus, place the LTO10.acu and LTO60.acu into the
%G1C1P\lib area.
3. Place the %G1LTO%\lib area into your CODE_PREFIX statement in SETUP.BAT. This allows
Windows to search the listed locations for modules when they are called by the various calling
programs.
Control Totals Report
The Control Totals Report shows you statistics about processed, matched, and unmatched records
for a job. This report is printed automatically when your job is run, unless you type an “X” in position
50 of the EXITOP parameter. If you need to call Pitney Bowes Customer Support about a problem
with any of your jobs, please have this report handy for reference. Numbers and percentages are
listed for the following:
•
•
Release 4.1.0
Records Processed — The number of records that were processed from your input file.
Valid Format ZIP Code Presented — The number of records processed that contained 5-digit
ZIP Codes in valid format. 5-digit ZIP Codes in valid format consist of numeric, non-zero data.
187
User’s Guide - Open Systems
Control Totals Report
•
•
•
•
•
•
•
•
•
•
•
•
Zero Or Non-numeric ZIP+4 Codes Presented — The number of records processed that
contained zeros or non-numeric data in the ZIP+4 field.
Valid Format ZIP+4 Code Presented — The number of records processed that contained 9digit ZIP+4 Codes in valid format. 9-digit ZIP Codes in valid format consist of numeric, non-zero
data.
Valid Format DPC Values Presented — The number of records processed that contained 2digit DPC add-on codes in valid format.
Invalid Carrier Route Codes Presented —The number of records processed that contained a
4-digit Carrier Route Code in invalid format.
Valid Carrier Route Codes Presented —The number of records processed that contained a 4digit Carrier Route Code in valid format.
Records Not Matching Master File, Invalid Input — The number of records that were not
successfully matched against the Line of Travel Master File, due to invalid input. Records with
invalid input contain zeroes or non-numeric data in the ZIP and/or ZIP+4 Code field, or a nonnumeric DPC or invalid Carrier Route Code format.
Records Not Matching Master File, Default Coded — The number of records processed that
did not match the Line of Travel Master file, but contained valid input. These records were default
coded, which means the LOT code is four zeroes followed by a descending flag (0000D). Please
note that default-coded records do qualify for the basic enhanced carrier route rate.
Records Matching LOT Master File — The number of records processed that contained valid
input and were successfully matched against the Line of Travel Master File.
Line of Travel Codes Determined — The number of records processed that were LOT coded.
This number is equal to number of records matching at the ZIP+4 Code level plus the number of
records that were default coded.
LOT Numbers with Ascending Sequence Codes — The number of LOT numbers that are
followed by an ascending (A) flag.
LOT Numbers with Descending Sequence Codes — The number of LOT numbers returned
that are followed by a descending (D) flag.
Alternate DPC Sequence Codes Determined — The number of records processed for which
alternate DPC sequence codes were determined. Please note that LTO60 returns an alternate
sequence code only if positions 37-44 of the EXITOP parameter are not blank.
The following is an example of the Control Totals Report.
Line of Travel Option
LTO60: Control Totals
Line of Travel Option Master File Version:
February 2016
Total Records Presented To Processing Logic
Records Processed
Valid Format ZIP Code Presented
Zero Or Non-numeric ZIP+4 Codes Presented
Valid Format ZIP+4 Code Presented
Non-numeric DPC Values Presented
Valid Format DPC Values Presented
Invalid Carrier Route Codes Presented
Valid Carrier Route Codes Presented
5,890
5,890
5,890
884
5,006
884
5,006
868
5,022
Line of Travel Matching Attempts
5,890
Records Not Matching Master File, Invalid Input
Records Not Matching Master File, Default Coded
Records Matching Line of Travel Master File
Line Of Travel Codes Determined
LOT Numbers with Ascending Sequence Codes
LOT Numbers with Descending Sequence Codes
5,022
3,308
4,703
Alternate DPC Sequence Codes Determined
5,022
Line of Travel Option
Release 4.1.0
2/13/2016
LTO60: Control Totals
188
100.00%
100.00%
10.11%
84.99%
15.01%
84.99%
14.74%
85.26%
868
319
4,703
of
of
of
of
of
of
of
of
Total Records
Records Processed
Records Processed
Records Processed
Records Processed
Records Processed
Records Processed
Records Processed
14.74% of Matching Attempts
5.42% of Matching Attempts
79.85% of Matching Attempts
65.87% of LOT Numbers
34.13% of LOT Numbers
100.00% of LOT Coded Records
2/13/2016
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Alternate Sequence Codes
Alternate Sequence Codes
This section describes how to sort your output records using the two types of alternate sequence
codes generated by the Line of Travel Option. It also provides a reference table for all potential
sequence codes.
Sorting LOT Records Using Alternate Sequence Codes
Line of Travel can help you sort your output records in the sequence required by the USPS to obtain
the basic enhanced carrier route rate. Line of Travel returns two kinds of alternate sequence codes
that you can use when sorting your records prior to presorting your mailing using, for example, the
Pitney Bowes MailStream Plus software.
The Alternate Sequence Code(s) are normally obtained by using the LOTOUT parameter. If you are
using a call or EXITOP to get the Alternate Sequence Code(s), note that in order for Line of Travel to
return the alternate sequence codes, you must present a 2-character DPC add-on as input. If you
are accessing the program via the EXITOP parameter, you must also specify the location of the input
record DPC add-on by completing positions 29-32 on the EXITOP parameter, and you must specify
a location on the output record for one of the alternate sequence codes by completing positions 3740 or 41-44 on the EXITOP parameter.
Line of Travel uses the DPC add-on and the eLOT sequence code, which is either “A” for ascending
or “D” for descending, to determine the two alternate codes.
The alternate sequence code is a two-character code used to sort your file in ascending order only.
It consists of an uppercase letter followed by a digit 0 through 9. Values range from “A0” (99
descending) through “J9” (00 descending), and “K0” (00 ascending) through “T9” (99 ascending).
The hexadecimal sequence code is a single-character code, and it also allows you to sort your file in
ascending order only. There are 200 values ranging from 99 descending through 00 descending,
then 00 ascending through 99 ascending.
If you choose to use one of these codes to sort your file, you must sort your eLOT-coded records in
ascending order in the following sequence:
1. 5-digit ZIP Code
2. 4-byte Carrier Route Code
3. 4-digit Line of Travel Code

This includes only the numeric portion of the eLOT code. It does not include the eLOT
sequence code.
4. 4-byte ZIP + 4 Code
5. 2-byte Alternate Sequence Code or 1-character Hexadecimal Sequence Code

Release 4.1.0
Per USPS regulations, records with missing (blank) or invalid (0000) LOT information are to
be sorted to the end of the CRRT.
189
User’s Guide - Open Systems
Alternate Sequence Codes
Sequence Code Table
This table provides a reference for potential sequence codes that correspond to a combination of the
2-digit DPC add-on, and the eLOT sequence code.
Sequence Codes (Part 1 of 8)
Sequence Order
Release 4.1.0
DPC add-on
eLOT
Sequence
Code
1-character
Hexadecimal
Sequence
Code
2-Byte
Alternate
Sequence
Code
001
99
D
X'21'
A0
002
98
D
X'22'
A1
003
97
D
X'23'
A2
004
96
D
X'24'
A3
005
95
D
X'25'
A4
006
94
D
X'26'
A5
007
93
D
X'27'
A6
008
92
D
X'28'
A7
009
91
D
X'29'
A8
010
90
D
X'2A'
A9
011
89
D
X'2B'
B0
012
88
D
X'2C'
B1
013
87
D
X'2D'
B2
014
86
D
X'2E'
B3
015
85
D
X'2F'
B4
016
84
D
X'30'
B5
017
83
D
X'31'
B6
018
82
D
X'32'
B7
019
81
D
X'33'
B8
020
80
D
X'34'
B9
021
79
D
X'35'
C0
022
78
D
x'36'
C1
023
77
D
X'37'
C2
024
76
D
X'38'
C3
025
75
D
X'39'
C4
190
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Alternate Sequence Codes
Sequence Codes (Part 2 of 8)
Sequence Order
Release 4.1.0
DPC add-on
eLOT
Sequence
Code
1-character
Hexadecimal
Sequence
Code
2-Byte
Alternate
Sequence
Code
026
74
D
X'3A'
C5
027
73
D
X'3B'
C6
028
72
D
X'3C'
C7
029
71
D
X'3D'
C8
030
70
D
X'3E'
C9
031
69
D
X'3F'
D0
032
68
D
X'40'
D1
033
67
D
X'41'
D2
034
66
D
X'42'
D3
035
65
D
X'43'
D4
036
64
D
X'44'
D5
037
63
D
X'45'
D6
038
62
D
X’46’
D7
039
61
D
X'47'
D8
040
60
D
X'48'
D9
041
59
D
X'49'
E0
042
58
D
X'4A'
E1
043
57
D
X'4B'
E2
044
56
D
X'4C'
E3
045
55
D
X'4D'
E4
046
54
D
X'4E'
E5
047
53
D
X'4F'
E6
048
52
D
X'50'
E7
049
51
D
X'51'
E8
050
50
D
X'52'
E9
051
49
D
X'53'
F0
052
48
D
X'54'
F1
191
User’s Guide - Open Systems
Alternate Sequence Codes
Sequence Codes (Part 3 of 8)
Sequence Order
Release 4.1.0
DPC add-on
eLOT
Sequence
Code
1-character
Hexadecimal
Sequence
Code
2-Byte
Alternate
Sequence
Code
053
47
D
X'55'
F2
054
46
D
X'56'
F3
055
45
D
X'57'
F4
056
44
D
X'58'
F5
057
43
D
X'59'
F6
058
42
D
X'5A'
F7
059
41
D
X'5B'
F8
060
40
D
X'5C'
F9
061
39
D
X'5D'
G0
062
38
D
X'5E'
G1
063
37
D
X'5F'
G2
064
36
D
X'60'
G3
065
35
D
X'61'
G4
066
34
D
X'62'
G5
067
33
D
X'63'
G6
068
32
D
X'64'
G7
069
31
D
X'65'
G8
070
30
D
X'66'
G9
071
29
D
X'67'
H0
072
28
D
X'68'
H1
073
27
D
X'69'
H2
074
26
D
X'6A'
H3
075
25
D
X'6B'
H4
076
24
D
X'6C'
H5
077
23
D
X'6D'
H6
078
22
D
X'6E'
H7
079
21
D
X'6F'
H8
192
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Alternate Sequence Codes
Sequence Codes (Part 4 of 8)
Sequence Order
Release 4.1.0
DPC add-on
eLOT
Sequence
Code
1-character
Hexadecimal
Sequence
Code
2-Byte
Alternate
Sequence
Code
080
20
D
X'70'
H9
081
19
D
X'71'
I0
082
18
D
X'72'
I1
083
17
D
X'73'
I2
084
16
D
X'74'
I3
085
15
D
X'75'
I4
086
14
D
X'76'
I5
087
13
D
X'77'
I6
088
12
D
X'78'
I7
089
11
D
X'79'
I8
090
10
D
X'7A'
I9
091
09
D
x'7B'
J0
092
08
D
X'7C'
J1
093
07
D
X'7D'
J2
094
06
D
X'7E'
J3
095
05
D
X'7F'
J4
096
04
D
X'80'
J5
097
03
D
X'81'
J6
098
02
D
X'82'
J7
099
01
D
X'83'
J8
100
00
D
X'84'
J9
101
00
A
X'85'
K0
102
01
A
X'86'
K1
103
02
A
X'87'
K2
104
03
A
X'88'
K3
105
04
A
X'89'
K4
106
05
A
X'8A'
K5
193
User’s Guide - Open Systems
Alternate Sequence Codes
Sequence Codes (Part 5 of 8)
Sequence Order
Release 4.1.0
DPC add-on
eLOT
Sequence
Code
1-character
Hexadecimal
Sequence
Code
2-Byte
Alternate
Sequence
Code
107
06
A
X'8B'
K6
108
07
A
X'8C'
K7
109
08
A
X'8D'
K8
110
09
A
X'8E'
K9
111
10
A
X'8F'
L0
112
11
A
X'90'
L1
113
12
A
X'91'
L2
114
13
A
X'92'
L3
115
14
A
X'93'
L4
116
15
A
X'94'
L5
117
16
A
X'95'
L6
118
17
A
X'96'
L7
119
18
A
X'97'
L8
120
19
A
X'98'
L9
121
20
A
X'99'
M0
122
21
A
X'9A'
M1
123
22
A
X'9B'
M2
124
23
A
X'9C'
M3
125
24
A
X'9D'
M4
126
25
A
X'9E'
M5
127
26
A
X'9F'
M6
128
27
A
X'A0'
M7
129
28
A
X'A1'
M8
130
29
A
X'A2'
M9
131
30
A
X'A3'
N0
132
31
A
X'A4'
N1
133
32
A
X'A5'
N2
194
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Alternate Sequence Codes
Sequence Codes (Part 6 of 8)
Sequence Order
Release 4.1.0
DPC add-on
eLOT
Sequence
Code
1-character
Hexadecimal
Sequence
Code
2-Byte
Alternate
Sequence
Code
134
33
A
X'A6'
N3
135
34
A
X'A7'
N4
136
35
A
X'A8'
N5
137
36
A
X'A9'
N6
138
37
A
X'AA'
N7
139
38
A
X'AB'
N8
140
39
A
X'AC'
N9
141
40
A
X'AD'
O0
142
41
A
X'AE'
O1
143
42
A
X'AF'
O2
144
43
A
X'B0'
O3
145
44
A
X'B1'
O4
146
45
A
X'B2'
O5
147
46
A
X'B3'
O6
148
47
A
X'B4'
O7
149
48
A
X'B5'
O8
150
49
A
X'B6'
O9
151
50
A
X'B7'
P0
152
51
A
X'B8'
P1
153
52
A
X'B9'
P2
154
53
A
X'BA'
P3
155
54
A
X'BB'
P4
156
55
A
X'BC'
P5
157
56
A
X'BD'
P6
158
57
A
X'BE'
P7
159
58
A
X'BF'
P8
160
59
A
X'C0'
P9
195
User’s Guide - Open Systems
Alternate Sequence Codes
Sequence Codes (Part 7 of 8)
Sequence Order
Release 4.1.0
DPC add-on
eLOT
Sequence
Code
1-character
Hexadecimal
Sequence
Code
2-Byte
Alternate
Sequence
Code
161
60
A
X'C1'
Q0
162
61
A
X'C2'
Q1
163
62
A
X'C3'
Q2
164
63
A
X'C4'
Q3
165
64
A
X'C5'
Q4
166
65
A
X'C6'
Q5
167
66
A
X'C7'
Q6
168
67
A
X'C8'
Q7
169
68
A
X'C9'
Q8
170
69
A
X'CA'
Q9
171
70
A
X'CB'
R0
172
71
A
X'CC'
R1
173
72
A
X'CD'
R2
174
73
A
X'CE'
R3
175
74
A
X'CF'
R4
176
75
A
X'D0'
R5
177
76
A
X'D1'
R6
178
77
A
X'D2'
R7
179
78
A
X'D3'
R8
180
79
A
X'D4'
R9
181
80
A
X'D5'
S0
182
81
A
X'D6'
S1
183
82
A
X'D7'
S2
184
83
A
X'D8'
S3
185
84
A
X'D9'
S4
186
85
A
X'DA'
S5
187
86
A
X'DB'
S6
196
User’s Guide - Open Systems
Chapter 10: Using Line of Travel
Alternate Sequence Codes
Sequence Codes (Part 8 of 8)
Sequence Order
Release 4.1.0
DPC add-on
eLOT
Sequence
Code
1-character
Hexadecimal
Sequence
Code
2-Byte
Alternate
Sequence
Code
188
87
A
X'DC'
S7
189
88
A
X'DD'
S8
190
89
A
X'DE'
S9
191
90
A
X'DF'
T0
192
91
A
X'E0'
T1
193
92
A
X'E1'
T2
194
93
A
X'E2'
T3
195
94
A
X'E3'
T4
196
95
A
X'E4'
T5
197
96
A
X'E5'
T6
198
97
A
X'E6'
T7
199
98
A
X'E7'
T8
200
99
A
X'E8'
T9
197
User’s Guide - Open Systems
Alternate Sequence Codes
Release 4.1.0
198
User’s Guide - Open Systems
Using Residential
Delivery Indicator (RDI)
In this chapter:




What is Residential Delivery File Processing? . . . . . . . . . . . . . .200
Building the Residential Delivery File in CODE-1 Plus. . . . . . . .200
Activating the RDI Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202
RDI Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
11
What is Residential Delivery File Processing?
What is Residential Delivery File Processing?
The Residential Delivery Indicator is a licensed product of the USPS. Residential Delivery File (RDI)
processing can help you determine the best cost for shipping your packages based upon the fact
that some delivery services charge a higher price for delivery to a residential address than they do to
a business address. RDI processing can help you shop for the lowest delivery cost for a specific
address by identifying whether an address is listed as a business or a residential address in the
USPS Address Management Systems database.

You must license the raw RDI file directly from the USPS. RDI data is valid for CODE-1 Plus
processing for 105 days from the 1st day of the month of issue. For example, the July 2015
RDI data is valid for CODE-1 Plus processing starting on July 1, 2015 and expires on
October 14, 2015.
RDI is designed to be used in conjunction with CODE-1 Plus. It works similarly to the DPV process,
in that the RDI data is supplied as hash tables. However, it is a much simpler process than DPV in
that the standard hash algorithm is only determined for the 9-digit and 11-digit ZIP Code rather than
the entire address.
While this is called Residential Delivery Indicator, the Residential Delivery File also provides
information regarding business deliveries. The residential status of an input address to which a
ZIP+4 CODE is assigned is determined by the fact that it does not match to a record in either RDI
table.
Using the DPVOUT parameter, CODE-1 Plus provides flags that will allow you to determine between
a residential, business, or mixed (residential and/or business) address.
Building the Residential Delivery File in CODE-1 Plus
To use RDI in your CODE-1 Plus jobs, follow these steps:
1. Obtain the 9-digit and 11-digit hash tables from the USPS.
2. Run the program C1DBRDI to build the RDI masterfile.
3. Tell CODE-1 Plus you want to use the RDI option.
Each step is detailed below, with platform-specific detail where needed.
C1DBRDI Program
CODE-1 Plus provides the C1DBRDI program so you can build an RDI file as often as needed. This
program builds a Pitney Bowes-formatted file that will be accessed by the RDI lookup program.
To build the Residential Delivery Indicator with the RDI file, follow these steps:
1. Receive the latest RDI hash tables from the USPS.
2. Load the RDI hash tables to the platform on which you are running CODE-1 Plus.
3. Run C1DBRDI to build the RDI file.

Release 4.1.0
If you need to FTP the RDI hash tables, the transfer must be performed in binary format (no
data conversion), using a fixed record of 1024 bytes.
200
User’s Guide - Open Systems
Chapter 11: Using Residential Delivery Indicator (RDI)
Building the Residential Delivery File in CODE-1 Plus
In the following sections, find the platform you are using and follow the steps to complete building
your RDI file.
Building Your RDI File in z/OS/IMS
To run C1DBRDI in an z/OS/IMS environment, modify the RDILOAD member in the INSTALL library
according to your site’s needs, and submit the job.
Building Your RDI File in Windows
To build the RDI file in Windows, from the Start menu, select Database Load from the CODE-1 Plus
folder and complete the following steps:
1. Select the Residential Delivery Indicator (RDI) radio button.
2. You will be prompted for two files. First, select the 9-digit RDI table. Then, select the 11-digit RDI
table.
3. Click on [Next] to load your RDI file.

To override the default system date, you must modify the RDIPRM file located in the
%G1C1P%\data directory and format the date as indicated in the FILEDT parameter on
FILEDT Parameter.
Building Your RDI File in Unix
To build your RDI file in Unix, follow these steps:
1. Copy the RDI raw data file obtained from the USPS into the $G1C1P/data subdirectory.
2. Change directory (cd) to the $G1C1P/g1bin subdirectory.
3. Run the Database Install script, installdb.
4. Select CODE-1 Plus.
5. Select Residential Delivery Indicator (RDI).
6. Verify the file input and output areas.
7. Enter the file name of the RDI file that was placed in the $G1C1P/data subdirectory.
8. The load program creates and RDI file in the output area specified in step 6 above. This file is a
relative record file with the name of RDIMSTR.REL.
9. Ensure that the DD_RDIMSTR file definition variable has been defined (reference the sample
script in $G1C1P/bin).
10. CODE-1 Plus can now use the RDI file during processing.

Release 4.1.0
To override the default system date, you must modify the RDIPRM file located in the
$G1C1P\data directory and format the date as indicated in the FILEDT parameter on FILEDT
Parameter.
201
User’s Guide - Open Systems
Activating the RDI Option
FILEDT Parameter
The following table is an overview of each field on the FILEDT parameter.
Fields on the FILEDT Parameter
Position
Field Name
Description
Comments
1-6
KEYWORD
FILEDT is the only acceptable entry.
Systemgenerated
Required.
8-13
FILE DATE
Date of RDI file being created in YYYYMM
format.
Optional.
Default is to use
the system date.
Activating the RDI Option
After building the RDI file, you can use RDI in your CODE-1 Plus processing. Use the following
parameters to activate and define options for RDI processing.
DPVIN Parameter
Use the RDI Indicator field in position 52 of the DPVIN parameter to specify whether to perform RDI
processing. For more information on the DPVIN parameter, please refer to “DPVIN” in your CODE-1
Plus Reference Guide.
DPVOUT Parameter
Use the Location for Residential Flag field in positions 50-52 of the DPVOUT parameter to specify
the location on the output record for a 1-character Residential Flag. One of the following codes is
stored:
•
•
R — Yes, this address is a residential-only delivery point.
Blank — Not a residential delivery point.
For more information on the DPVOUT parameter, please refer to “DPVOUT” in your CODE-1 Plus
Reference Guide.
PGMNAM Parameter
The RDI Large Memory Module (DPV040L) can improve speed during RDI processing. Please refer
to the PGMNAM parameter in your CODE-1 Plus Reference Guide for more information on using
DPV040L.
Release 4.1.0
202
User’s Guide - Open Systems
Chapter 11: Using Residential Delivery Indicator (RDI)
RDI Reports
REPORT Parameter
Use the following REPORT parameter fields to define the RDI reports.
Position
42
Field Name
Residential Delivery
Indicator (RDI)
Processing Summary
Counts
Description
Optional. Specify a code to indicate whether to print the report:
• Y — Print RDI counts.
• N — Do not print RDI counts.
• Blank — Default is Y.
44
Residential Delivery
Indicator (RDI)
Processing Counts by
List Code
Optional. Specify a code to indicate whether to print the report:
• Y — Print the RDI List Code Report.
• N — Do not print the RDI List Code Report.
• Blank — Default is Y.
RDI Reports
You can print RDI processing results on the following reports:
•
•
•
•
Release 4.1.0
Delivery Point Validation Processing Summary Report
RDI Build Report
RDI Counts by List Code Report
Qualitative Statistical Summary (QSS) section of the PS Form 3553 includes the RDI counts
203
User’s Guide - Open Systems
RDI Reports
Release 4.1.0
204
User’s Guide - Open Systems
Auxiliary File Processing
In this chapter:






What is the Early Warning System? . . . . . . . . . . . . . . . . . . . . . . .206
Auxiliary File Processing and EWS . . . . . . . . . . . . . . . . . . . . . . .206
Building the Auxiliary File with the Early Warning System . . . .206
AUXIL Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
Activating the Auxiliary File/Early Warning System File . . . . . .209
Auxiliary File Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
12
What is the Early Warning System?
What is the Early Warning System?
The Early Warning System (EWS) was devised by the USPS to prevent address records from
miscoding due to a delay in postal data reaching the USPS address matching files. The less recent
the ZIP+4 File, the higher potential you have for miscoding addresses. When a valid address is
miscoded because the address it matches to in the ZIP+4 File is inexact, it will result in what is
termed a “broken address.” Once an address is broken, the effect is permanent without manual
intervention.
Using the EWS Auxiliary File with CODE-1 Plus will prevent “broken addresses” from occurring.
EWS consists of records containing partial address information limited to the ZIP Code, street name,
pre- and post-directionals, and a suffix. For an address record to be EWS-eligible, it must be an
address not present on the most recent monthly production ZIP+4 File.
Auxiliary File Processing and EWS
CODE-1 Plus implements EWS through Auxiliary File processing. There are two steps to setting up
your auxiliary file. First, you must reformat the record into a structure recognizable by the CODE-1
Plus matching engine. Second, CODE-1 Plus must recognize the additional auxiliary file.
When you activate the Auxiliary File, addresses that match to the EWS File will not be coded.
CODE-1 Plus will report these records as neither matched nor mismatched records. Additionally,
addresses that match to the EWS file will appear on the Control Totals Report as “Confirmed via
Match to Auxiliary File.”


You must build the Auxiliary File using the C1AUXBLD program, supplied with your CODE-1
Plus software.
The USPS refreshes the EWS file on a weekly basis (Thursdays). You can download the
EWS file from at the USPS RIBBS web site https://ribbs.usps.gov/cassmass/documents/
tech_guides/. It is a line sequential file containing 3950 records and is about 345 KB in size.
However, the number of records and file size is subject to change.
Building the Auxiliary File with the Early Warning System
There are three major steps you must perform to use EWS in your CODE-1 Plus jobs:
•
•
•
Step 1 — Download the latest EWS File onto the NT/Windows machine. This file can be found
on at the USPS RIBBS web site https://ribbs.usps.gov/cassmass/documents/tech_guides/.
Step 2 — Unzip the downloaded file to extract the EWS raw data.
Step 3 — Translate the downloaded EWS File into a form that is recognized by CODE-1 Plus by
using the C1AUXBLD utility.

•
Unix users only: Transfer the extracted input EWS raw data in binary mode onto your
system platform.
Step 4 — Tell CODE-1 Plus you want to use the translated EWS database, the Auxiliary File, in
your job by using the AUXIL1 parameter.
Each step is detailed below, with platform-specific detail where needed.
Release 4.1.0
206
User’s Guide - Open Systems
Chapter 12: Auxiliary File Processing
Building the Auxiliary File with the Early Warning System
C1AUXBLD Utility Program
CODE-1 Plus provides the C1AUXBLD utility program so you can build an EWS file as often as
needed. This utility builds a Pitney Bowes-formatted file that will be utilized by the EWS module/
lookup program.
In order to build the Auxiliary File with the EWS File, do the following:
1. Download the latest EWS File from at the USPS RIBBS web site https://ribbs.usps.gov/
cassmass/documents/tech_guides/.


Unix users only: We recommend that you use an NT/Windows machine to download the
EWS file and extract the raw data. Then FTP the raw data in binary mode to your system
platform.
For non-PC-based platforms, convert to a fixed length file with a record length of 89
bytes. Also, if transferring to a mainframe platform, be sure the character set is converted
to EBCDIC. There are approximately 4,000 records on the EWS file, which are subject to
change.
In the following sections, find the platform you are using and follow the steps to complete building
your Auxiliary File.
Building Your Auxiliary File in z/OS/IMS
To run C1AUXBLD in an z/OS/IMS environment, modify the AUXBLD member in the INSTALL
library according to your site’s needs, and submit the job.
Building Your Auxiliary File in NT
To build the Auxiliary File in NT, from the Start menu, select Database Load from the CODE-1 Plus
folder and complete the following steps:
1. Execute the Database Load Utility.
2. Select the Early Warning System (EWS) radio button.
3. Click on [Browse] to locate your EWS file, or place the full path and file name in the Source text
box.
4. Click on [Next] to load your EWS File.
Building Your Auxiliary File in Unix
To build your Auxiliary File in Unix follow these steps:
1. Copy the EWS raw data file obtained from the USPS website into the $G1C1P/data
subdirectory.
2. Change directory (cd) to the $G1DIR/g1bin subdirectory.
3. Run the Database Install script, installdb.
4. Select CODE-1 Plus.
5. Select Auxiliary Reference File (EWS).
6. Verify the file input and output areas.
Release 4.1.0
207
User’s Guide - Open Systems
AUXIL Parameter
7. Enter the file name of the Auxiliary File that was placed in the $G1C1P/data subdirectory.
8. The load program creates an Auxiliary File in the output area specified in step 6 above. This file
is an indexed sequential file with the name of g1c1aux.
9. Ensure that the DD_G1C1AUX file definition variable has been defined (reference the sample
script in $G1C1P/bin).
10. CODE-1 Plus can now use the Auxiliary File during processing.
AUXIL Parameter
The AUXIL parameter is used with the C1AUXBLD program, and is used to define the field positions
on the input Auxiliary File.
Field-by-Field
The following table is an overview of each field on the AUXIL parameter.
Fields on the AUXIL Parameter (Part 1 of 2)
Position
Field Name
Description
Comments
1-5
Keyword
AUXIL is the only acceptable entry.
Required.
6
Number of the Input File
Only numbers 1 through 9 are acceptable in
this position.
Required.
8
Format Of Input
Parameter
Code indicating the format type of your input
parameter. Choose one of the following
codes:
• A — Street, Suffix, and Directionals in a
single address line.
Required.
• E — Address elements separate.
10-12
Location of 5-digit Zip
Code
Location on the input record of the 5-digit ZIP
Code.
Optional.
14-16
Location of Street Name/
address Line
Location on the input record of the street
name or address line.
Optional.
18-19
Length of Street Name/
address Line
Length of the street name or address line.
Optional.
21-23
Location of Street Suffix
Location on the input record of the street
suffix.
Optional.
25-27
Location of Predirectional
Location on the input record of the predirectional information.
Optional.
29-31
Location of Postdirectional
Location on the input record of the postdirectional information.
Optional.
33-35
Location of House
Range
Location on the input record of 20-character
house range formatted as 10-character low
range followed by 10-character high range.
NOTE: If there is no house range information
in the input record, populate this field with
leading zeros.
Optional.
Release 4.1.0
208
User’s Guide - Open Systems
Chapter 12: Auxiliary File Processing
Activating the Auxiliary File/Early Warning System File
Fields on the AUXIL Parameter (Part 2 of 2)
Position
Field Name
Description
Comments
37-39
Location of Secondary
Range
Location on the input record of 16-character
secondary range formatted as 8-character
low range followed by 8-character high
range.
NOTE: If there is no secondary range
information in the input record, populate this
field with leading zeros.
Optional.
41-43
Location of Secondary
Designator
Location on the input record of the secondary
designator.
Optional.
Activating the Auxiliary File/Early Warning System File
Auxiliary File matching is only available through the CODE-1 Plus batch driver (C1BM00), the
callable batch driver (C1BMCBD), or a user-defined program calling the batch matcher C1MATCHx.
When calling C1MATCHx through a user-defined program, you must populate P9IAUX as defined in
the Input Call Area (P9IN)

The Auxiliary matcher is not available as a stand-alone program or as a callable routine.
To activate and match to the Auxiliary File, you must include the AUXIL1 parameter in your CODE-1
Plus batch job. This is not the same parameter used in the C1AUXBLD program. The AUXIL1
parameter for the CODE-1 Plus batch driver is as follows:
....+....1....+....2....+....3....+....4....+....5
AUXIL1............................................
In addition to the AUXIL1 parameter, you must make the Auxiliary File known to CODE-1 Plus by
defining it in your job control set-up script as G1C1AUX. This file definition should be associated with
the file you created using the C1AUXBLD program described earlier in this chapter.
Auxiliary File Reports
In this section, we describe the two reports that are generated when using the Auxiliary File Option
in CODE-1 Plus.
Auxiliary File Build (C1AUXBLD) Reports
The Auxiliary File Build program (C1AUXBLD), generates a standard Pitney Bowes job report
(PRNTRPT) and an execution log (PRNTXLG). The report lists the parameter given and the control
totals for the job. The execution log shows when the job started and ended. You should check both
reports for any error messages.

Release 4.1.0
Because of the way the Auxiliary File is built for use by CODE-1 Plus, the number of records
read will not equal the number of physical records written to the output G1C1AUX Auxiliary
File.
209
User’s Guide - Open Systems
Auxiliary File Reports
Auxiliary File Build Report
You will find the following information on this report:
•
•
Parameter given
Control totals for your Auxiliary File build job
Auxiliary File Build Execution Log
You will find the following information on the execution log:
•
•
•
•
Date and time of the Auxiliary File build
Number of records read
Number of virtual records written
Number of physical records written
Auxiliary File Reporting in the CODE-1 Plus Matcher
There are no new or separate reports from the CODE-1 Plus matcher as a result of Auxiliary File
matching. The records presented to the CODE-1 Plus matcher that match to the Auxiliary File will
show on a new line of the Control Totals Report under the heading “Confirmed via Match to Auxiliary
File.” These records will not be included in the counts for any of the following major headings on the
Control Totals Report:
•
•
•
Total records for which Address Match attempted
Total Unmatched Records
Total Records successfully Matched
Another new report line, “Total records Matched to EWS,” will appear on the Control Totals Report
when there are EWS matching records. This count will also appear on the PS Form 3553 in Section
E under the heading of EWS.
Release 4.1.0
210
User’s Guide - Open Systems
Reducing Databases and
Creating Media
In this chapter:




Building a Reduced Database . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
Creating a Reduced Database from Delivery Media (Tape) . . . .212
Creating a Reduced Database from Disk . . . . . . . . . . . . . . . . . . .221
Performing Database Media Creation. . . . . . . . . . . . . . . . . . . . . .229
13
Building a Reduced Database
Building a Reduced Database
This chapter describes the CODE-1 Plus G1DBLOAD batch program that you can use to build your
own reduced database from either delivery media (tape) or a previously installed CODE-1 Plus
database (disk). Once you use G1DBLOAD to create a new database, you can run your input nameand-address files against the reduced database to save disk space. This chapter also describes how
to create your own media files of the CODE-1 Plus databases using the G1DBTAP2 program.
Creating a Reduced Database from Delivery Media (Tape)
The G1DBLOAD program normally unloads complete database files during installation. You can use
the instructions in this section to create a reduced or regional CODE-1 Plus database directly from
delivery media (tape).
If you process name-and-address list records in a limited geographic region of the United States,
building and using a reduced database can save you a significant amount of disk space. If you
already have a CODE-1 Plus database installed on your system, you can delete that main database
after you build the reduced database. To save the time associated with installing the complete
database on your system first, create the reduced database directly from the delivery media.
To reduce the database:
1. Define the parameters used by G1DBLOAD to reduce a database.
2. G1DBLOAD prints the Parameter Record Listing and Processing Summary and Execution Log
reports.
Defining Parameters for G1DBLOAD Processing
This section provides information for defining the parameters required to use G1DBLOAD to create
a reduced database.
PRODCD
Required. The PRODCD parameter passes control information to the G1DBLOAD program.
PRODCD Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
PRODCD is the only acceptable entry.
Required.
8-10
Product Code
A 3-character code to specify the product to
be loaded:
C1P
CODE-1 Plus
Required.
Release 4.1.0
212
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Creating a Reduced Database from Delivery Media (Tape)
FILESL
Optional. The FILESL parameter identifies the databases to load into the G1DBLOAD program.
FILESL Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
FILESL is the only acceptable entry.
Optional.
8-15
File Name
An 8-character code to specify the database
to be loaded:
• ALL — All databases
Optional.
Default is ALL.
• C1ALP2 — Abbreviated and Preferred
Alias database
• CITYDB — City Database
• CITYNM — City Name Database
• COUNTY — County Database
• DPVSDB — DPV Split Database
• DPVDB — DPV Flat Database
• DPVHDB — DPV Full Database
• DTLDB — Detail Database
• LCLDB — Locality Database
• LTMASTR — Line of Travel Database
• PTRDB — Pointer Database
• ZIPIDX — ZIP Code Index
• Z4CHNG — ZIP + 4 Change Database
Use the value DPVLOAD for all Delivery
Point Verification databases.
HEADER
Required. The HEADER parameter defines the date and header text to print on reports.
HEADER Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
HEADER is the only acceptable entry.
Required.
8-17
Date
The date that prints on the top of the report.
If you leave this field blank, the current
system date is printed on your report.
Optional.
Default is current
system date.
19-58
Header Text
Any text that identifies the report.
Optional.
No default.
Release 4.1.0
213
User’s Guide - Open Systems
Creating a Reduced Database from Delivery Media (Tape)
PAGESZ
Optional. The PAGESZ parameter defines the number of lines to print on each page of the report(s).
PAGESZ Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
PAGESZ is the only acceptable entry.
Required.
8-10
Lines-Per-Page
The number of lines you want printed on
each page of the report.
Optional.
Default is 60.
Minimum is 25.
Maximum is 225.
12-14
Report
Code indicating whether the specified line
number applies to the reports. Enter the
following code:
RPT
Reports
Optional.
Default is RPT.
REDUCE
Required. The REDUCE parameter specifies the states to include in the reduced database. You
must define at least one state and can define up to 100 REDUCE parameters in a job.
REDUCE Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
REDUCE is the only acceptable entry.
Required.
8-9
11-12
14-15
17-18
20-21
23-24
26-27
29-30
32-33
35-36
38-39
41-42
44-45
47-48
50-51
53-54
56-57
59-60
62-63
65-66
State Abbreviations
Up to 20, 2-character, USPS official state
abbreviations. These states will be
processed and placed in the new regional
database.
You can specify up to 100 state
abbreviations, spread across 100 REDUCE
parameters. An error is not generated if you
repeat a state abbreviation.
The first blank STATE ABBREVIATIONS
field terminates processing of this
parameter.
Required.
One state
required on a
REDUCE
parameter.
One REDUCE
parameter is
required.
NOTE: See “USPS State Abbreviations,”
on page 214 for information on valid
USPS, 2-character state abbreviations.
State Abbreviation Information
USPS State Abbreviations (Part 1 of 2)
State/Region
Name
2-Character
Code
3-Digit SCF
Code
State/Region
Name
2-Character
Code
3-Digit SCF
Code
Alabama
AL
350-369
Kansas
KS
660-679
Alaska
AK
995-999
Kentucky
KY
400-427
APO AA
AA
340-340
Louisiana
LA
700-714
Release 4.1.0
214
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Creating a Reduced Database from Delivery Media (Tape)
USPS State Abbreviations (Part 2 of 2)
State/Region
Name
2-Character
Code
3-Digit SCF
Code
State/Region
Name
2-Character
Code
3-Digit SCF
Code
APO AE
AE
090-098
Maine
ME
039-049
APO AP
AP
962-966
Maryland
MD
206-219
Arizona
AZ
850-865
Massachusetts
MA
010-027
Arkansas
AR
716-729
Michigan
MI
480-499
California
CA
900-961
Minnesota
MN
550-567
Colorado
CO
800-816
Mississippi
MS
386-397
Connecticut
CT
060-069
Missouri
MO
630-658
Delaware
DE
197-199
Montana
MT
590-599
District of
Columbia
DC
200-205
Nebraska
NE
680-693
Florida
FL
320-349
Nevada
NV
889-898
Georgia
GA
300-319
New Hampshire
NH
030-038
Guam
GU
969-969
New Jersey
NJ
070-089
Hawaii
HI
967-968
New Mexico
NM
870-884
Idaho
ID
832-838
New York
NY
100-149
Illinois
IL
600-629
North Carolina
NC
270-289
Indiana
IN
460-479
North Dakota
ND
580-588
Iowa
IA
500-528
Ohio
OH
430-459
Oklahoma
OK
730-749
Utah
UT
840-847
Oregon
OR
970-979
Vermont
VT
050-059
Pennsylvania
PA
150-196
Virgin Islands
VI
008-008
Puerto Rico
PR
006-009
Virginia
VA
220-246
Rhode Island
RI
028-029
Washington
WA
980-994
South Carolina
SC
290-299
West Virginia
WV
247-268
South Dakota
SD
570-577
Wisconsin
WI
530-549
Tennessee
TN
370-385
Wyoming
WY
820-831
Texas
TX
750-799
Release 4.1.0
215
User’s Guide - Open Systems
Creating a Reduced Database from Delivery Media (Tape)
UFTxx
Optional. The UFTxx parameter defines up to four additional footer lines to print on every page of
every report.
UFTxx Parameter Fields
Position
Field Name
Description
Comments
1-3
Keyword
UFT is the only acceptable entry.
Required.
4
Line Number
The footer line number. Enter 1, 2, 3, or 4.
Required.
No default.
5
Line Side
The side of the footer line on which this text
should appear. Enter one of the following
codes:
A
Left side of the line.
B
Right side of the line.
Required.
No default.
7-72
Footer Text
Specify the text to display at the bottom of
every page of each report.
Required.
No default.
UHDxx
Optional. The UHDxx parameter defines text to print at the top of each page of each report. You can
define up to four additional header lines.
UHDxx Parameter Fields
Position
Field Name
Description
Comments
1-3
Keyword
UHD is the only acceptable entry.
Required.
4
Line Number
The header line number. Enter 1, 2, 3, or 4.
Required.
No default.
5
Line Side
The side of the header line on which this text
should appear. Enter one of the following
codes:
A
Left side of the line.
B
Right side of the line.
Required.
No default.
7-72
Header Text
The text that you want to appear at the top of
each page of every report.
Required.
No default.
G1DBLOAD Reports
The G1DBLOAD database reduction program produces the following reports.
G1DBLOAD Reports
Report
Parameter Record Listing
Report
Release 4.1.0
Description
Shows the parameters that were in file C1DRPRM for the database
reduction operation.
216
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Creating a Reduced Database from Delivery Media (Tape)
G1DBLOAD Reports
Report
Description
Processing Summary
Report
Shows the number of records per file in the reduced database.
Execution Log
Shows the steps that CODE-1 Plus executes when processing your nameand-address file.
The C1DBSTSZ program produces the CODE-1 Plus State Sizes Report. This report shows the
approximate size in bytes of each state's data within your database. For more information on
CODE-1 Plus reports, please refer to "Generating CODE-1 Plus Reports” on page 117.
Input File Names
The following file assignments are used when you reduce the database from delivery media (e.g.,
tape).
Input Files for Media-to-Disk Reduction
Assignment
Release 4.1.0
File Name
G1FILE
Input Media Image 1
G2FILE
Input Media Image 2
G3FILE
Input Media Image 3
G4FILE
Input Media Image 4
G5FILE
Input Media Image 5
G6FILE
Input Media Image 6
G7FILE
Input Media Image 7
G8FILE
Input Media Image 8
G9FILE
Input Media Image 9
G10FILE
Input Media Image 10
217
User’s Guide - Open Systems
Creating a Reduced Database from Delivery Media (Tape)
Output File Names
The following table lists the file names for each reduced output database file required by
G1DBLOAD.
Output Files for Reduced Output Database Files
File Name

Description
ZPIDX
Output ZIPINDEX file
CITYDB
Output CITYDTLS file
CITYNM
Output CITYNAME file
COUNTY
Output COUNTY file
Z4CHNG
Output Z4CHANGE file
LCLDB
Output LOCALITY file
DTLDB
Output DETAILS file
LTMASTR
Output LOT file
PTRDB
Output pointer file
C1STRDB
Input enhanced street matching file
When you reduce a database, the ZIPINDEX and City Names files are not reduced.
Information in ZIPINDEX and City Names is used to navigate through the other database
files. These files combined contain less than 2 MB of data.
Executing G1DBLOAD
This section lists the file names to use in your platform control language to run G1DBLOAD. Each
platform section lists the file(s) (e.g., JCL, BAT, CMD) in your product directories that you should
modify according to your site and procedures to run G1DBLOAD. To minimize maintenance, the file
layouts are not included here.
Release 4.1.0
218
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Creating a Reduced Database from Delivery Media (Tape)
File Names for Executing G1DBLOAD
File Names for Executing the G1DBLOAD Program
File Name
Description
G1FILE
Input Media Image 1
G2FILE
Input Media Image 2
G3FILE
Input Media Image 3
G4FILE
Input Media Image 4
G5FILE
Input Media Image 5
G6FILE
Input Media Image 6
G7FILE
Input Media Image 7
G8FILE
Input Media Image 8
G9FILE
Input Media Image 9
G10FILE
Input Media Image 10
IMS and z/OS JCL
To run G1DBLOAD in an IMS or z/OS environments, modify the C1PDBR member in the INSTALL
library according to your site’s needs.
The start of the members has a chart containing substitutable variables, which you may customize
according to your site standards.
Unix Environment
To run G1DBLOAD under Unix, complete the following steps.
1. Edit the data/rdbunld.prm file to include the regions that you need to include in the reduced
database. The data/rdbmedia.prm file contains all the state codes that you can include in a
reduced database. Edit the file for your database reduction needs.
2. Source the setup script to set up the CODE-1 Plus environment variables. The setup script sets
all the CODE-1 Plus environment variables. For more information on the bin/setup file, see your
Installation Instructions.
3. Modify the environment variables in the setc1pdb_raw script. If you are building a reduced
database from subscription media, modify the setc1pdb_raw script. You only need to change the
$g1reddb environment variable to point to where you would like your reduced database to
reside. The default is $g1dir/rddb.

It is recommended that you make a back-up copy of this file before you modify it.
4. Run the installdb script to execute the G1DBLOAD batch driver. After modifying the appropriate
script in Step 2, run the installdb script found in the g1bin directory ($g1dir/g1bin/installdb).
Release 4.1.0
219
User’s Guide - Open Systems
Creating a Reduced Database from Delivery Media (Tape)
Windows Environment
To run the G1DBLOAD program in the Windows environment, complete these steps.
1. Edit the REDIVP.BAT file in the CMDS subdirectory of your CODE-1 Plus installation to create
the reduced database from your original installation media. Copy and modify the appropriate file
to meet your needs. To edit this file:
a. Click on the Edit Job File icon.
b. Specify REDIVP as the job to edit.
2. Edit the REDIVP.PRM file in the DATA subdirectory of your CODE-1 Plus installation. Copy and
modify this file to meet your needs. To edit this file:
a. Click on the Edit File icon.
b. Specify REDIVP as the file to edit.
3. Run the reduce database job. To run your job:
a. Click on the Reduce Database icon.
b. When prompted for the name of the job to run, enter REDIVP, (or the name under which you
saved your job file).
c. After job processing completes, you will be asked if you want to view an execution log. If you
want to view this log at a later time, you can find it as a.xlg file in the directory where you
installed your reduced database.
If you would like your reduced database files to reside in a directory other than the main database
directory, create a G1RDB environment variable, setting it to the full path of the desired destination
directory. Otherwise, your reduced database files are placed in the directory specified by G1DB and
renamed to avoid duplication.
If you choose to put your output files into the directory specified by G1DB, rename the files
according to the table below. Replace the file name in the left column with the file name in the right
column. Also, make sure that the files in the right column do not already exist in the G1DB directory.
Original File Name
Release 4.1.0
Must Be Renamed To...
RDSTRDB
C1STRDB
RDCTYDTL
CITYDB
RDCTYNAM
CITYNM
RDCTYNAM.VIX
CITYNM.VIX
RDCOUNTY
COUNTY
RDCOUNTY.VIX
COUNTY.VIX
RDDETAIL
DTLDB
RDLOCAL
LCLDB
RDLTMSTR
LTMASTR
RDLCLPTR
PTRDB
RDZIPIDX
ZIPIDX
RDZIPIDX.VIX
ZIPIDX.VIX
220
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Creating a Reduced Database from Disk
Original File Name
Must Be Renamed To...
RDZ4CHNG
Z4CHNG
RDZ4CHNG.VIX
Z4CHNG.VIX
Creating a Reduced Database from Disk
This section provides instruction for using the C1PDRDSK program to create a reduced or regional
CODE-1 Plus database directly from a previously installed CODE-1 Plus database (disk).
If you process name-and-address list records in a limited geographic region of the United States,
building and using a reduced database can save you a significant amount of disk space. If you
already have a CODE-1 Plus database installed on your system, you can delete that main database
after you build the reduced database. To save the time associated with installing the complete
database on your system first, you can create the reduced database directly from the delivery
media.
Follow these steps to reduce the database:
1. Define the parameters C1PDRDSK uses to reduce the database.
2. C1PDRDSK calls program C1PDR and passes a parameter call area containing the information
that C1PDR requires to reduce the database. Some of this information originates from the
parameters.
3. C1PDR attempts or performs the database reduction.
4. C1PDR passes back to C1PDRDSK a code indicating whether the database reduction was
successful, as well as the information that C1PDRDSK requires to print the Print Summary by
State.
5. C1PDRDSK prints the Parameter Record Listing and Processing Summary by State and
Parameter Record Listing reports.
This section describes the parameter layouts needed to use C1PDRDSK, the parameter call area,
and control language for using C1PDR.
Defining Parameters for C1PDRDSK Processing
This section provides information for defining the parameters required to use C1PDRDSK to create
a reduced database. The presence of this parameter file invokes C1PDR, the routine that reduces
your database.
C1PDRDSK Parameters
Parameter
Description
CONTRL
Required. Passes control of C1PDRDSK to the program C1PDR, which
reduces the database.
HEADER
Required. Defines a main heading to appear on the first page of each
report.
PAGESZ
Required. Defines the number of lines to print on each report.
STATES
One is required. Specifies the states to include in the reduced database.
Release 4.1.0
221
User’s Guide - Open Systems
Creating a Reduced Database from Disk
C1PDRDSK Parameters
Parameter
Description
UHDxx
Optional. Defines up to four additional header lines that print on every page
of every report.
UFTxx
Optional. Defines up to four additional footer lines that print on every page
of every report.
CONTRL
Required. The CONTRL parameter passes control information to the C1PDR program C1PDR.
CONTRL Parameter Fields
Position
1-6
Field Name
Keyword
Description
Comments
CONTRL is the only acceptable entry.
Required.
HEADER
Required. The HEADER parameter defines the date and header text to print on reports.
HEADER Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
HEADER is the only acceptable entry.
Required.
8-17
Date
The date that prints on the top of the report.
If you leave this field blank, the current
system date is printed on your report.
Optional.
Default is current
system date.
19-58
Header Text
Any text that identifies the report.
Optional.
No default.
PAGESZ
Optional. The PAGESZ parameter defines the number of lines to print on each page of the report(s).
PAGESZ Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
PAGESZ is the only acceptable entry.
Required.
8-10
Lines-per-page
The number of lines you want printed on
each page of the report.
Optional.
Default is 60.
Minimum is 25.
Maximum is 225.
12-14
Report
Code indicating whether the specified line
number applies to the reports. Enter the
following code:
RPT
Reports.
Optional.
Default is RPT.
Release 4.1.0
222
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Creating a Reduced Database from Disk
STATES
Required. The STATES parameter specifies the states to include in the reduced database. You
must define at least one state and can define up to 100 STATES parameters in a job.
STATES Parameter Fields.
Position
Field Name
Description
Comments
1-6
Keyword
STATES is the only acceptable entry.
Required.
8-9
11-12
14-15
17-18
20-21
23-24
26-27
29-30
32-33
35-36
38-39
41-42
44-45
47-48
50-51
53-54
56-57
59-60
62-63
65-66
State Abbreviations
Up to 20, 2-character, USPS official state
abbreviations. These states will be
processed and placed in the new regional
database.
You can specify up to 100 state
abbreviations, spread across 100 STATES
parameters. An error is not generated If you
repeat a state abbreviation.
The first blank STATE ABBREVIATIONS
field terminates processing of this
parameter.
Required.
One state required
on a STATES
parameter.
One STATES
parameter is
required.
NOTE: See “USPS State Abbreviations,”
on page 214 for information on valid
USPS, 2-character state abbreviations.
UFTxx
Optional. The UFTxx parameter defines up to four additional footer lines to print on every page of
every report.
UFTxx Parameter Fields
Position
Field Name
Description
Comments
1-3
Keyword
UFT is the only acceptable entry.
Required.
4
Line Number
The footer line number. Enter 1, 2, 3, or 4.
Required.
No default.
5
Line Side
The side of the footer line on which this text
should appear. Enter one of the following
codes:
A
Left side of the line.
B
Right side of the line.
Required.
No default.
7-72
Footer Text
The text that you want to appear at the
bottom of every page of each report.
Required.
No default.
Release 4.1.0
223
User’s Guide - Open Systems
Creating a Reduced Database from Disk
UHDxx
Optional. The UHDxx parameter defines text to print at the top of each page of every report. You
can define up to four additional header lines.
UHDxx Parameter Fields
Position
Field Name
Description
Comments
1-3
Keyword
UHD is the only acceptable entry.
Required.
4
Line Number
The header line number. Enter 1, 2, 3, or 4.
Required.
No default.
5
Line Side
The side of the header line on which this text
should appear. Enter one of the following
codes:
A
Left side of the line.
B
Right side of the line.
Required.
No default.
7-72
Header Text
The text that you want to appear at the top of
each page of every report.
Required.
No default.
C1PDRDSK Reports
The C1PDRDSK database reduction program produces the following reports.
C1PDRDSK Reports
Report
Description
Parameter Record Listing
Report
Shows the parameters that were in file C1DRPRM for the database
reduction operation.
Processing Summary by
State Report
Shows the number of records per file in the reduced database.
Execution Log
Shows the steps that CODE-1 Plus executes when processing your nameand-address file.
The C1DBSTSZ program produces the CODE-1 Plus State Sizes Report. This report shows the
approximate size in bytes of each state's data within your database. For more information on
CODE-1 Plus reports, please refer to "Generating CODE-1 Plus Reports” on page 117.
Calling the C1PDR Module
The C1PDR module uses, as parameters, a 4,682-character call area. This call area contains the
database input type, the abbreviations of the states to be reduced, and the information that C1PDR
returns to the C1DRDSK program.
Release 4.1.0
224
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Creating a Reduced Database from Disk
Input File Names
The following file assignments are used when you reduce the database from a disk.
Input Files for Disk-to-Disk Reduction
File Name
Description
ZIPIDX
Input ZIPINDEX file
CITYIDB
Input CITYDTLS file
CITYNX
Input CITYNAME file
CNTYX
Input COUNTY file
Z4CHX
Input Z4CHANGE file
LCLIDB
Input LOCALITY file
DTLIDB
Input DETAILS file
LOTIDB
Input LOT file
PTRIDB
Input pointer file
C1STRDB
Input enhanced street matching file
Output File Names
The following table lists the file names for each reduced output database file required by C1PDR.
Output Files for Reduced Output Database Files
File Name

Release 4.1.0
Description
ZPIDX
Output ZIPINDEX file
CITYDB
Output CITYDTLS file
CITYNM
Output CITYNAME file
COUNTY
Output COUNTY file
Z4CHNG
Output Z4CHANGE file
LCLDB
Output LOCALITY file
DTLDB
Output DETAILS file
LTMASTR
Output LOT file
PTRDB
Output pointer file
C1STRDB
Output database file
When you reduce a database, the ZIPINDEX and City Names files are not reduced. Use the
information in ZIPINDEX and City Names to navigate through the other database files. These
files combined contain less than 2 MB.
225
User’s Guide - Open Systems
Creating a Reduced Database from Disk
C1PDR Parameter Call Area
The C1PDR call area is associated with a specific map. This map describes the data that is stored in
each byte of the call area. Because the map is specific, the callable module and the driver program
“know” where each piece of data is stored in the call area. Instead of passing all of the data between
the driver and the callable module, the only parameter that is passed between the two programs is
the name of the call area. The C1PDR module uses, as parameters, the name of one call area that
includes 4,682 characters.

The COBOL copy member of this call area, DRPARM, is provided on your installation media
(in the installation library).
The C1PDR Call Area (Part 1 of 2)
Position
Name
Length
Contents
1
DR-SOURCE
1
A 1-character code indicating whether the
database to be reduced resides on a distribution
media or on a disk. One of the following values is
stored:
T
The complete database resides on
distribution media.
D
The complete database resides on disk.
2-201
DR-STATE-ARRAY
200
An array of all the valid, 2-character USPS state
abbreviations to be included in the reduced
database.
Output from the Database Reduction Process
202
DR-GRC
1
A 1-character code indicating whether the
database was successfully reduced or failed in the
process. One of the following codes is stored:
Blank The database was successfully reduced.
X
The input database expired.
E
An error occurred during the database
reduction.
203-282
DR-VINTAGE-STRING
80
An 80-character message indicating the vintage
date of the reduced database.
283-602
DR-EXPIRATIONMSG-GRP
320
Up to four lines, 80-characters long indicating the
expiration date for the database, and any warning
messages for future expiration.
603-682
DR-ERROR-MSG
80
If position 202, the DR-GRC field, contains an E
(error during reduction process), this field contains
the error message.
683-4,682
DR-STATESCOUNTS-GRP
4,000
This is an array of information about each state
included in the database reduction process. This
array occurs up to 100 times.
The following layout occurs 100 times within the DR-STATES-COUNTS-GRP field:
Release 4.1.0
DR-STATE ABBV
2
The 2-character state abbreviation.
DR-STATE-NAME
15
The 15-character state name.
DR-STATE-SCF
7
The range of Sectional Center Facilities residing in
the current state. The format is ###-###.
226
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Creating a Reduced Database from Disk
The C1PDR Call Area (Part 2 of 2)
Position
Name
Length
Contents
DR-STATE-LOCALITY
4
A 4-byte binary value containing the number of
bytes in the Locality file that apply to the current
state.
DR-STATE-DETAILS
4
A 4-byte binary value containing the number of
bytes in the Details file that apply to the current
state.
DR-STATECITYNAME
4
A 4-byte binary value containing the number of
bytes in the City Name file that apply to the current
state.
DR-STATE-COUNTY
4
A 4-byte binary value containing the number of
bytes in the County file that apply to the current
state.
DR-STATE-LOT
4
A 4-byte binary value containing the number of
bytes in the LOT file that apply to the current state.
Executing C1PDR
This section lists the file names used in your platform control language to run C1PDR. Each platform
section lists the file(s) (e.g., JCL, BAT, CMD) in your product directories that you should modify
according to your site and procedures to follow to run C1PDR. To minimize maintenance, the file
layouts are not listed here.
IMS JCL
To run RUNDBRD in an IMS environment, modify the RUNDBRD member in the INSTALL library
according to your site needs.
z/OS JCL
To run RUNDBRD in an z/OS environment, modify the RUNDBRD member in the INSTALL library
according to your site needs.
Unix Environment
To run C1PDR under Unix, complete the following steps.
1. Edit the data/rdbunld.prm file to include the regions to include in the reduced database. This file
contains all the state codes that you can include in a reduced database. Edit the file for your
database reduction needs.
2. Source the setup script to set up the CODE-1 Plus environment variables. The setup script sets
all the CODE-1 Plus environment variables. For more information on the bin/setup file, see your
Installation Instructions.
Release 4.1.0
227
User’s Guide - Open Systems
Creating a Reduced Database from Disk
3. If you are building a reduced database from an previously-installed full database, modify the
environment variables in setc1pdb_disk script. You only need to change the $g1reddb
environment variable to point to the location where you would like your reduced database to
reside. The default is $g1dir/rddb.

It is recommended that you make a copy of this file before you modify it.
4. Run the installdb script found in the g1bin directory ($g1dir/g1bin/installdb) to
execute the C1PDR batch driver.
Windows Environment
To run the C1PDR program in the Windows environment, complete these steps.
1. Edit the REDDSK.BAT file in the CMDS subdirectory of your CODE-1 Plus installation to create
the reduced database from an installed database. Copy and modify the appropriate file to meet
your needs. To edit this file:
a. Click on the Edit Job File icon
b. Specify REDDSK as the job to edit.
2. Edit the RDBUNLD.PRM file in the DATA subdirectory of your CODE-1 Plus installation. Copy
and modify this file to meet your needs. To edit this file:
a. Click on the Edit File icon.
b. Specify RDBUNLD as the file to edit.
3. Run the reduce database job. To run your job:
a. Click on the Reduce Database icon.
b. When prompted for the name of the job to run, enter REDDSK, (or the name under which you
saved your job file).
c. When the job completes running, you will be asked if you want to view an execution log. If
you want to view this log at a later time, you can find it as an .xlg file in the directory where
you installed your reduced database.
If you would like your reduced database files to reside in a directory other than the main database
directory, you must create a G1RDB environment variable. Set the G1RDB environment variable to
the full path of the desired destination directory. Otherwise, your reduced database files are placed
into the directory specified by G1DB and renamed to avoid duplication.
If you choose to put your output files into the same directory specified by G1DB, rename the files
according to the table below. Replace the file name in the left column with the file name in the right
column. Also, make sure that the files in the right column do not already exist in the G1DB directory.
Original File Name
Release 4.1.0
Must Be Renamed To...
RDSTRDB
C1STRDB
RDCTYDTL
CITYDB
RDCTYNAM
CITYNM
RDCTYNAM.VIX
CITYNM.VIX
RDCOUNTY
COUNTY
RDCOUNTY.VIX
COUNTY.VIX
228
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Performing Database Media Creation
Original File Name
Must Be Renamed To...
RDDETAIL
DTLDB
RDLOCAL
LCLDB
RDLTMSTR
LTMASTR
RDLCLPTR
PTRDB
RDZIPIDX
ZIPIDX
RDZIPIDX.VIX
ZIPIDX.VIX
RDZ4CHNG
Z4CHNG
RDZ4CHNG.VIX
Z4CHNG.VIX
Performing Database Media Creation
The G1DBTAP2 program copies complete or reduced databases to media files. The program is
designed to recognize the capacity of various media formats and only write data within 10% of the
desired media capacity. The valid types of media that the G1DBTAP2 program recognizes are listed
next.
Media Type
Media Format
Media Capacity
CD
CD/ROM diskette
650 MB
TAPE
6250 BPI magnetic tape
180 MB
CART
3480/90 cartridge tape
210 MB
4MM
4-millimeter cartridge tape
2 GB
8MM
8-millimeter cartridge tape
5 GB
Q120
QIC120 cartridge tape
128 MB
IDS
Internet distribution
Unlimited
The G1DBTAP2 program generates one file onto a single piece of media (limited to its capacity).
The program creates a total number of media files to contain all of the selected databases. Each
physical media file contains several logical files. For example, Pitney Bowes ships the current nine
databases for CODE-1 Plus on two CD/ROMs for systems like NT or AS/400, and on six 3480 tape
cartridges for systems like z/OS.
Internet Distribution (IDS) is a special type. IDS allows for a single file to contain all of the selected
databases. You can use this type of media file to send over the Internet, or some other bulk data
transfer method, to another site and load the selected databases there. The format of all these
media files is compatible with the G1DBLOAD program. To execute the database media creation:
1. Define the parameters used by G1DBTAP2 to specify which files you wish to include and the
required media type.
2. G1DBTAP2 prints the Parameter Record Listing, Processing Summary, and the Execution Log.
Release 4.1.0
229
User’s Guide - Open Systems
Performing Database Media Creation
Defining Parameters for G1DBTAP2 Processing
To create media files, define the parameters described next. A brief description of each parameter
you can use to define a G1DBTAP2 job follows.
PRODID
Required. The PRODID parameter identifies the product, version, release, and description to the
G1DBTAP2 program.
PRODID Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
PRODID is the only acceptable entry.
Required.
8-10
Product Code
A 3-character code to specify the product to be
built.
C1P
CODE-1 Plus
Required.
12
Product Version
A single number representing the current
version of the product.
Required.
14
Product Release
A single number representing the current
release of the product.
Required.
16-45
Product
Description
Any 30 character text description.
Required.
MEDIA
Required. The MEDIA parameter defines the type of media to be created by the G1DBTAP2
program.
MEDIA Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
MEDIA is the only acceptable entry.
Required.
8-11
Media Type
A 2 to 4-character code to specify the type of
media desired.
CD
CD/ROM
TAPE 6250 BPI Tape
CART 3480/90 Cartridge Tape
4MM
4 Millimeter Tape
8MM
8 Millimeter Tape
Q120 QIC120 Cartridge Tape
IDS
Internet Distribution
Required.
13
Media Blocksize
A number to specify the block size of the
output files.
24576 Recommended value.
Required.
19
Media Header
Records
A single character to specify whether or not
to include media header records.
Y
Yes
N
No
Optional.
Default is N.
Release 4.1.0
230
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Performing Database Media Creation
FILEDF
Required. The FILEDF parameter defines the databases to include on the media. At least one
record is required for the G1DBTAP2 program. The order of the records presented to G1DBTAP2 is
the order the databases are written to the media files.
FILEDF Parameter Fields
Position
Field Name
Description
Comments
1-6
Keyword
FILEDF is the only acceptable entry.
Required.
8-15
File Name
The name of the database to be copied to
the media file.Valid entries for CODE-1 Plus
and the recommended order:
ZIPIDX ZIP Code Index
CITYDB City Detail
CITYNM City Name
COUNTY County Name
Z4CHNG ZIP + 4 Change
LCLDB Locality Detail
DTLDB Details
PTRDB Pointer File
LTMASTR Line of Travel
C1STRDB Enhanced Street Matching
Required.
17-19
File Product
Code
A 3-character code to specify the product to
be built.
C1P
CODE-1 Plus
Required.
21-32
File Version,
Release,
Modification,fix
Level
A string of data to show the version, release,
modification, and the fix level of the file.
Format is vv.rr.mm.xxx where:
vv
Version
rr
Release
mm
Modification
xxx
Fix Level
NOTE: Each field is separated by a required
period (.).
For example, for CODE-1 Plus,
03.80.00.000.
Required.
34-38
File Blocksize
Specify the block size of the file selected.
Required.
40
File Type
Specify the file type:
I
Indexed
R
Relative
S
Sequential
Required.
42-46
File Key Length
Specify the length of the key field for indexed
file(s).
Required only for
indexed files.
48-52
File Key Poisiton
Specify the location of the key field for an
indexed file(s).
Required only for
indexed files.
Release 4.1.0
231
User’s Guide - Open Systems
Performing Database Media Creation
ADDESC
Optional. The ADDESC parameter defines an additional description to the media header records.
This description is in addition to the description provided on the PRODID parameter for the
G1DBTAP2 program.
The Fields on the ADDESC Parameter
Position
Field Name
Description
Comments
1-6
Keyword
ADDESC is the only acceptable entry.
Optional.
8-42
Description
Define a 35-character descriptive phrase or
text to add to the media header records.
Optional.
VNTAGE
Optional. The VNTAGE parameter overrides the current date with a defined date. This date is only
used to determine the type of vintage description to use in the media header records and does not
override any other date field in the media header records.
The Fields on the VNTAGE Parameter
Position
Field Name
Description
Comments
1-6
Keyword
VNTAGE is the only acceptable entry.
Optional.
8-9
Date Month
A 2-digit number between 01 and 12 to
represent the month of the desired vintage
notation.
Optional.
11-12
Date Year
A 2-digit number between 00 and 99 to
represent the year of the desired vintage
notation.
Optional.
G1DBTAP2 Reports
The G1DBTAP2 media create program produces three reports:
G1DBTAP2 Reports
Report
Description
Parameter Record Listing
Shows the parameters that were in the file G1DBPRM input file.
Processing Summary
Report
Shows the number of records per file, number of media files created, and
the product/version/release of the files.
Execution Log
Shows the steps that CODE-1 Plus executes when processing your nameand-address file.
For more information on CODE-1 Plus reports, please refer to "Generating CODE-1 Plus Reports”
on page 117.
Release 4.1.0
232
User’s Guide - Open Systems
Chapter 13: Reducing Databases and Creating Media
Performing Database Media Creation
Input File Names
The following file assignments are used when you create media files.
Assignment
File Name
G1DBPRM
Parameter Record Input File
ZIPIDX
ZIP Code Index Database
CITYDB
City Details Database
CITYNM
City Names Database
COUNTY
County Names Database
Z4CHNG
ZIP + 4 Change Database
LCLDB
Locality Database
DTLDB
Details Database
PTRDB
Pointer Database
LTMASTR
Line of Travel Database
Output File Names
The following file assignments are used when you create media files.
Assignment
Release 4.1.0
File Name
TAPBLK01
Media Output File 1
TAPBLK02
Media Output File 2
TAPBLK03
Media Output File 3
TAPBLK04
Media Output File 4
TAPBLK05
Media Output File 5
PRNTRPT
Parameter Record and Processing
Summary Reports
PRNTXLG
Execution Log Report
233
User’s Guide - Open Systems
Performing Database Media Creation
Executing G1DBTAP2
This section lists the files used in your platform control language to run G1DBTAP2. Each platform
section lists the file(s) (e.g., JCL, BAT, CMD) in your product directories that you should modify
according to your site and any procedures to follow to run G1DBTAP2. To minimize maintenance,
the file layouts are not listed here.
IMS Job Control Language (JCL)
To create media files using G1DBTAP2 in an IMS environment, modify the C1PTAP2 member in the
INSTALL library according to your site needs.
z/OS Job Control Language (JCL)
To create media files using G1DBTAP2 in an z/OS environment, modify the C1PTAP2 member in
the INSTALL library according to your site needs.
Release 4.1.0
234
User’s Guide - Open Systems
Glossary
Alphabetic character
Any one of the letters A through Z (upper case and lower case).
Alphanumeric character
Any one of the alphabetic characters, or any one of the digits 0 through 9.
Batch job
A batch job consists of a predefined group of processing actions that are
done with little or no interaction between a user and the system. A user
puts the batch job on a job queue (or list), where it waits until the system is
ready for it.
Bit
A unit of data used to make up the bytes of information to be used in
processing. Either of the binary digits 0 or 1.
Byte
A group of 8 adjacent bits. In the EBCDIC and ASCII coding systems, 1
byte represents a character, such as 1 letter in the alphabet. In the doublebyte coding system, 2 bytes represent a character.
Character
Any letter, number or other symbol in the data character set that is part of
the organization, control, or representation of data.
Carrier code
A code assigned to each address on a mail carrier’s route.
Coded output file
Output file that contains processed records coded with ZIP + 4 and/or
carrier route codes.
Constant
Data that has an unchanging, predefined value to be used in processing. A
constant does not change during the running of the program, while the
contents of a field or variable can.
Customer file
An input or output file that contains customer’s names and addresses.
GL
Glossary
Default value
A value supplied by the system that is used when no other value is specified by the user.
Directional
A prefix or suffix on an address that identifies a direction. Predirectionals precede street names,
such as W. Terry Avenue. Post directionals follow street names, such as 23 Democracy Avenue,
NW.
Dropped address information
Address elements dropped during the matching process.
Embedded blank
A space between the characters in a unit of data.
Exit routine
Programming that enables another routine or module, separate from CODE-1 Plus, to execute a
series of operations and then return to CODE-1 Plus.
Field
A group of related characters (such as a name or amount) that are treated as a unit in a record.
File
A generic term for a set of related records treated as a unit.
Firm name
The company name associated with an address.
General delivery
Mail picked up at post offices by customers who do not use a post office box.
High-rise delivery point
An address in an apartment or office building that accepts mail for tenants or companies within the
building.
Highway contract route
A mail route assigned to a private carrier on a contract basis. The post office sometimes assigns
contracts for sparsely populated rural areas.
Input file
Contains variable data used for input. It is typically a name-and-address file, but may contain any
type of data. The input file is described by the user. It may have any file attributes and may reside on
either disk, diskette, or tape.
Invalid ZIP Code File
Output file that contains addresses that have invalid ZIP Codes.
Job description
A set of characters that defines how the system handles a job.
Job queue
A waiting list. In this case, a list of the jobs waiting for processing.
Library
An object on disk that serves as a directory of other objects. A library groups related objects, and
enables you to find objects by name.
Leading zeros
Zeroes that are place-holders to the left of numbers that are right-aligned and smaller than the
specified field length.
Release 4.1.0
236
User’s Guide - Open Systems
Glossary
List codes
A generic term for codes placed next to records in a file. A list code might be used to sort records or
perform other operations that require codes to identify like records.
Match attempts
Number of tries the system made to match the input address.
Matching algorithm
Program logic that controls address matching.
Member
Different files within a library.
National character
One of the characters $, @, #, or _ (underscore).
Numeric character
Any one of the digits 0 through 9.
Packed data
Data that is in a packed decimal format.
Packed field
A field that contains data in packed decimal format.
Packed decimal format
Representation of a decimal value in which each byte within a field represents two numeric digits
except the rightmost byte, which contains one digit in bits 0 through 3 and the sign in bits 4 through
7. For all other bytes, bits 0 through 3 represent one digit; bits 4 through 7 represent one digit. For
example, the decimal value for +123 would be represented as 0001 0010 0011 1100 in binary
notation, or X'123C' in hexadecimal notation. Note that some computers use alternative
representations for packed decimal numbers.
Parameter
Data passed to or received from another program.
Record
A collection of related data or words, treated as a unit, such as one name, address, and telephone
number.
Record layout
Layout of a record, showing all the fields it contains along with each field's length, type, and position
in the record.
Record position
The position in a record where a field is located.
Record types
The Postal Service categorizes addresses and assigns each category a code called a record type.
For example a rural route is assigned a record type of “R.”
Return codes
Codes produced by the system that indicate matching success and either changes made or
discrepancies found in the input address during matching.
Rural route
A delivery route operated in communities lacking convenient postal facilities and maintained by area
residents.
Uncoded output file
Output file that contains processed records left uncoded with either ZIP + 4 or carrier route codes.
Release 4.1.0
237
User’s Guide - Open Systems
Glossary
ZIP Code
A 5-digit code identifying the post office or delivery station associated with an address.
ZIP + 4 Code
A 4-digit code added to a ZIP Code. The first two digits designate a sector that corresponds to a
portion of a zone, rural route, several city blocks, or a large building. A company on one floor of a
large office building can have its own ZIP + 4 Code.
Release 4.1.0
238
User’s Guide - Open Systems
Index
A
example 13
what is it all about? 12
Addressing conventions 12
Address-Match Execution Statistics Report
example 119
Administration Sign-on Screen (Interactive) 107
AE OUT parameter record
example 49
Alternate city name, defined 101
Alternate sequence code 189
AM OUT parameter record
example 52
Analysis of Matched Records Report
example 121
AP OUT parameter record
example 50
Apartment designator 13
Apartment number 13
Apartments at a House Range Screen
(Interactive) 100
Ascending/descending sequence 178
Automatically printed reports 129
Address-Match Execution Statistics 119
Control Totals 120, 128
Execution Log 121
Parameter Record Listing 121
AUXIL Parameter 208
AUXIL parameter record
Field-by-Field 208
Auxiliary File
building in NT 207
building in Unix 207
building in z/OS/VSE/IMS 207
Auxiliary File Build (C1AUXBLD) Reports 209
Auxiliary File Build Execution Log 210
Auxiliary File Build Report 210
Auxiliary File Reporting in the CODE-1 Plus
Matcher 210
Auxiliary File Reports 209
Accessing
interactive system 73
Accessing Line of Travel 178
Activating the Auxiliary File/Early Warning
System File Option 209
additional 13
ADDRDF parameter record
example 46
Address
dropped information 15
normalized 15
standardized 15
what is an address? 13
when no match is found 15
Address elements
apartment designator 13
apartment number 13
defined 13
house number 13
leading directional 13
rural route or highway contract numbers 13
rural route or highway contract route type 13
rural route, highway contract, or P.O. box
numbers 13
street name 13
suffix 13
trailing directional 13
Address Match Screen (Interactive) 84
Address matching function (interactive
environment)
Address Match Screen 84
Address Stack Screen 98
capabilities 66
Delivery Sequence Footnotes Screen 85
Dropped Information/Base Address Screen 86
example work session 76
Expanded Return Codes Screen 87
Geocoder Information Screen 87
Match Settings Screen 88
Multiple Elements Screen 89
Parsed Elements Screen 90
Return Codes Screen 91
Statistics Screen 96
Address Stack Screen 98
Address standardization 12
Release 4.1.0
B
Batch system
C1BM00 standard driver 20
C1BM00XL driver program (additional list
codes) 20
Building
239
User’s Guide - Open Systems
RDI file 200
Building Your Auxiliary File
in NT 207
in Unix 207
in z/OS/VSE/IMS 207
What is it?
UNIX 35
Windows 34
z/OS 36
Command field
in interactive system 68
commercial mail receiving agency 138
Concatenated commands
using in interactive system 82
CONTRL parameter record
example 47
CONTRL parameter record (for C1DBUNLD)
defined 212, 222
field-by-field 213, 222
Control Totals Report
example 120, 128
Correcting uncoded records
G1CPNBC user exit program 113
in interactive system 67, 77
interactive system 113
CR OUT parameter record
example 52
CS OUT parameter record
example 51
CS ZIP parameter record
example 46
C
C1AUXBLD Utility Program 207
C1BM00 driver program
batch system 20
C1BM00XL driver program
batch system (additional list codes) 20
C1DBRDI
RDI utility program
definition 200
C1DBUNLD database reduction program
defined 212, 221
headers and footers 213, 222
parameter records 212, 221
reports produced 216, 224
C1DBUNLD parameter records
CONTRL 212, 222
HEADER 213, 222
PAGESZ 214, 222
STATES 214, 223
UFT 216, 223
UHD 216, 224
C1PDR database reduction program
executing 219
IMS JCL 219, 227
UNIX shell scripts 219, 227
VSE JCL 219
Windows NT batch file 220, 228
z/OS JCL 219, 227
Callable subroutine
LTO10 callable subroutine 178
Calling Z4CHANGE
from your own driver 134
Carrier Route 178
CASS
certification 129
certifying your configurations 17
defined 16
Stage 1 tape 16
Stage 2 tape 16
CASS Form 3553
See USPS Form 3553 56
Cities in a State Screen (Interactive) 100
Cities in a ZIP Code Screen (Interactive) 101
City Information Screen (Interactive) 102
City name
alternate 101
short 101
City Type, defined 101
CMRA 138
CODE-1 Plus
database 15
using other Pitney Bowes products 20
CODE-1 Plus Database
Release 4.1.0
D
Database
for CODE-1 Plus 15
for Z4CHANGE 132
Database expiration 31
and interactive matcher 67
Database inquiry function (interactive system)
Apartments at a House Range Screen 100
capabilities 66
Cities in a State Screen 100
Cities in a ZIP Code Screen 101
City Information Screen 102
defined 27
Firms on a Street Screen 102
Houses on a Street Screen 103
in interactive system 68
information displayed 66
Streets in a City Screen 104
Defining
files 43
input file 23
input record layout 45
output 47
output file 24
report headers and footers 55
reports 54
reports parameter record list) 25
Delivery Point Validation
Getting started with 139
License Management 139
Delivery Point Validation database
installing
240
User’s Guide - Open Systems
MVS/VSE/IMS 142, 170
Unix 141, 169
Windows NT 140–141, 154, 168
z/OS/VSE/IMS 156
verify the install 141, 161
Delivery Point Validation processing
expiration of 145
Delivery Sequence Footnotes Screen
(Interactive) 85
Domestic Mail Manual 138, 178
Domestic Mail Manual (DMM) 16
DPV
Getting started with 139
License Management 139
DPV database
installing
Unix 141, 169
Windows NT 140–141, 154, 168
z/OS/VSE/IMS 142, 156, 170
verify the install 141, 161
DPV errors
interactive 84
DPV Large Memory Module 202
DPV message
interactive 84
DPV Parameters and Return Codes 143
DPV processing
expiration of 145
improving speed of 202
DPV Processing Summary Report 144
DPV010L 202
DPVIN Parameter 143, 202
DPVOUT Parameter 143
Dropped Information/Base Address Screen
(Interactive) 86
False/Positive Table
reporting a match 146
Field 68
File names 22
for database reduction (C1PDR) 217
for running a job 57
FILEDT parameter record
field-by-field 202
FILESL parameter 213
Firms on a Street Screen (Interactive) 102
First Interactive Customization Screen
(Interactive) 108
FOOTER TEXT field (UFTxx) 216, 223
Footers
example 42
Function keys
in interactive system 68
G
G1C1AUX 209
G1CPBNC user exit program
correcting uncoded records (interactive system)
113
for correcting uncoded records 116
G1CPFDF 112
G1DBLOAD
FILESL parameter 213
Generating reports 41
for Z4CHANGE processing 135
Geocoder Information Screen (Interactive) 87
Geographic coding information
defining 25
Geographic Coding Plus/System 66, 73, 76
Geographic Coding System Interface
(Interactive) 104
GeoTAX Key 107
GeoTAX Key Return Code 107
Getting Started with Delivery Point Validation
139
Guam
information about database reduction 214
E
Early Warning System
what is it? 206
Enhanced Carrier Route 138, 178
EWS
what is it? 206
Executable programs
overview 30
Executing Line of Travel 178
Execution Log
example 121
Exit routine
LTO60 exit routine 178
Expanded Return Codes Screen (Interactive) 87
Expired database 31
bypassing 31
using with interactive system 67
EXTADDR2, short description 29
H
Handbooks, USPS
Domestic Mail Manual (DMM) 16
HEADER parameter record (for C1DBUNLD)
defined 213, 222
field-by-field 213, 222
HEADER TEXT field (UHDxx) 216, 224
Headers
example 42
Hexadecimal sequence code 189
Highway contract or rural route
numbers 13
type 13
House number 13
Houses on a Street Screen (Interactive) 103
F
False/Positive
seed record
report 144
Release 4.1.0
241
User’s Guide - Open Systems
I
Statistics Screen 96
Streets in a City Screen 104
using concatenated commands 82
using with expired database 67
Invoking Line of Travel 178
IMS JCL
for C1PDR (database reduction) 219, 227
for running a job 58
Input file
defining 23
example 39
Installing
DPV database
L
LACS/Link Option
overview 12
LACS/Link processing
processing
described 152
LACSLink
processing requirements 153
using batch processing 156
using Interactive processing 158
LACSLink database
installing
Unix 155
Leading directional 13
License Management
DPV processing 139
LINE NUMBER field
(UFTxx) 216, 223
(UHDxx) 216, 224
Line of Travel
accessing 178
executing 178
LTO10 callable subroutine 178
LTO60 exit routine 179
output records 178
Line of Travel code
LOT code 178
Line of Travel number 178, 189
Line of Travel sequence code 178
LINE SIDE field
(UFTxx) 216, 223
(UHDxx) 216, 224
LINES-PER-PAGE field (PAGESZ) 214, 222
List codes
processing up to 10,000 list codes (C1BM00XL
driver program) 21
Looseness/tightness settings
in interactive matching 66
LOT code 138, 178
defined 178
LOT coded records
alternate sequence code 180
hexadecimal sequence code 180
Sorting 179
z/OS/VSE/IMS 170
Unix 141, 169
verify the install 141, 161
Windows NT 140–141, 154, 168
z/OS/VSE/IMS 142, 156
LACSLink database
Unix 155
Interactive Screen Reference
GeoTAX Key 107
Interactive site customization
Administration Sign-on screen 107
First Interactive Customization screen 108
Second Interactive Customization screen 110
Interactive system
accessing 73
Address Match Screen 84
address matching 27, 66, 69
Address Stack Screen 98
Administration Sign-on Screen 107
Apartments at a House Range Screen 100
Cities in a State Screen 100
Cities in a ZIP Code Screen 101
City Information Screen 102
Command field 68
correcting uncoded records 67, 77
database inquiry 27, 66, 68
Delivery Sequence Footnotes Screen 85
Dropped Information/Base Address Screen 86
example work session 73
Expanded Return Codes Screen 87
Firms on a Street Screen 102
First Interactive Customization Screen 108
function keys 68
Geocoder Information Screen 87
Houses on a Street Screen 103
introduction to 66
match results 68
Match Settings Screen 88
matching an address 74, 76
Multiple Elements Screen 89
online help 69
overview picture 28
Parsed Elements Screen 90
querying the database 75
Return Codes Screen 91
screen components 68
Second Interactive Customization Screen 110
site customization file (G1CPFDF) 112
Release 4.1.0
M
Match
reporting a seed record 146
Match results
in interactive system 68
Match Settings Screen (Interactive) 88
Matching an address 74, 76
Moving to a line
242
User’s Guide - Open Systems
in interactive system 71
multiple conditions 138
Multiple Elements Screen (Interactive) 89
defining 26
Processing Summary by 3-digit ZIP Code Report
example 127
Processing Summary by List Code Report
example 127
Processing Summary by State Report
example 127
Processing Summary Report
DPV 144
Program parameters
for correcting uncoded records 115
N
NAIC 12
National Address Information Center 12
National Deliverability Index (NDI) Report
example 128
NDI
See National Delivery Index (NDI) Report 128
Normalized address
description 15
Q
Quality addressing 12
Querying the database
in interactive system 72, 75
O
Online help
interactive system 69
Open/Read failure
DPV 145
Output file
defining 24
reviewing sample jobs 61
Output records 178
Overview picture
interactive system 28
R
RDI
definition of 200
RDI processing
building the RDI File step-by-step 200
building your RDI file 200
building your RDI file in
z/OS/VSE/IMS 201
building your RDI file in Windows 201
Specifying location for RDI flag 202
RDI utility program
C1DBRDI 200
Reducing the database
overview 212, 221
reports produced 216, 224
REPORT OR LOG CODE field (PAGESZ) 214, 222
Reporting a match
seed record 146
Reports
Address-Match Execution Statistics 119
Analysis of Matched Records 121
CASS Form 3553 56
Control Totals 120, 128
Control Totals Report 120, 128
defining 25
example headers and footers 42
Execution Log 121
for database reduction 216, 224
generated for sample job 41
National Deliverability Index (NDI) Report 128
Parameter Record Listing 121
printed automatically 129
printing 118
Processing Summary by 3-digit ZIP 127
Processing Summary by List Code 127
Processing Summary by State 127
required 118
reviewing sample jobs 61
USPS Form 3553 16, 129
Residential Delivery File processing
building the RDI file step-by-step 200
building your RDI file 200
P
P9IAUX 209
PAGESZ parameter record (for C1DBUNLD)
defined 214, 222
field-by-field 214, 222
LINES-PER-PAGE 214, 222
REPORT OR LOG CODE 214, 222
Parameter Record Listing
example 121
Parsed Elements Screen (Interactive) 90
Performance, improving 42
PFKEYS (Interactive)
Definition of 111
platform-specific
building your RDI file 201
PMB 138
PMBs
standardizing 14
Postal Addressing Standards 12
Postal Form 3553 129
Posting information
for sample job 40
Preferred city name, defined 101
private mail boxes 138
Private Mailboxes
normalizing 14
standardizing 14
Probable correctness
and the Analysis of Matched Records report 121
Processing Requirements
LACSLink 153
Processing requirements
Release 4.1.0
243
User’s Guide - Open Systems
building your RDI file in
z/OS/VSE/IMS 201
building your RDI file in Windows 201
C1DBRDI 200
definition of 200
Return Codes Screen (Interactive) 91
Running a job
IMS JCL 58
UNIX shell scripts 58
Windows NT batch file 58
z/OS JCL 58
Rural route or highway contract numbers 13
Rural route or highway contract route type 13
interactive 91
what does it look like?
interactive 91
Seed Record
reporting a match 146
Seed records
definition 145
Short city name, defined 101
Site customization file (G1CPFDF) 112
recovering 112
Sorting LOT-coded records 179, 189
Speed of
improving DPV processing 202
Standardization
address
what is it all about? 12
Standardized address
description 15
State abbreviations
list 214
STATES parameter record (for C1DBUNLD)
defined 214, 223
field-by-field 214, 223
Statistics Screen 96
Street name 13
Streets in a City Screen (Interactive) 104
Suffix 13
SuiteLink
defined 166
eligibility 167
input and output examples 174
mainframe DD names 174
reporting 174
return codes 174
using batch processing 143, 170
using Interactive processing 143, 158, 172
SuiteLink Option
overview 12
S
SA OUT parameter record
example 49
Sample job
input file layout 39
output record posting 40
reading the output 61
review Step 1 45
review Step 2 47
review Step 3 54
review Step 4 54
review Step 5 56
steps to follow 42
Screen components
for interactive system 68
Screens (Batch)
Geographic Coding Plus/System 66, 73, 76
Screens (Interactive)
Address Match Screen 84
Address Stack Screen 98
Administrative Sign-on Screen 107
Apartments at a House Range Screen 100
Cities in a State Screen 100
Cities in a ZIP Code Screen 101
City Information Screen 102
correcting uncoded records 113
Delivery Sequence Footnotes Screen 85
Dropped Information/Base Address Screen 86
Expanded Return Codes Screen 87
Firms on a Street Screen 102
First Interactive Customization Screen 108
Geocoder Information Screen 87
Geographic Coding System Interface 104
Houses on a Street Screen 103
Match Settings Screen 88
Multiple Elements Screen 89
Parsed Elements Screen 90
program parameters for correcting records 115
Return Codes Screen 91
Second Interactive Customization Screen 110
Statistics Screen 96
Streets in a City Screen 104
Second Interactive Customization Screen
(Interactive) 110
Seed ID
Release 4.1.0
T
Tightness/looseness settings
in interactive matching 66
Trailing directional 13
U
UAA 138
UFTxx parameter record (for C1DBUNLD)
defined 216, 223
field-by-field 216
FOOTER TEXT 216, 223
LINE NUMBER 216, 223
LINE SIDE 216, 223
UHDxx parameter record (for C1DBUNLD)
defined 216, 224
field-by-field 216
HEADER TEXT 216, 224
LINE NUMBER 216, 224
LINE SIDE 216, 224
Uncoded records
244
User’s Guide - Open Systems
correcting in Interactive environment 113
undeliverable-as-addressed 138
Unique Zip and Small Town 138
UNIX platform
getting started on 35
UNIX shell script
for C1PDR (database reduction) 219, 227
for running a job 58
for Z4CHANGE (C1P430) reports 135
UR command
for correcting uncoded records 114
User exit routines
for correcting uncoded records Interactive 116
Using G1DBLOAD
FILESL parameter 213
USPS
RDI processing 200
USPS Form 3553 16
explained with example 129
review example jobs 56
USPS Publication 28 12
USPS rules and exception
for Z4CHANGE processing 132
USPS-preferred
city name, defined 101
UW command
for correcting uncoded records 114
defined 132
parameter records 133
reports generated 135
using 133
USPS rules and exception 132
Z4CHANGE reports
UNIX environment 135
Windows NT environment 136
Z5 OUT parameter record
example 51
V
VSE JCL
for C1PDR (database reduction) 219
W
What is Delivery Point Validation? 138
What is EWS? 206
What is Line of Travel? 178
What is Residential Delivery File processing?
200
Why Use Line of Travel? 178
Windows NT batch file
for C1PDR (database reduction) 220, 228
for running a job 58
for Z4CHANGE (C1P430) reports 136
Windows platform
getting started on 34
Z
z/OS JCL
for C1PDR (database reduction) 219, 227
for running a job 58
z/OS platform
getting started on 36
Z4 OUT parameter record
example 51
Z4CHANGE processing
activating 132
calling from your own driver 134
database requirements 132
Release 4.1.0
245
User’s Guide - Open Systems
Release 4.1.0
246
User’s Guide - Open Systems
Feedback
Document Title:
CODE-1 Plus 4.1.0 User's Guide for Open Systems
Document Date:
May 2016
Software Version: 4.1.0
Comment regarding page: 1
Contact Preferences
May we contact you if we have questions about your comments?
Yes
No
Contact Information
Name:
Email:
Phone:
Best time to contact: Any time
Comments
Enter you comments here:
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement