Working with CODE-1 Plus Guide - Support

Working with CODE-1 Plus Guide - Support
CODE-1 Plus™
Release 4.0.0 - March 2015
Working with CODE-1 Plus™ Guide
for Linux, Unix, Windows, and z/OS
© 2015 Pitney Bowes Software, Inc. All rights reserved. MapInfo, 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 Software 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.
Pitney Bowes Inc.
Documentation Team
pbbidocs@pb.com
One Global View
Troy, New York 12180
www.pb.com/software
www.g1.com/support
software.support@pb.com
Support: +1 (800) 367-6950
TABLE OF CONTENTS
CHAPTER 1. WORKING WITH CODE-1 PLUS IN DISPATCHER4
Configuring All Fields on the CODE-1 Plus Primary Window. . . . . . .
Standardized Address Field Selections . . . . . . . . . . . . . . . . . . . . .
Standardized Firm Field Selection . . . . . . . . . . . . . . . . . . . . . . . . .
City and State Field Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZIP, ZIP+4, DPBC, CR-RT Field Selections. . . . . . . . . . . . . . . . . . .
Address Elements Field Selections . . . . . . . . . . . . . . . . . . . . . . . .
Normalized Address Lines Field Selections . . . . . . . . . . . . . . . . .
Other Match Results Field Selections . . . . . . . . . . . . . . . . . . . . . .
Line of Travel Field Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delivery Point Validation Field Selections . . . . . . . . . . . . . . . . . . .
Configuring the Options on the Records Menu . . . . . . . . . . . . . . . . . .
Address... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZIP Codes... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Masterfile Vintage Date... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Geographic Input... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rearrange Before Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rearrange After Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Options on the Options Menu . . . . . . . . . . . . . . . . . . .
Limit Records... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exit Routine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Confirm Without Matching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maximum Correctness Scores.... . . . . . . . . . . . . . . . . . . . . . . . . . .
CASS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define Input Client Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define LACS Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define STELNK Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Options on the Report Menu. . . . . . . . . . . . . . . . . . . .
Choose Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Headers/Footers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List/Mailer Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dispatcher4 Field Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input File Field Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output Layout File Definition Field Labels. . . . . . . . . . . . . . . . . . .
Output File Definition Field Labels . . . . . . . . . . . . . . . . . . . . . . . . .
Output File Definition Field Labels for GeoCoding Plus . . . . . . . .
Working With CODE-1 Plus
13
13
16
17
21
27
28
30
30
31
35
35
37
38
39
40
42
43
46
46
49
50
52
53
58
59
60
61
63
65
66
66
70
71
73
73
75
81
84
3
CHAPTER 2. PARAMETER REFERENCE
ADDRDF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
AE OUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
AM OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
AM2OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
AP OUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Example of Storing Additional Input Data/Unmatched
Data - Fixed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Example of Storing Additional Input Data/Unmatched
Data - Concatenated Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
AUXIL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
BYPEXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
CASSA1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
CASSA4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
CASSA7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
CHCKPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
z/OS Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
CONFRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
CONTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
CR OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
CS OUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
CS ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
DPVIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
DPVOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
EXITOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
FILEDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Limiting Processing With FILEDF . . . . . . . . . . . . . . . . . . . . . . . . 161
FIRMNM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
G9 OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
G9XOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
G9ZIP9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
HEADER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
LACS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
L CODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
LISTID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
LISTNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
LOTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
MAILER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
MOVE I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
MOVE O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
NTHSEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Performing Cross-Sectional Sampling . . . . . . . . . . . . . . . . . . . . 187
Including/Excluding Nth Records . . . . . . . . . . . . . . . . . . . . . . . . 188
4
Software Release 4.0.0/March 2015
PAGESZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PGMNAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SA OUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SA2OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEQCHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STELNK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TESTIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UFTxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UHDxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Z4 OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Z5 OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
189
190
192
197
206
208
210
213
214
215
216
221
CHAPTER 3. INTERACTIVE SCREEN REFERENCE
The Command Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Concatenated Commands. . . . . . . . . . . . . . . . . . . . . . . . . .
Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Screens that Support Address Matching . . . . . . . . . . . . . . . . . . . . . .
Address Match Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delivery Sequence Footnotes Screen. . . . . . . . . . . . . . . . . . . . . .
Miscellaneous Information/Base Address Screen . . . . . . . . . . .
Expanded Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Geographic Coding Information . . . . . . . . . . . . . . . . . . . . . . . . . .
Match Settings Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Elements Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parsed Elements Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Return Codes Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistics Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Address Stack Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Screens that Support Database Inquiry . . . . . . . . . . . . . . . . . . . . . . .
Apartments at a House Range . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cities in a State Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cities in a ZIP Code Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
City Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Firms in a House Range Screen . . . . . . . . . . . . . . . . . . . . . . . . . .
Houses on a Street Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Streets in a City or Streets in a ZIP Code Screen . . . . . . . . . . . .
Geographic Coding Plus Interface . . . . . . . . . . . . . . . . . . . . . . . .
Screens that Support Site Customization . . . . . . . . . . . . . . . . . . . . .
Administration Sign-on Screen. . . . . . . . . . . . . . . . . . . . . . . . . . .
Interactive Customization Screens . . . . . . . . . . . . . . . . . . . . . . . .
Database Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customization File Administration . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Backup and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Repair, Re-Initialization, and Password Display . . . . . . . . .
Batch Uncoded Records Interface (G1CPBNC) . . . . . . . . . . . . . . . . .
How it Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UR COMMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UW COMMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
227
232
232
233
233
236
239
242
244
246
249
252
254
262
266
270
270
273
276
278
281
283
286
288
294
294
296
304
305
305
305
307
307
308
309
Working With CODE-1 Plus
5
Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Description of Supplied Sample G1CPBNC . . . . . . . . . . . . . . . . . 311
6
CHAPTER 4. USING THE Z4CHANGE OPTION
What is the Z4CHANGE Option? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Z4CHANGE Option Database . . . . . . . . . . . . . . . . . . . . . . . . .
Rules for Using the Z4CHANGE Option . . . . . . . . . . . . . . . . . . . .
Activating the Z4CHANGE Option, C1P430 . . . . . . . . . . . . . . . . . .
Using Z4CHANGE Option Processing . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling C1P430 From Your Own Driver. . . . . . . . . . . . . . . . . . . . . . . .
Generating Reports for Z4CHANGE Processing . . . . . . . . . . . . . . . .
Unix Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
314
314
314
315
315
315
317
318
319
319
CHAPTER 5. LINE OF TRAVEL (LTO10)
What is Line of Travel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why Use Line of Travel?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing Line of Travel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Started with Line of Travel . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sorting Your LOT Coded Records . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling the LTO10 Subroutine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input Area — Parameter 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output Area — Parameter 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COBOL Calling Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Calling Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Line of Travel Exit Routine (LTO60) . . . . . . . . . . . . . . . . . . . . . . .
EXITOP Parameter for the LTO60 Exit Routine . . . . . . . . . . . . . . . . .
Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line of Travel Exit Routine for Unix . . . . . . . . . . . . . . . . . . . . . . . . . .
Line of Travel Exit Routine for Windows. . . . . . . . . . . . . . . . . . . . . . .
Control Totals Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
322
322
323
323
324
325
326
327
328
329
329
330
330
332
333
333
334
CHAPTER 6. USING DELIVERY POINT VALIDATION
What is Delivery Point Validation?. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Matches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Started with Delivery Point Validation . . . . . . . . . . . . . . . . . .
Installing the DPV Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating Delivery Point Validation . . . . . . . . . . . . . . . . . . . . . . .
Delivery Point Validation and Seed Records . . . . . . . . . . . . . . . .
Residential Delivery File Processing . . . . . . . . . . . . . . . . . . . . . . . . .
What is Residential Delivery File Processing? . . . . . . . . . . . . . .
Building the Residential Delivery File in CODE-1 Plus . . . . . . . .
FILEDT Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating the RDI Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DPV Parameters and Return Codes . . . . . . . . . . . . . . . . . . . . . .
DPVIN Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DPVOUT Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
339
339
341
341
346
348
355
355
355
358
359
359
359
360
Software Release 4.0.0/March 2015
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Expiration of DPV Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open/Read Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
“Seed Records” and Stop DPV Processing . . . . . . . . . . . . . . . . .
Software Incompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DPV File Load or Location Definition . . . . . . . . . . . . . . . . . . . . . .
DPV by List Code Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DPV Processing Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . .
Residential Delivery File Build Report . . . . . . . . . . . . . . . . . . . . . . . .
Residential Delivery File Build Execution Log . . . . . . . . . . . . . . . . . .
361
361
361
362
362
363
363
363
364
364
CHAPTER 7. AUXILIARY FILE PROCESSING
What is the Early Warning System? . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Processing and EWS . . . . . . . . . . . . . . . . . . . . . . . .
Building the Auxiliary File with the Early Warning System . . . . . . .
C1AUXBLD Utility Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AUXIL Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating the Auxiliary File/Early Warning System File. . . . . . . . . .
Auxiliary File Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Build (C1AUXBLD) Reports. . . . . . . . . . . . . . . . . . .
Auxiliary File Build Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Build Execution Log . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Reporting in the CODE-1 Plus Matcher. . . . . . . . . . . .
366
366
367
367
369
370
371
372
372
372
372
373
CHAPTER 8. USING G1G001
What is G1G001? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using G1G001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input File and Header/Footer Parameters. . . . . . . . . . . . . . . . . . . . .
FILEDF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HEADER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HEADxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UFTxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UHDxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Report Layout and Content Parameters. . . . . . . . . . . . . . . . . . . . . . .
CONTRL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONSTANT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MOVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGESZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TESTIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNPK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record Selection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Control Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Control Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IMS JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
376
376
377
377
379
380
381
382
383
383
385
386
388
389
390
391
392
392
393
394
394
394
394
Working With CODE-1 Plus
7
z/OS JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Unix Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
CHAPTER 9. CALLING CODE-1 PLUS MATCHING, ANALYZER, AND CALLABLE BATCH DRIVER MODULES
CODE-1 Plus Matching Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
What is C1MATCHx?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
What is C1ANZADR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
What is C1BMCBD? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
What is EXTADDR2? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Call Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Calling CODE-1 Plus on z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Calling C1MATCHx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Casing Your Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Format of Cased Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Special Casing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
COBOL Call to Batch Version of C1MATCHx . . . . . . . . . . . . . . . . 404
The Input Call Area (P9IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
The Output Results Call Area (P9OUT) . . . . . . . . . . . . . . . . . . . . . . . . 414
Output Audit Call Area (P9AUDIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Unmatched Data Call Area (P9INTRF) . . . . . . . . . . . . . . . . . . . . . . . . 444
CICS Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
IMS Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Calling CODE-1 Plus from Unix, Windows, or VMS . . . . . . . . . . . . . . 454
Calling C1ANZADR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
ANALYSIS-PARAMETERS Call Area . . . . . . . . . . . . . . . . . . . . . . . 455
ANALYSIS-NORMALIZATION Call Area . . . . . . . . . . . . . . . . . . . . 456
Calling C1BMCBD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Calling C1BMCBD in IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Calling the Address Line Extraction Module (EXTADDR2) . . . . . . . . 462
Calling EXTADDR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Supplied Copybooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
CHAPTER 10. CALLING C1PRPT, C1CTYLKX, OR G1CPLKX
What is C1PRPT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling C1PRPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The C1PRPT Call Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is C1CTYLKx?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZIP Code Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
City and State Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZIP Code and City/State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling C1CTYLKx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling from an IMS Application . . . . . . . . . . . . . . . . . . . . . . . . . .
The C1CTYLKx Call Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is G1CPLKx? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling G1CPLKC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G1CPLK-USER-REQUEST-AREA . . . . . . . . . . . . . . . . . . . . . . . . .
G1CPLK-USER-RESULT-AREA . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
468
469
471
481
482
482
482
483
483
484
485
489
489
490
494
Software Release 4.0.0/March 2015
G1CPLK-IPC-AREAS-LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Calling G1CPLKB from an IMS Application . . . . . . . . . . . . . . . . . . . . 497
CHAPTER 11. USING LACSLINK
What is LACSLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What are the Benefits of LACSLink?. . . . . . . . . . . . . . . . . . . . . . .
Who is Eligible to Use LACSLink?. . . . . . . . . . . . . . . . . . . . . . . . .
How Does LACSLink Work?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the LACSLink Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LACSLink Processing Requirements . . . . . . . . . . . . . . . . . . . . . .
How Do I Install the LACSLink Option? . . . . . . . . . . . . . . . . . . . .
How Do I Install the LACS Database? . . . . . . . . . . . . . . . . . . . . . .
How Do I Activate LACSLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LACSLink Processing Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LACSLink Information on USPS Form 3553. . . . . . . . . . . . . . . . .
Seed Record Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What If My Mailing Generates a Seed Violation? . . . . . . . . . . . . .
500
500
501
501
502
502
502
503
507
515
517
517
517
518
CHAPTER 12. USING SUITELINK
What is SuiteLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What are the Benefits of SuiteLink? . . . . . . . . . . . . . . . . . . . . . . .
Who is Eligible to Use SuiteLink? . . . . . . . . . . . . . . . . . . . . . . . . .
How Does SuiteLink Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the SuiteLink Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How do I Install the SuiteLink Option? . . . . . . . . . . . . . . . . . . . . .
How do I Install the SuiteLink Database?. . . . . . . . . . . . . . . . . . .
How Do I Activate SuiteLink?. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DD Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SuiteLink Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input and Output Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SuiteLink Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
522
522
523
523
524
524
524
529
536
536
537
537
INDEX
Working With CODE-1 Plus
9
10
Software Release 4.0.0/March 2015
CHAPTER 1
Working With CODE-1 Plus in Dispatcher4
This chapter contains detailed information on all the options available in
CODE-1 Plus when using Dispatcher4.
Configuring All Fields on the CODE-1 Plus Primary Window. . . . . . .
Standardized Address Field Selections . . . . . . . . . . . . . . . . . . . . .
Standardized Firm Field Selection . . . . . . . . . . . . . . . . . . . . . . . . .
City and State Field Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZIP, ZIP+4, DPBC, CR-RT Field Selections. . . . . . . . . . . . . . . . . . .
Address Elements Field Selections . . . . . . . . . . . . . . . . . . . . . . . .
Normalized Address Lines Field Selections . . . . . . . . . . . . . . . . .
Other Match Results Field Selections . . . . . . . . . . . . . . . . . . . . . .
Line of Travel Field Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delivery Point Validation Field Selections . . . . . . . . . . . . . . . . . . .
Configuring the Options on the Records Menu . . . . . . . . . . . . . . . . . .
Address... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZIP Codes... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Masterfile Vintage Date... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Geographic Input... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rearrange Before Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rearrange After Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Options on the Options Menu . . . . . . . . . . . . . . . . . . .
Limit Records... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exit Routine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Confirm Without Matching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maximum Correctness Scores.... . . . . . . . . . . . . . . . . . . . . . . . . . .
CASS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define Input Client Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define LACS Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Define STELNK Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Options on the Report Menu. . . . . . . . . . . . . . . . . . . .
Choose Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Headers/Footers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List/Mailer Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dispatcher4 Field Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input File Field Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output Layout File Definition Field Labels. . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
13
13
16
17
21
27
28
30
30
31
35
35
37
38
39
40
42
43
46
46
49
50
52
53
58
59
60
61
63
65
66
66
70
71
73
73
75
11
1
Working With CODE-1 Plus in Dispatcher4
Output File Definition Field Labels . . . . . . . . . . . . . . . . . . . . . . . . . 81
Output File Definition Field Labels for GeoCoding Plus . . . . . . . . 84
12
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
Configuring All Fields on the CODE-1 Plus Primary Window
For an actual CODE-1 Plus job using Dispatcher4, you do not have to add all the
fields listed in the Available Fields section on the CODE-1 Plus primary window.
Additionally, you do not have to configure every output option available within these
fields. If you do not configure an output option, CODE-1 Plus simply uses the default
value. For the purposes of this chapter, however, we will access every Add Field dialog
box that has output options and describe them for you.
Standardized Address Field Selections
The selections under the Standardized Address category on the CODE-1 Plus primary
window for which you can change storage options are:
–
Address With Apartment
–
Address Without Apartment
–
Apartment/PMB Number
–
Private Mail Box
When you select one of these, an Add Field dialog box displays.
Working With CODE-1 Plus
13
1
Working With CODE-1 Plus in Dispatcher4
A description for each storage option available with this dialog box follows.
Table 1: Storage Options for Standardized Address Fields (Part 1 of 3)
This option...
Overwrite Input
Address
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus whether or not to overwrite the
input address, using the following selections.
SA OUT
• Yes — Replace the input address with the
standardized address in your input file:
• No — Do not replace the input address with the
standardized address in your input file.
Return Base if Alias
Matched
Tells CODE-1 Plus what to do when an alias is
encountered in your input file, using the following
selections:
SA OUT
• Yes — When a street name differs from the input
address, match the alias with the base when
possible, and the base will be returned.
• No — Do not match the alias with the base.
Store Input
Address When
Address With Apt.
Not Stored
Tells CODE-1 Plus what to do when the
standardized address with apartment is too long,
using the following selections:
SA OUT
• Yes — When the standardized address with
apartment is too long, store a portion of the input
address.
• No — Do not store a portion of the input address.
Store Address
Without Apt. Only If
With Apt. Not
Stored
Tells CODE-1 Plus what to do with the standardized
address without the apartment number, using the
following selections:
SA OUT
• Yes — Store the standardized address without
the apartment number.
• No — Do not store the standardized address
without the apartment number.
Store Even If
Information
Dropped
Tells CODE-1 Plus what to do with information that
does not appear to be address data, using the
following selections:
SAOUT
• Yes — Reject any information that does not
appear to be address data and store the updated
address.
• No — Do not store the updated address.
14
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
Table 1: Storage Options for Standardized Address Fields (Part 2 of 3)
This option...
Store Even If
Multiple Address
Matches
Performs this function...
GRAYED OUT OPTION. Tells CODE-1 Plus what to
store when multiple address matches are found,
using the following selections:
And maps to this
parameter...
SA OUT
Box indicating that the standardized address should
be stored when multiple address matches were
found.
• Yes — Yes, store the standardized address when
multiple addresses are found.
• No — No, do not store the standardized address
when multiple addresses are found.
Store Even If
Multiple ZIP Code
Matches
GRAYED OUT OPTION. Tells CODE-1 Plus what to
store when multiple ZIP Code matches are found,
using the following selections:
SA OUT
Box indicating that the standardized address should
be stored when multiple ZIP Code matches were
found.
• Yes — Yes, store the standardized address when
multiple ZIP Code matches are found.
• No — No, do not store the standardized address
when multiple ZIP Code matches are found.
When Address With
Apartment/PMB
Not Stored, Store
Tells CODE-1 Plus what to store when the address
with apartment/PMB is not stored, using the
following selections:
SA OUT
• PMB Number — Store PMB number when unable
to store in primary address line due to
truncation.
• Apartment — Store the apartment information
anyway.
• Nothing — Do not store apartment information if
it is successfully stored in the standardized
address with apartment field.
Maximum Address
Correction for
Storage
Defines the level of correctness that must be
achieved to store the standardized address, based
on street address. Enter a number from 0 to 9, with
0 being the best match.
SA OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
Maximum Overall
Correctness for
Storage
Defines the level of correctness that must be
achieved to store the standardized address, based
on street address and firm name. Enter a number
from 0 to 9, with 0 being the best match.
SA OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
Working With CODE-1 Plus
15
1
Working With CODE-1 Plus in Dispatcher4
Table 1: Storage Options for Standardized Address Fields (Part 3 of 3)
This option...
When the
Standardized
Address is Not
Stored
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus what to store if, for any of the
reasons specified earlier, the standardized address
is not being stored, using the following selections:
SA OUT
• Blank — Store blanks.
• Nothing — Store nothing.
Preferred Alias
Processing
Indicates if preferred alias processing should be
performed:
• Y — Perform preferred alias processing.
• N — Do not perform preferred alias processing.
(default)
NOTE: Selecting No will generate a
non-CASS-certified configuration. No PS FORM
3553 will be generated.
Abbreviated Alias
Processing
Indicates if abbreviated alias processing should be
performed:
• Y — Perform abbreviated alias processing.
• N — Do not perform abbreviated alias
processing. (default)
Standardized Firm Field Selection
The selection under the Standardized Firm category on the CODE-1 Plus primary
window to which you can make storage options changes is:
–
16
Standardized Firm Name.
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
When you select this option, an Add Field dialog box will appear. A description for
each storage option available with this dialog box follows.
Table 2: Storage Options for Standardized Firm Name
This option...
When Standardized
Firm Name Not
Stored, Store
Performs this function...
Tells CODE-1 Plus whether what to store if the
standardized firm name is not stored, using the
following selections.
And maps to this
parameter...
FIRMNM
Input Firm Name — Store the input firm name.
Blanks — Store blanks.
Nothing — Store nothing.
NOTE: USPS CASS regulations require SuiteLink
processing for CASS certification and to generate
the USPS Form 3553 (USPS CASS Summary
Report). The FIRMNM parameter is required when
you perform SuiteLink processing.
City and State Field Selections
The selections under the City and State category on the CODE-1 Plus primary
window to which you can make storage options changes are:
These selections allow you to set up positions and lengths on the output record for
the following information:
•
City
Working With CODE-1 Plus
17
1
Working With CODE-1 Plus in Dispatcher4
•
State
When you select one of these, an Add Field dialog box will appear. A description for
each storage option available with this dialog box follows.
Table 3: Storage Options for City and State Fields (Part 1 of 3)
This option...
Format of
Standardized City/
State Line
And maps to this
parameter...
Performs this function...
Describes the format of the standardized city/state
line, using the following selections:
CS OUT
• City, State, ZIP+4 — Indicates that all of these
elements are located in your standardized city/
state line.
• City, State, ZIP — Indicates that all of these
elements are located in your standardized city/
state line.
• City — Indicates that only the city is located in
your standardized city/state line.
Maximum Address
Correctness for
Storage
Defines the level of correctness that must be
achieved to store the standardized address, based
on street address. Enter a number from 0 to 9, with
0 being the best match.
CS OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
Maximum Overall
Correctness for
Storage
Defines the level of correctness that must be
achieved to store the standardized address, based
on street address and firm name. Enter a number
from 0 to 9, with 0 being the best match.
CS OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
When City/State is
Not Stored, Store
Tells CODE-1 Plus what to store when the
standardized city/state line was not stored, using
the following selections:
CS OUT
Blanks — Store blanks.
Nothing — Store nothing.
Overwrite Input City
and State
18
GRAYED OUT OPTION. Tells CODE-1 Plus to store
the standardized city/state line in the same location
as the input city/state line.
CS OUT
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
Table 3: Storage Options for City and State Fields (Part 2 of 3)
This option...
If No Address
Match, Store...
Performs this function...
Tells CODE-1 Plus whether or not to store the input
city when no address match was found, using the
following options:
And maps to this
parameter...
CS OUT
• Info From Disposition — Store the disposition
indicator.
• Input City — Store the input city.
• City of Valid Input ZIP — Store the primary city for
the valid input ZIP Code. If you select this option,
CODE-1 Plus does not generate a USPS Form
3553 (CASS Summary Report).
If No Match, Keep
Input State
Tells CODE-1 Plus whether or not to store the input
state when no state match was found, using the
following selections:
CS OUT
• Yes — Store the input city.
• No — Do not store the input city.
If No City Match,
Store Default City
Tells CODE-1 Plus whether or not to store the
default city when no city name match was found,
using the following selections:
CS OUT
• Yes — Store the default city.
• No — Do not store the default city.
Store Even If
Information is
Dropped
Tells CODE-1 Plus whether or not you want to reject
any information that does not appear to be address
data and then to store the updated address, using
the following selections:
CS OUT
• Yes — Yes, reject any information that does not
appear to be address data and store the updated
address.
• No — Do not reject any information that does not
appear to be address data and store the updated
address.
Store Even If
Multiple ZIP+4
Matches
GRAYED OUT OPTION. Tells CODE-1 Plus whether
or not to store the standardized city/state line when
multiple ZIP+4 Code matches were found, using the
following selections:
CS OUT
• Yes — Store the standardized city/state line.
• No — Do not store the standardized city/state
line.
Store Even If
Multiple ZIP Code
Matches
GRAYED OUT OPTION. Tells CODE-1 Plus whether
or not to store the standardized city/state line when
multiple ZIP Code matches were found, using the
following selections:
CS OUT
• Yes — Store the standardized city/state line.
• No — Do not store the standardize city/state line.
Working With CODE-1 Plus
19
1
Working With CODE-1 Plus in Dispatcher4
Table 3: Storage Options for City and State Fields (Part 3 of 3)
This option...
Store Short Name If
Input Short City
Name
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus whether or not to store the input
city. CODE-1 Plus stores the input city name as long
as the input city name matches the USPS short city
name. Choose from the following selections:
CS OUT
• Yes — Store the input city name.
• No — Do not store the input city name.
Store Standardized
Urbanization Name
GRAYED OUT OPTION. Tells CODE-1 Plus whether
or not to store the standardized urbanization name
when there are multiple matches, using the
following selections:
CS OUT
• Yes — Store the standardized urbanization name.
• No — Do not store the standardized urbanization
name.
Store City Name
From
Tells CODE-1 Plus whether to store the city name
from the USPS City/State File or to store the ZIP+4
File Preferred Last Line City Name, using the
following selections:
CS OUT
• Last Line City Name — Store the ZIP+4 File
Preferred Last Line City Name. For CASS 3553
generation, store Last Line City Name.
• Default City Name — Store the city name from
the USPS City/State File.
• Primary City Name — Store the Primary City
Name from the USPS City/State File.
20
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
ZIP, ZIP+4, DPBC, CR-RT Field Selections
The selections under the ZIP, ZIP+4, DPBC, CR-RT category on the CODE-1 Plus
primary window to which you can make storage options changes are:
These selections allow you to set up positions and lengths on the output record for
the following information:
•
ZIP Code
•
ZIP+4 Code
•
Delivery Point Barcode (DPBC)
•
DPBX with Check Digit
•
Carrier Route Code (CR-RT)
•
Extracted ZIP Code
•
DPBC Add-on
•
DPBC Add-on Check Digit
•
Final ZIP Code Source
•
Seasonal Delivery Flags
Working With CODE-1 Plus
21
1
Working With CODE-1 Plus in Dispatcher4
When you select one of these, an Add Field dialog box will appear. Each storage option
available in these dialog boxes are outlined on the following page. Unlike the earlier
tables, the storage options for these dialog boxes are split into separate tables for ZIP
Code, ZIP+4 Code, and Carrier Route Code as the storage options vary.
Table 4: Storage Options for the ZIP Code Dialog Box (Part 1 of 2)
This option...
ZIP Code Format
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus the format of your ZIP Code in
your input record, using the following selections:
Z5 OUT
• Character — Your ZIP Code is in character
format.
• Packed — Your ZIP Code is in packed format.
Store Even If
Information
Dropped
Tells CODE-1 Plus whether or not to reject any
information that does not appear to be address data
and to store the updated address, using the
following selections:
Z5 OUT
• Yes — Store information that does not appear to
be address data.
• No — Do not store information that does not
appear to be address data.
Store Even If
Multiple ZIP Code
Matches
Tells CODE-1 Plus whether or not the standardized
address should be stored when multiple ZIP Code
matches were found, using the following selections:
Z5 OUT
• Yes — Yes, store the standardized address when
multiple ZIP Code matches are found.
• No — No, do not store the standardized address
when multiple ZIP Code matches are found.
NOTE: This field is grayed out if the Store
Standardized Data Even If Multiple Matches Found
check box is enabled on the CASS Configuration
dialog box.
NOTE: CASS certification discounts are not
available when you select Yes..
Maximum Address
Correction for
Storage
Allows you to enter a number between 0 and 9 to
determine the maximum address correction score
you desire.
Z5 OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
Maximum Overall
Correctness for
Storage
Allows you to enter a number between 0 and 9 to
determine the maximum overall correctness score
you desire.
Z5 OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
22
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
Table 4: Storage Options for the ZIP Code Dialog Box (Part 2 of 2)
This option...
When ZIP Code Not
Stored, Store
Performs this function...
Tells CODE-1 Plus what to store if you do not have
an address match, using the following selections:
And maps to this
parameter...
Z5 OUT
• Input ZIP — Store the input ZIP Code.
• Blanks — Store blanks.
• Nothing — Store nothing.
• Zeros — Store zeros.
Store Input ZIP
Code
Tells CODE-1 Plus whether or not to store the input
ZIP Code, using the following selections:
Z5 OUT
Yes — Store the input ZIP Code.
No — Do not store the input ZIP Code.
NOTE: Selecting No will created a non-CASS
certified configuration and no PS Form 3553 will be
generated.
Table 5: Storage options on the ZIP+4 Code Dialog Box (Part 1 of 3)
This option...
ZIP Code+4 Format
Performs this function...
Tells CODE-1 Plus the format of your ZIP+4 Code in
your input record, using the following selections:
And maps to this
parameter...
Z4 OUT
• Character — Your ZIP+4 Code is in character
format.
• Packed — Your ZIP+4 Code is in packed format.
• Hyphen — You want CODE-1 Plus to store your
ZIP+4 Code with a preceding hyphen.
Store Even If
Information
Dropped
Tells CODE-1 Plus whether or not to reject any
information that does not appear to be address data
and to store the updated address, using the
following selections:
Z4 OUT
• Yes — Store information that does not appear to
be address data.
• No — Do not store information that does not
appear to be address data.
Working With CODE-1 Plus
23
1
Working With CODE-1 Plus in Dispatcher4
Table 5: Storage options on the ZIP+4 Code Dialog Box (Part 2 of 3)
This option...
Store Even If
Multiple ZIP Code
Matches
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus whether or not the standardized
address should be stored when multiple ZIP Code
matches were found, using the following selections:
Z4 OUT
• Yes — Yes, store the standardized address when
multiple ZIP Code matches are found.
• No — No, do not store the standardized address
when multiple ZIP Code matches are found.
NOTE: This field is grayed out if the Store
Standardized Data Even If Multiple Matches Found
check box is enabled on the CASS Configuration
dialog box.
NOTE: CASS certification discounts are not
available when you select Yes..
Store Even If
Multiple ZIP+4
Code Matches
Tells CODE-1 Plus whether or not the standardized
ZIP+4 Code and Delivery Point Barcode (DPBC)
should be stored when multiple ZIP+4 Code
matches are found, using the following selections:
Z4 OUT
• From Disposition Code — Store the disposition
indicator.
• Standard ZIP+4 & DPBC — Store the
standardized ZIP+4 Code and DPBC when
multiple ZIP+4 Code matches are found.
• Disposition & Write to NCO — Store the
disposition indicator and write it to the NCO file.
Maximum Address
Correction for
Storage
Allows you to enter a number between 0 and 9 to
determine the maximum address correction score
you desire.
Z4 OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
Maximum Overall
Correctness for
Storage
Allows you to enter a number between 0 and 9 to
determine the maximum overall correctness score
you desire.
Z4 OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
24
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
Table 5: Storage options on the ZIP+4 Code Dialog Box (Part 3 of 3)
This option...
When ZIP+4 Code
Not Stored, Store...
Performs this function...
Tells CODE-1 Plus what gets stored, if for any
reason, the ZIP+4 Code is not being stored, using the
following selections:
And maps to this
parameter...
Z4 OUT
• Blanks — Store blanks.
• Nothing — Store nothing.
• Input ZIP+4 Code — Store the input ZIP+4 Code.
Rooftop Access
Method
Uses longitude and latitude coordinates to provide
more accuracy to your location and distance
calculation, using the following selections:
G9ZIP9
• No Rooftop Access — No rooftop access is to be
attempted.
• ZIP+4 Database — Use the DPBC and house
number that matched to the ZIP+4 database to
determine the rooftop answer.
• Input ZIP+4 Code — Use the input DPBC and
house number to determine the rooftop answer.
• Database/Input ZIP+4 — First, use the DPBC and
house number from the ZIP+4 database match,
and then, if there is no ZIP+4 database match, use
the input DPBC and house number to determine
the rooftop answer.
Working With CODE-1 Plus
25
1
Working With CODE-1 Plus in Dispatcher4
Table 6: Storage Options on the Carrier Route Code Dialog Box (Part 1 of 2)
This option...
Store Even If
Information
Dropped
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus whether or not to reject any
information that does not appear to be address data
and to store the updated address, using the
following selections:
CR OUT
• Yes — Store information that does not appear to
be address data.
• No — Do not store information that does not
appear to be address data.
Store Even If
Multiple ZIP Code
Matches
Tells CODE-1 Plus whether or not the standardized
address should be stored when multiple ZIP Code
matches were found, using the following selections:
CR OUT
• Yes — Store the standardized address when
multiple ZIP Code matches are found.
• No — Do not store the standardized address
when multiple ZIP Code matches are found.
NOTE: This field is grayed out if the Store
Standardized Data Even If Multiple Matches Found
check box is enabled on the CASS Configuration
dialog box.
NOTE: CASS certification discounts are not
available when you select Yes.
Store Even If
Multiple CR-RT
Code Matches
GRAYED OUT OPTION. Tells CODE-1 Plus whether
or not the standardized Carrier Route Code should
be stored when multiple Carrier Route Code
matches were found, using the following selections:
CR OUT
• Yes — Store the standardized Carrier Route
Code.
• No — Do not store the standardized Carrier
Route Code.
NOTE: If enabled, CODE-1 Plus will stored the
returned Carrier Route Code.
NOTE: CASS certification discounts are not
available when you select Yes.
Maximum Address
Correction for
Storage
Allows you to enter a number between 0 and 9 to
determine the maximum address correction score
you desire.
CR OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
26
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
Table 6: Storage Options on the Carrier Route Code Dialog Box (Part 2 of 2)
This option...
Maximum Overall
Correctness for
Storage
Performs this function...
Allows you to enter a number between 0 and 9 to
determine the maximum overall correctness score
you desire.
And maps to this
parameter...
CR OUT
NOTE: This field is grayed out if you have specified
this setting on the Overriding Maximum
Correctness Scores dialog box.
When Carrier
Route Code Not
Stored, Store
Tells CODE-1 Plus what to store when the
standardized carrier route code was stored, using
the following selections:
CR OUT
• Blanks — Store blanks.
• Input ZIP Code — Store the input ZIP Code.
• Nothing — Store nothing.
Address Elements Field Selections
The selections under the Address Elements category on the CODE-1 Plus primary
window to which you can make storage options changes are:
These selections allow you to set up positions and lengths on the output record for
the address elements.
Working With CODE-1 Plus
27
1
Working With CODE-1 Plus in Dispatcher4
When you select one of these, an Add Field dialog box displays. A description for each
storage option available with this dialog box follows.
Table 7: Storage Options for Address Elements Fields
This option...
When no Match was
Found, Store
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus what to store in place of the
address element that could not be matched, using
the following selections:
AE OUT
• Blanks — Store blanks.
• Nothing — Store nothing.
• Input Elements from Primary Address
—
Allows you to store elements from the address
using the primary address line only.
• Input Elements Merged from Primary and
Secondary Address — Allows you to store
elements from the address and merging
secondary line elements with the primary
address line elements. In cases where an
element appears in the primary and the
secondary address lines, use the element from
the primary address lines.
Store Private Mail
Box Numbers
Tells CODE-1 Plus whether or not to store all
Private Mail Box Numbers (PMBs), using the
following selections:
AE OUT
• Yes — Store all PMBs.
• No — Do not store all PMBs
NOTE: If you select Yes, a non-CASS-certified
configuration is created and no PS Form 3553 will
be generated.
Normalized Address Lines Field Selections
The selections under the Normalized Address Lines category on the
CODE-1 Plus primary window to which you can make storage options changes are:
These selections allow you to set up positions and lengths on the output record for
the following information:
•
28
Normalized Address Lines.
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
When you select one of these, an Add Field dialog box will appear. A description for
each storage option available with this dialog box follows.
Table 8: Storage Options for Normalized Address Lines Fields
This option...
Store Normalized
Primary Address
Performs this function...
Tells CODE-1 Plus whether you would like all
normalized primary address records stored or the
normalized primary address stored when the
standardized address was not stored, using the
following selections:
And maps to this
parameter...
AP OUT
• Only When No Match Was Found — Store the
normalized primary address.
• For All Records — Store all normalized primary
address records.
Store Normalized
Secondary Address
Tells CODE-1 Plus whether you would like all
secondary address records store or the secondary
primary address stored when the standardized
address was not stored, using the following
selections:
AP OUT
• Only When No Match Was Found — Store the
normalized secondary address
• For All Records — Store all normalized
secondary primary address records
• Store Dropped Dual Address — Store dropped
dual address from matched address.
Store Normalized
Address Types
Tells CODE-1 Plus what types of normalized
addresses to store, using the following selections:
AP OUT
• All Types — Store all types of normalized
addresses.
• Selected Types — Normalize selected address
types such as General Delivery keywords, PO Box
keywords, and RR/HC keywords, or otherwise
return input.
Working With CODE-1 Plus
29
1
Working With CODE-1 Plus in Dispatcher4
Other Match Results Field Selections
The selection under the Other Match Results category on the CODE-1 Plus primary
window to which you can make storage options changes is:
When you select it, an Add Field dialog box will appear. A description for each storage
option available with this dialog box follows.
Table 9: Storage Option for Other Match Results Field
This option...
Masterfile Vintage
Date Format
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus the format of the masterfile
vintage date in your input record, using the following
selections:
CS ZIP
• 4-Byte Character Format — YYMM
• 6-Byte Character Format — YYYYMM
• 3-Byte Packed Format — YYMM
• 4-Byte Packed Format — YYYYMM
• 2-Byte Packed Format — YYMM
• 3-Byte Binary Format — YYYYMM
Line of Travel Field Selections
The selections under the Line of Travel category on the CODE-1 Plus primary window
to which you can make storage options changes are:
30
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
These selections allow you to set up positions and lengths on the output record for
the following information:
•
Line of Travel.
When you select one of these, an Add Field dialog box will appear. A description for
each storage option available with this dialog box follows.
Table 10: Storage Option for Line of Travel Fields
This option...
When LOT Code is
Not Determined
Performs this function...
Tells CODE-1 Plus whether you want to store
nothing or blanks when the LOT Code is not
determined, using the following selections:
And maps to this
parameter...
LOTOUT
• Blank — Store blanks.
• Nothing — Store nothing.
Delivery Point Validation Field Selections
The selections under the Delivery Point Validation category on the CODE-1 Plus
primary window to which you can make storage options changes are:
NOTE: Refer to Chapter 6 of the Working With CODE-1 Plus Guide for more
information on the Delivery Point Validation option for CODE-1 Plus.
Working With CODE-1 Plus
31
1
Working With CODE-1 Plus in Dispatcher4
When you select one of these, an Add Field dialog box will appear. A description for
each storage option available with this dialog box follows.
Table 11: Storage Options for Delivery Point Validation Fields (Part 1 of 3)
This option...
Multi-Match — ZIP
and PO Box or RR/
Hwy Contract Addr
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus whether you want to DPV confirm
the ZIP Code and PO Box or RR/Highway Contract
address when multiple matches occur, using the
following selections:
DPVIN
• DPV Confirm — When the above-described
multiple match occurs, DPV confirm.
• No DPV Confirm — When the above-described
multiple match occurs, do not DPV confirm.
Multi-Match — ZIP
and Street Addr
Type
Tells CODE-1 Plus whether or not you want to DPV
confirm the ZIP Code and Street Address type when
multiple matches occur, using the following
selections:
DPVIN
• DPV Confirm — When the above-described
multiple match occurs, DPV confirm.
• No DPV Confirm — When the above-described
multiple match occurs, do not DPV confirm.
Multi-Match —
Carrier Route
Tells CODE-1 Plus whether or not you want to DPV
confirm the Carrier Route when multiple matches
occur, using the following selections:
DPVIN
• DPV Confirm — When the above-described
multiple match occurs, DPV confirm.
• No DPV Confirm — When the above-described
multiple match occurs, do not DPV confirm.
Multi-Match —
Directional
Tells CODE-1 Plus whether or not you want to DPV
confirm the directional when multiple matches
occur, using the following selections:
DPVIN
• DPV Confirm — When the above-described
multiple match occurs, DPV confirm.
• No DPV Confirm — When the above-described
multiple match occurs, do not DPV confirm.
Multi-Match —
Suffix
Tells CODE-1 Plus whether or not you want to DPV
confirm the suffix when multiple matches occur,
using the following selections:
DPVIN
• DPV Confirm — When the above-described
multiple match occurs, DPV confirm.
• No DPV Confirm — When the above-described
multiple match occurs, do not DPV confirm.
32
Software Release 4.0.0/March 2015
Configuring All Fields on the CODE-1 Plus Primary Window
1
Table 11: Storage Options for Delivery Point Validation Fields (Part 2 of 3)
This option...
Multi-Match —
Suffix/Directional
Correction
Performs this function...
Tells CODE-1 Plus whether or not you want to DPV
confirm the suffix/directional correction when
multiple matches occur, using the following
selections:
And maps to this
parameter...
DPVIN
• DPV Confirm — When the above-described
multiple match occurs, DPV confirm.
• No DPV Confirm — When the above-described
multiple match occurs, do not DPV confirm.
Multi-Match —
Multiple Input 2nd
Components
Tells CODE-1 Plus whether or not you want to DPV
confirm the multiple input secondary components
when multiple matches occur, using the following
selections:
DPVIN
• DPV Confirm — When the above-described
multiple match occurs, DPV confirm.
• No DPV Confirm — When the above-described
multiple match occurs, do not DPV confirm.
Unique ZIP/Small
Town Default ZIP+4
Assignment
Tells CODE-1 Plus whether or not you want to DPV
confirm a ZIP+4 assigned by CODE-1 Plus during
regular processing, using the following selections:
DPVIN
• DPV Confirm — When the above-described ZIP+4
assignment occurs, DPV confirm.
• No DPV Confirm — When the above-described
ZIP+4 assignment occurs, do not DPV confirm.
DPV Secondary
Address Validation
Tells CODE-1 Plus whether or not you wish to
perform DPV processing on secondary address
information, using one of the following selections:
DPVIN
• Bypass DPV Validation — Do not perform DPV
validation on secondary address information.
• Do Not Bypass DPV — Do not perform DPV
validation Validation on secondary address
information.
CMRA Lookup
Tells CODE-1 Plus whether or not you wish to
determine if an address is a Commercial Mail
Receiving Agency (CMRA), using one of the following
options:
DPVIN
• Bypass CMRA Lookup — No, do not determine if
the address is a CMRA.
• Do Not Bypass CMRA Lookup — Yes, determine
if the address is a CMRA.
RDI Indicator
Tells CODE-1 Plus whether or not you wish to
perform DPV or RDI processing, or both, using one
of the following options:
DPVIN
• Do DPV Only — Perform DPV processing only.
• Do Both DPV and RDI — Perform both DPV and
RDI processing.
• Do RDI Only — Perform RDI processing only.
Working With CODE-1 Plus
33
1
Working With CODE-1 Plus in Dispatcher4
Table 11: Storage Options for Delivery Point Validation Fields (Part 3 of 3)
This option...
Business Flag
Option
And maps to this
parameter...
Performs this function...
In order to receive a distinction between which
RDI- processed address are only business
addresses and which are mixed (both business and
residential) addresses in the Business Flag
location, use one of the following options.
DPVOUT
• Return ‘B’ for All — Return B for all Business
Delivery Points
• Return ‘M’ and ‘B’ — Return M for Mixed
Business and Residential Delivery Points and B
for Business-only Delivery Points.
DPV Data Base
Type Option
Tells CODE-1 Plus which DPV file to match against.
DPVIN
• Blank — Process the DPV split file.
• S — Process the DPV split file.
• F — Process the DPV flat file.
• H — Process the DPV full (hash) file.
DPV File Option
This option allows you to specify the DPV file to
match against.
DPVIN
• Blank — Process the DPV split file.
• S — Process the DPV split file.
• F — Process the DPV flat file.
• H — Process the DPV full (hash) file.
DPV Memory
Module Size
Indicator
This option allows you to specify size of DPV module.
DPVIN
• Blank — DPV process will be using Medium
memory model (default).
• P — Pico memory model (no files in memory).
• U — Micro memory model (no files in memory,
only indexes).
• S — Small memory model (HSC and HSF in
memory).
• M — Medium memory model (LCD also in
memory).
• L — Large memory model (HSX also in memory).
• H — Huge memory model (all files in memory).
Shutdown for DPV
Seed
Tells CODE-1 Plus to shut down when the DPV
subsystem encounters a seed record.
DPVOUT
• S — Shut down CODE-1 Plus when a DPV seed
record is encountered.
• W — Continue processing.
The default is "W". In either case CODE-1 Plus will
output to the execution log file the seed record
information necessary to reactivate the DPV license.
34
Software Release 4.0.0/March 2015
Configuring the Options on the Records Menu
1
Configuring the Options on the Records Menu
On the CODE-1 Plus primary window there are several pull-down menus which allow
you various options for your CODE-1 Plus processing.
Pull-down menus
First, we will discuss each dialog box under the Records menu and the choices
available to you in your CODE-1 Plus processing. Later in this chapter, we will
describe the dialog boxes under the Options and Reports menus.
Address...
1. Click on the Records menu, and a list of options appears.
2. Select Address... under Input Formats and the Address and City/State/ZIP Code
Layout dialog box appears.
Working With CODE-1 Plus
35
1
Working With CODE-1 Plus in Dispatcher4
Use this dialog box to define the formats for your address, city, state, and ZIP
Code information in your input file. The table below describes each selection on
this screen.
Table 12: Options on the Address and City/State/ZIP Code
Layout Dialog Box
This option...
And maps to this
parameter...
Performs this function...
Address section
Single Line
Defines your input address as a single line street
address.
ADDRDF
2 to 6 Lines
Defines your input address as containing up to 6
address lines. Appearing as a mailing label, it
may or may not include the City, State, and ZIP
Code.
ADDRDF
2 to 6 Fields
Defines your input address as containing up to 6
street address fields, which can be joined
together to build one good street address.
ADDRDF
Firm name stored
within the address
lines
Defines if the firm name is stored within the
address lines on the input file.
FIRMNM
Three Separate
Fields
Defines if the City, state, and ZIP Code are
located in three separate fields.
CS ZIP
City/State/ZIP
Together in 1 Field
City, state, and ZIP Code are located in a single
field separate from the address.
CS ZIP
City/State
Together, ZIP
Separate
City/state are located in one field and the ZIP
Code in a separate field.
CS ZIP
City/State/ZIP
Among Address
Lines
City, state, and ZIP Code are located among the
address lines (you must first select the 2 to 6
lines radio button).
CS ZIP
City/State Among
Address Lines, ZIP
Separate
City/state are mixed with address lines; the ZIP
Code is in a separate field.
CS ZIP
City/State/ZIP section
36
Software Release 4.0.0/March 2015
Configuring the Options on the Records Menu
1
ZIP Codes...
1. Click on the Records menu, and a list of options appears.
2. Select ZIP Codes... under Input Formats, and the ZIP Code and ZIP+4 Code Formats
dialog box appears.
Use this dialog box to define the format of your ZIP Code and ZIP + 4 Code
information in your input file.
Table 13: Options on the ZIP Code and ZIP+ Code Formats Dialog Box
This option...
Performs this function...
And maps to this
parameter...
Separate ZIP Code section
Character
Defines your input ZIP Code as being in a
character format.
CS ZIP
Packed
Defines your input ZIP Code as being in a packed
format.
CS ZIP
3-Byte Binary
Defines your input ZIP Code as being 5 digits in 3bytes.
CS ZIP
4-Byte Binary
Defines your input ZIP Code as being 9 digits in 4bytes.
CS ZIP
Character
Defines your input ZIP+4 Code as being in
character format.
CS ZIP
Packed
Defines your input ZIP+4 Code as being in packed
format.
CS ZIP
Binary
Defines your input ZIP+4 Code as being in binary
format.
CS ZIP
ZIP+4 Code section
Working With CODE-1 Plus
37
1
Working With CODE-1 Plus in Dispatcher4
Masterfile Vintage Date...
1. Click on the Records menu, and a list of options appears
2. Select Masterfile Vintage Date... under Input Formats, and the Input Masterfile Vintage
Date Format dialog box appears.
Use this dialog box to define the format of your masterfile date information.
Table 14: Options on the Input Masterfile Vintage Date Format Dialog Box
This option...
And maps to this
parameter...
Performs this function...
Masterfile Vintage Date section
38
4-Byte Character
Format
Defines your Masterfile Vintage Date as being in
a 4-byte character format.
CS ZIP
6-Byte Character
Format
Defines your Masterfile Vintage Date as being in
a 6-byte character format.
CS ZIP
3-Byte Packed
Format
Defines your Masterfile Vintage Date as being in
a 3-byte packed format.
CS ZIP
4-Byte Packed
Format
Defines your Masterfile Vintage Date as being in
a 4-byte packed format.
CS ZIP
2-Byte Binary
Format
Defines your Masterfile Vintage Date as being in
a 2-byte binary format.
CS ZIP
3-Byte Binary
Format
Defines your Masterfile Vintage Date as being in
a 3-byte binary format.
CS ZIP
Actual Date
Defines your Masterfile Vintage Date
CS ZIP
Software Release 4.0.0/March 2015
Configuring the Options on the Records Menu
1
Geographic Input...
1. Click on the Records menu, and a list of options appears
2. Geographic Coding Plus is a Pitney Bowes product. Contact your sales
representative for more information on this and other Pitney Bowes products.
3. Select Geographic Input... on the Records menu, and the Geographic Coding Input
dialog box appears.
Use this dialog box to define ZIP Code and ZIP+4 Code information for a
CODE-1 Plus job that uses Geographic Coding Plus.
Table 15: Options on the Geographic Coding Input Dialog Box
This option...
Performs this function...
And maps to this
parameter...
ZIP Code section
Location
Defines the location of the ZIP Code information
for Geographic Coding Plus.
G9ZIP9
Character button
Defines your ZIP Code information as being in
character format for Geographic Coding Plus.
G9ZIP9
Packed button
Defines your ZIP Code information as being in
packed format for Geographic Coding Plus.
G9ZIP9
Location
Defines the location of your ZIP+4 Code
information for Geographic Coding Plus.
G9ZIP9
Character button
Defines your ZIP+4 Code information as being in
character format for Geographic Coding Plus.
G9ZIP9
Packed button
Defines your ZIP+4 Code information as being in
packed format for Geographic Coding Plus.
G9ZIP9
ZIP + 4 Code section
Working With CODE-1 Plus
39
1
Working With CODE-1 Plus in Dispatcher4
Rearrange Before Processing
1. Click on the Records menu, and a list of options appears.
2. Select Rearrange Before Processing on the Records menu, and the Rearrange Field
Before Processing dialog box appears.
Use this dialog box to change the order of your fields in your input file before you
begin CODE-1 Plus processing.
Table 16: Options on the Rearrange Field Before Processing Dialog Box
This option...
And maps to this
parameter...
Performs this function...
Source section
Input Field
Character Zeros
Select the option for the type of information that
you wish to move. Then, click [Add]. The Move
Definition dialog box, pictured on the following
page, will appear.
MOVE I
MOVE I
Blanks
MOVE I
Binary Zeros
MOVE I
Defined Move Operations section. This section will display the options you selected in the Source
Section with their move definitions.
40
Software Release 4.0.0/March 2015
Configuring the Options on the Records Menu
1
Table 17: Buttons on the Rearrange Field Before Processing Dialog Box
This option...
Performs this function...
Add
Adds the selected source to the Defined Move
Operations section and opens the Move Definition
dialog box for each entry.
Remove
Removes a selected source from the Defined
Move Operations section.
Modify
Allows you to modify the selected source and its
move definition.
OK
Tells CODE-1 Plus that your entries are correct.
Once clicked, the Rearrange Fields Before
Processing dialog box will close.
Cancel
Cancels any action in this dialog box that you may
have defined.
Help
Opens the help system for assistance in setting up
and running your CODE-1 Plus job in Dispatcher4.
3. Once you select a source option and click [Add] on the Rearrange Fields Before
Processing dialog box, the Move Definition dialog box displays.
The table below describes each entry on this dialog box.
Table 18: Options on the Move Definition Dialog Box
This option...
Performs this function...
And maps to this
parameter...
Source Location
Tells CODE-1 Plus where to find the data in your
file that you want to move.
MOVE I
Data Length
Defines how long the data is that you want to
move.
MOVE I
Target Location
Tells CODE-1 Plus where you would like to place
this data in your file.
MOVE I
Working With CODE-1 Plus
41
1
Working With CODE-1 Plus in Dispatcher4
Rearrange After Processing
1. Click on the Records menu, and a list of options appears.
2. Select Rearrange After Processing on the Records menu, and the Rearrange Field
After Processing dialog box appears.
This dialog box is very similar to the Rearrange Fields Before Processing dialog box
in the previous section. However, this dialog box allows you to change the order
of your fields in your file after CODE-1 Plus processing.
Table 19: Options on the Rearrange Field After Processing Dialog Box
This option...
And maps to this
parameter...
Performs this function...
Source box
Input Field
Character Zeros
Select the option for the type of information that
you wish to move. Then, click [Add]. The Move
Definition dialog box, pictured on the following
page, will appear.
MOVE O
MOVE O
Blanks
MOVE O
Binary Zeros
MOVE O
Defined Move Operations section. This section will display the options you selected in the Source
Section with their move definitions.
42
Software Release 4.0.0/March 2015
Configuring the Options on the Records Menu
1
3. Once you select a source option and click [Add] on the Rearrange Fields After
Processing dialog box, the Move Definition dialog box displays.
Table 20: Options on the Move Definition Dialog Box
This option...
Performs this function...
And maps to this
parameter...
Source Location
Tells CODE-1 Plus where to find the data in your
file that you want to move
MOVE O
Data Length
Defines how long the data is that you want to
move.
MOVE O
Target Location
Tells CODE-1 Plus where you would like to place
this data in your file.
MOVE O
Record Sequence
1. Click on the Records menu, and a list of options appears.
2. Select Records Sequence on the Records menu, and the Sequence Checking dialog
box appears.
Working With CODE-1 Plus
43
1
Working With CODE-1 Plus in Dispatcher4
Define up to 9 segments. See the table
below for details.
Prior to running CODE-1 Plus, you can use your own sort utility to sort the
records in your input file. CODE-1 Plus enables you to verify the sequence of your
records using up to 9 segments using this dialog box. Sequence errors will be
indicated in the execution log.
Table 21: Options on the Sequence Checking Dialog Box
This option...
And maps to this
parameter...
Performs this function...
Sequencing Field Segments
Source
Identifies the source of your sequencing field
segments.
SEQCHK
Start Position
Identifies the start position in the selected file
where sequence checking should begin.
SEQCHK
Length
Identifies that length of the information in the
start position.
SEQCHK
Format
Identifies the format of the information in the
start position:
SEQCHK
• Character
• Packed
Character or
Packed
44
Identifies the format of the information in the
start position.
SEQCHK
Software Release 4.0.0/March 2015
Configuring the Options on the Records Menu
1
Defining Your Segment(s)
You can use the Name, Position, Length, and Format fields on the Sequence Checking
dialog box to define more than one segment of information. The table below
illustrates how you can store information for (up to) nine defined segments.
Number of
Segment
Position for
Location
Position for
Length
Position for
Format
1
10-12
14-15
13
2
17-19
21-22
20
3
24-26
28-29
27
4
31-33
35-36
34
5
38-40
42-43
41
6
45-47
49-50
48
7
52-54
56-57
55
8
59-61
63-64
62
9
66-68
70-71
69
When a Sequence Error is Found
If a sequence error is detected during processing, you will be presented with several
options found in the When a Sequence Error is Found section of the dialog box. The
results in this section of the dialog box are detailed in the following table.
Table 22: Options in When a Sequence Error is Found Text Box (Part 1 of 2)
This option...
Performs this function...
And maps to this
parameter...
When a Sequence Error is Found...
Treat as End of File
Halts sequence checking after bypassing the
offending record and tells CODE-1 Plus to treat
the process as if the end of the input file had been
reached.
SEQCHK
Bypass Offending
Record
Bypasses the offending record and continues
checking the sequence.
SEQCHK
Working With CODE-1 Plus
45
1
Working With CODE-1 Plus in Dispatcher4
Table 22: Options in When a Sequence Error is Found Text Box (Part 2 of 2)
This option...
And maps to this
parameter...
Performs this function...
Continue
Processing
Offending Record;
Continue Sequence
Check
Continues processing the offending record and
continues sequence checking.
SEQCHK
Continue
Processing the
Offending Record;
Discontinue
Sequence Check
Continues processing the offending record, but
abandons any further sequence checking.
SEQCHK
Configuring the Options on the Options Menu
As stated earlier in this chapter, there are several pull-down menus on the CODE-1
Plus primary window that allow you to define options for your CODE-1 Plus
processing.
Pull-down menus
We will now continue with the Options menu, discussing each dialog box and the
choices available to you for CODE-1 Plus processing.
Limit Records...
1. Click on the Options menu, and a list of options displays.
46
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
2. Select Limit Records... on the Options menu, and the Limit Records to Process dialog
box appears.
Enter ZIP Code
range here
Identify number
of records to
skip here
Process a
sample of your
records here
Exclude or include
cerrecord here
The Limit Records to Process dialog box lets you limit the number of records to
process from your input file using various methods.
Table 23: Options on the Limit Records to Process Dialog Box (Part 1 of 2)
This option...
Performs this function...
And maps to this
parameter...
Limit by ZIP Code Limit the records processed by entering a ZIP Code range. in this section of
the dialog box. Only records falling between the highest and lowest ZIP Code you enter will be
processed.
Starting ZIP Code
Tells CODE-1 Plus which ZIP Code in your input
file is to be your starting ZIP Code for your limited
processing.
HEADER
Ending ZIP Code
Tells CODE-1 Plus which ZIP Code in your input
file is to be your ending ZIP Code for your limited
processing.
HEADER
Working With CODE-1 Plus
47
1
Working With CODE-1 Plus in Dispatcher4
Table 23: Options on the Limit Records to Process Dialog Box (Part 2 of 2)
This option...
And maps to this
parameter...
Performs this function...
Limit Number of Records to Process Specify a number of records you want to skip in this section
of the dialog box. If you enter the number 4 in the Number of Records to Skip text box, for
example, processing will begin with the fifth record.
Number of Records
to Skip
Tells CODE-1 Plus how many records you would
like to skip before beginning to process your
input file.
FILEDF
Maximum Number
of Records to
Process
Tells CODE-1 Plus the maximum number of
records you would like processed from your input
file.
FILEDF
Sampling Enter how many records you want to sample from your file. CODE-1 Plus processes
records picked at random.
Total Number of
Records in File
Tells CODE-1 Plus the total number of records
that you have in the sampling of your input file.
FILEDF
Number of Records
to Process
Tells CODE-1 Plus the number of records from
the sampling of your input file to process.
NTHSEL
See note below
See note below
Record Selection Can include or exclude a specified number of records in a random sampling of
your input files.
Include
Tells CODE-1 Plus to include the amount of
records in your input file that you select.
NTHSEL
Exclude every
___th Record
Tells CODE-1 Plus to skip every __th record
when processing.
NTHSEL
Total Number of
Records in File
Tells CODE-1 Plus how many total records you
have in your input file.
NTHSEL
Total Number of
Records to Process
Tells CODE-1 Plus the total number of records
that you want processed in your job.
NTHSEL
See note below.
See note below.
NOTE: CODE-1 Plus divides your entry from Number of Records to Process by
your entry from Total Number of Records in File. The resulting fraction is used
in your CODE-1 Plus job. Your entry from Total Number of Records to Process
is divided by your entry from Total Number of Records in File. The resulting
fraction is used in your CODE-1 Plus job.
48
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
Exit Routine
1. Click on the Options menu, and a list of options appears.
2. Select Exit Routine... on the Options menu, and the Exit Routine dialog box
appears.
Use this dialog box to specify your own exit routine that will pass each record to
a program of your choice. The exit routine you specify runs instead of the exit
routine that comes with Dispatcher4.
Table 24: Options on the Exit Routine Dialog Box
This option...
Performs this function...
And maps to this
parameter...
Name of Output
Exit Routine
Tells CODE-1 Plus the name of your output
routine.
EXIT OP
Parameter String
to Pass to Exit
Routine
Tells CODE-1 Plus which parameter string
should be passed to the exit routine.
EXIT OP
Working With CODE-1 Plus
49
1
Working With CODE-1 Plus in Dispatcher4
Confirm Without Matching
1. Click on the Options menu, and a list of options appears.
2. Select Confirm Without Matching... on the Options menu, and the Confirm Without
Matching dialog box appears.
Use this dialog box to indicate if CODE-1 Plus should bypass addresses for
specific records instead of performing an address match.
3. If CODE-1 Plus is unable to successfully match an address, such as for an
APO/FPO, a military base, or a government agency, you can choose to have these
records written automatically to the confirmed records output file instead of the
rejected records file.
Table 25: Options on the Confirm Without Matching Dialog Box (Part 1 of 2)
This option...
And maps to this
parameter...
Performs this function...
Confirm Record If
50
Equal to Any
Tells CODE-1 Plus that the confirmation flag,
inserted in the record, must be equal to one of
the confirmation values you have selected in
order to be confirmed automatically.
CONFRM
Unequal to All
Tells CODE-1 Plus that the confirmation flag
must not match any of the confirmation values
that you have chosen in order for those records to
be confirmed automatically.
CONFRM
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
Table 25: Options on the Confirm Without Matching Dialog Box (Part 2 of 2)
This option...
Performs this function...
And maps to this
parameter...
Confirmation Mark Processing
Start Position
Tells CODE-1 Plus the start position of your
confirmation mark.
CONFRM
Length
Tells CODE-1 Plus the length of your
confirmation mark.
CONFRM
Value
Tells CODE-1 Plus the value of your confirmation
mark.
CONFRM
Government
Agency ZIP Codes
Tells CODE-1 Plus to always bypass Government
Agency ZIP Codes.
CONFRM
APO/FPO ZIP
Codes
Tells CODE-1 Plus to always bypass APO/FPO ZIP
Codes.
CONFRM
Military ZIP Codes
Tells CODE-1 Plus to always bypass military ZIP
Codes.
CONFRM
Always Bypass
Working With CODE-1 Plus
51
1
Working With CODE-1 Plus in Dispatcher4
Maximum Correctness Scores...
1. Click on the Options menu, and a list of options appears.
2. Select Maximum Correctness Scores... from the Options menu, and the Overriding
Maximum Correctness Scores dialog box appears.
Use this dialog box to override the maximum correctness scores you established
for the individual fields you added to the output file.
Table 26: Options on the Overriding Maximum Correctness Scores Dialog Box
This option...
52
And maps to this
parameter...
Performs this function...
Maximum Address
Correctness Score
for Storage of
Standardized Date
Tells CODE-1 Plus the maximum acceptable
address probability of correctness. You need to
enter a number between 0 and 9, where 0
indicates the best case, and 9 indicates the worst
case.
CONFIG
Maximum Overall
Correctness Score
for Storage of
Standardized Date
Tells CODE-1 Plus the maximum acceptable
overall probability of correctness. You need to
enter an number between 0 and 9, where 0
indicates the best case, and 9 indicates the worst
case.
CONFIG
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
CASS Configuration
1. Click on the Options menu, and a list of options appears.
2. Select CASS Configuration... on the Options menu, and the CASS Configuration
dialog box appears.
Use the CASS Configuration dialog box to set your preferences for CASS
configuration on your CODE-1 Plus job.
Table 27: Options on the CASS Configuration Dialog Box (Part 1 of 3)
This option...
Performs this function...
And maps to this
parameter...
Match Setting
Street Name
Tells CODE-1 Plus the match setting you would
like for your street name information.
CONFIG
Firm Name
Tells CODE-1 Plus the match setting you would
like for your firm name information.
CONFIG
Directional/Suffix
Tells CODE-1 Plus the match setting you would
like for your directional/suffix information.
CONFIG
Working With CODE-1 Plus
53
1
Working With CODE-1 Plus in Dispatcher4
Table 27: Options on the CASS Configuration Dialog Box (Part 2 of 3)
This option...
Execution Log
Counter
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus the number of records, in
thousands, to trigger progress reporting in the
execution log.
CONFIG
(100 = 100,000)
Correct ZIP Codes
Tells CODE-1 Plus whether or not you want to
change incorrect ZIP Codes.
Z5 OUT
NOTE: This selections is only available if you have
configured how the ZIP Code will be stored in the
storage options section of the Add Field dialog
box for ZIP Code.
NOTE: When this radio button is selected, a nonCASS-certified configuration will be generated.
Store Standardized
Data Even If
Multiple Matches
Found
Tells CODE-1 Plus to store standardized
components, if multiple matches are found
during processing.
CONFIG
Return Output
Address in Upper,
Lower, and Mixed
Case In All Address
Components
Tells CODE-1 Plus whether or not to return in
upper, lower, and mixed case all address
components that contain text.
CONFIG
Database Vintage
Expired
Tells CODE-1 Plus whether or not you are using
an expired database.
CONFIG
Store Input ZIP
Code
Tells CODE-1 Plus whether or not you want to
store the input ZIP Code.
CONFIG
NOTE: When this radio button is selected, a nonCASS-certified configuration will be generated.
NOTE: Selecting this radio button will create a
non-CASS-certified configuration, and you will
not be able to produce a PS Form 3553.
Attempt Match to
the Base Record
Tells CODE-1 Plus whether or not to attempt to
match to the base record when an alternate
match is made and the input address contains
secondary address information.
CONFIG
NOTE: If this radio button is turned off, a
non-CASS-certified configuration will be
generated.
Attempt Exact
Secondary Match
Tells CODE-1 Plus to attempt a secondary match
(when selected) or to assign a default ZIP+4
Code.
CONFIG
NOTE: If this radio button is turned off, a
non-CASS-certified configuration will be
generated.
Use Enhanced
Street Matching
54
Tells CODE-1 Plus to attempt enhanced street
matching during processing.
CONFIG
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
Table 27: Options on the CASS Configuration Dialog Box (Part 3 of 3)
This option...
Performs this function...
And maps to this
parameter...
Use All Street
Matching
Tells CODE-1 Plus to attempt all street matching
during processing.
CONFIG
Limit Address
Match to ZIP
Locality
Tells CODE-1 Plus whether to perform address
matching against multiple localities during
CODE-1 Plus processing.
CONFIG
NOTE: When this radio button is selected, a
non-CASS-certified configuration will be
generated.
Split Indicia
Tells CODE-1 Plus whether to perform split
indicia processing.
CONFIG
Append C/O Data
Flag
Code indicating whether to append care-of (C/O)
data to the end of the output address line.
CONFIG
Standardize Vanity
City Names
Tells CODE-1 Plus whether or not to return the
vanity city name if a valid USPS vanity city name
is found to match a primary input city name.
CONFIG
Store All Private
Mail Box Numbers
Tells CODE-1 Plus whether or not to store all
private mail box numbers.
CONFIG
NOTE: Selecting this radio button will create a
non-CASS-certified configuration, and you will
not be able to produce a PS Form 3553.
Dual Address MatchThis section tells CODE-1 Plus how to handle addresses with multiple nonblank address lines or multiple address types on the same address line.
Normal
Does normal match scoring for street address
elements, input ZIP Code, matching address line,
and so on when selected.
CONFIG
Street Address
Tells CODE-1 Plus to return a street address
match regardless of the address line when
selected.
CONFIG
NOTE: When the street address radio button is
selected, a non-CASS-certified configuration will
be generated.
PO Box
Tells CODE-1 Plus to return a PO Box match
regardless of the address line when selected.
CONFIG
NOTE: When the PO Box radio button is selected,
a non-CASS-certified configuration will be
generated.
3. When you have completed your configuration, click on [OK] to complete the
dialog box, or click on [Advanced...], if you wish to define your CASS
configuration further.
Working With CODE-1 Plus
55
1
Working With CODE-1 Plus in Dispatcher4
CASS Configuration—Advanced Options
On the CASS Configuration dialog box, there is an [Advanced...] button. You can
access the Advanced Options dialog box by clicking on this button. The Advanced
Options dialog box allows you to override Z4CHANGE and ELOT certification data as
it appears on the USPS Form 3553.
NOTE: Company name, software name, and version number are optional, but at
least one text box must be filled if you plan on using either of the advanced
options.
Table 28: Options on the Advanced Options Dialog Box (Part 1 of 2)
This option...
And maps to this
parameter...
Performs this function...
Override Z4CHANGE Certification Data
Company Name
56
Tells CODE-1 Plus the Z4CHANGE-certified
company name as it appears on your USPS
certificate. This name can be up to 25 characters
long.
CASSA4
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
Table 28: Options on the Advanced Options Dialog Box (Part 2 of 2)
This option...
Performs this function...
Software Name
Tells CODE-1 Plus the Z4CHANGE-certified
software name as it is to appear on your USPS
certificate. This name can be up to 30 characters
long.
Software Version
Number
Tells CODE-1 Plus the Z4CHANGE-certified
software version number in V.RR.MM format.
And maps to this
parameter...
CASSA4
These two fields are
optional. However,
you must fill in at
least one field, or an
error will occur.
Any field not filled in
will retain its
current Group 1
value.
Override ELOT Certification Data
Company Name
Tells CODE-1 Plus the LOT-certified company
name as it is to appear on your USPS certificate.
This name can be up to 25 characters long.
CASSA7
Software Name
Tells CODE-1 Plus the LOT-certified software
name as it is to appear on your USPS certificate.
This name can be up to 30 characters long .
CASSA7
Software Version
Number
Tells CODE-1 Plus the LOT-certified software
version number in V.RR.MM format.
CASSA7
Working With CODE-1 Plus
57
1
Working With CODE-1 Plus in Dispatcher4
Memory Configuration
1. Click on the Options menu, and a list of options appears.
2. Select Memory Configuration from the Options menu, and the Address Matcher
Memory Configuration dialog box appears.
Use this dialog box to select how much system memory you want to allocate to the
address matcher. CODE-1 Plus calls the address matching module corresponding
to the selection you make here.
Table 29: Options on the Address Memory Matcher Configuration Dialog Box
This option...
Configuration
Choices
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus to use a particular memory
model using the following selections:
PGMNAM
• 1 MB — Allocates approximately 1 megabyte
of memory.
• 3 MB — Allocates approximately 3 megabytes
of memory.
• 6 MB — Allocates approximately 6 megabytes
of memory.
• 12 MB — Allocates approximately 12
megabytes of memory.
• 28 MB — Allocates approximately 18
megabytes of memory.
• Alternate RDI Large Memory Module — Tells
CODE-1 Plus to use the alternate large
memory module for RDI processing.
NOTE: For more information on the Residential
Delivery File (RDI) processing option available in
CODE-1 Plus, see Chapter 6.
Use DPV Large
Memory Module
(check box)
Tells CODE-1 Plus to use the alternate large
memory module for DPV processing. This check
box will appear grayed-out if you do not have the
Delivery Point Validation option.
PGMNAM
NOTE: For more information on the Delivery
Point Validation option available in CODE-1 Plus,
see Chapter 6.
58
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
Auxiliary File Options
1. Click on the Options menu, and a list of options appears.
2. Select Auxiliary File Options... from the Options menu, and the Auxiliary File
Options dialog box appears.
Use the Auxiliary File Options dialog box to identify the presence of an auxiliary
reference file for Early Warning System matching purposes. For more information
on the Auxiliary File Processing option and the Early Warning System available in
CODE-1 Plus, see Chapter 7.
Table 30: Options on the Auxiliary Reference File Options Dialog Box
This option...
Performs this function...
And maps to this
parameter...
File Location
Write Record to
NCO File
Tells CODE-1 Plus if you want the record to be
written to the NCO (uncoded) File.
AUXIL1
Write Record to
COK File
Tells CODE-1 Plus if you want the record to be
written to the COK (coded) File.
AUXIL1
Implement EWS
Processing
Tells CODE-1 Plus whether or not you want to
process the Auxiliary File using the Early
Warning System.
AUXIL1
Working With CODE-1 Plus
59
1
Working With CODE-1 Plus in Dispatcher4
Define Input Client Code
1. Click on the Options menu, and a list of options appears.
2. Select Define Input Client Code... on the Options menu, and the Define Input Client
Code dialog box appears.
Use the Define Input Client Code dialog box to define your input client code and
specify the date you received the file.
Table 31: Options on the Define Input Client Code Dialog Box
This option...
60
And maps to this
parameter...
Performs this function...
Client Code
Tells CODE-1 Plus the client code information.
This can be up to 9 characters long.
L CODE
File Received Date
Tells CODE-1 Plus the date that you received
your file. This date must be in YYYYMMDD format.
L CODE
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
Define LACS Parameter
1. Click on the Options menu, and a list of options appears.
2. Select Define LACS Parameter on the Options menu, and the Define LACS Processing
Indicator dialog box appears.
Use the Define LACS Processing Indicator dialog box to define whether you want
CODE-1 Plus to perform LACS processing.
Table 32: Options on the Define LACS Processing Indicator Dialog Box (Part 1 of 2)
This option...
Performs this function...
And maps to this
parameter...
No LACS
Processing
Tells CODE-1 Plus not to perform LACS
processing.
LACS
Perform ZIP+4
Match before LACS
Perform the ZIP+4 coding process and only call
LACSLink if the ZIP+4 process returns a LACS
indicator.
LACS
Return Limited
LACS Results
Tells CODE-1 Plus to perform limited LACSLink
subsystem processing.
LACS
Stop Processing on
a Seed
Tells CODE-1 Plus to stop processing when a
false-positive (seed record) has been
encountered.
LACS
Working With CODE-1 Plus
61
1
Working With CODE-1 Plus in Dispatcher4
Table 32: Options on the Define LACS Processing Indicator Dialog Box (Part 2 of 2)
This option...
And maps to this
parameter...
Performs this function...
Suppress 99 Code
for Seed
Tells CODE-1 Plus to produce the “99” return
code when a false-positive (seed record) has
been encountered.
LACS
LACSLink Memory
Module Size
Indicator
This option allows you to specify size of LACSLink
module.
LACS
• Blank — LACS process will be using Medium
memory model (default).
• 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).
62
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
Define STELNK Parameter
1. Click on the Options menu, and a list of options appears.
2. Select Define SuiteLink Parameter on the Options menu, and the Define the SuiteLink
Parameter dialog box appears.
Use the Define SuiteLink Parameter dialog box to define whether you want CODE-1
Plus to perform SuiteLink processing.
NOTE: USPS CASS regulations require SuiteLink processing for CASS certification
and to generate the USPS Form 3553 (USPS CASS Summary Report).
NOTE: The FIRMNM parameter is required to perform SuiteLink processing.
Working With CODE-1 Plus
63
1
Working With CODE-1 Plus in Dispatcher4
The table below describes each entry on this dialog box.
Table 33: Options on the Define SuiteLink Parameter Dialog Box
This option...
And maps to this
parameter...
Performs this function...
Enable SuiteLink
Select this option to perform SuiteLink processing.
STELNK
SuiteLink Error
Indicator
Determines whether to shut down when SuiteLink
reports an error.
STELNK
• 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”.
• 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”.
Database
Expiration Bypass
Specify if an expired SuiteLink database will cause
the job to terminate:
STELNK
• N — Do not bypass SuiteLink database expiration
date processing (default).
• Y — Bypass SuiteLink database expiration
processing.
SuiteLink Memory
Model Flag
This option allows you to specify size of SuiteLInk
memory module.
STELNK
• Blank — SuiteLink process will use the Medium
memory model (default.)
• 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.)
Exclude Secondary
Information from
Output Address
64
Select this option to call SuiteLInk without appending
the secondary information to the output address
line. All other fields, the ZIP + 4 value, and the DPC
code, are determined using the secondary
information returned by SuiteLInk. The default for
this field is to include secondary information from
SuiteLInk on the output address line.
STELNK
Software Release 4.0.0/March 2015
Configuring the Options on the Options Menu
1
Summary
1. Click on the Options menu, and a list of options appears.
2. Select Summary... from the Options menu, and the Job Summary dialog box
appears.
The Job Summary dialog box contains no fields for entering information. It displays
an overview of the selections you made in setting up your job.
3.
Return to the respective dialog box to change an entry
Working With CODE-1 Plus
65
1
Working With CODE-1 Plus in Dispatcher4
Configuring the Options on the Report Menu
As stated earlier in this chapter, on the CODE-1 Plus primary window there are
several pull-down menus which allow you various options for your CODE-1 Plus
processing.
Pull-down menus
We will now continue with the Reports menu, discussing each dialog box and the
choices available to you for CODE-1 Plus processing.
Choose Reports
1. Click on the Reports menu, and a list of options appears.
2. Select Choose Reports... from the Reports menu, and the Choose Reports dialog box
appears.
66
Software Release 4.0.0/March 2015
Configuring the Options on the Report Menu
1
Use this dialog box to select which reports you want CODE-1 Plus to generate in
addition to the reports that print by default. You can also use this dialog box to
print all selected reports in upper case only.
Table 34: Options on the Choose Reports Dialog Box (Part 1 of 2)
This option...
Performs this function...
And maps to this
parameter...
Choose Any of All of These Reports
Analysis of
Matched Records
Tells CODE-1 Plus to produce this report when
checked.
REPORT
ZIP+4 Coding by
State
Tells CODE-1 Plus to produce this report when
checked.
REPORT
ZIP+4 Coding by
List Code
Tells CODE-1 Plus to produce this report when
checked.
REPORT
ZIP+4 Coding by
3-Digit ZIP
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Carrier Coding by
State
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Carrier Coding by
List Code
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Line of Travel
Coding by List Code
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Carrier Coding by
3-Digit ZIP
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Summary by State
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Summary by
List Code
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Summary by
3-Digit ZIP
Tells CODE-1 Plus to produce this report when
checked.
REPORT
NDI Report
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Line of Travel
Coding by State
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Line of Travel
Coding by 3-Digit
ZIP
Tells CODE-1 Plus to produce this report when
checked.
REPORT
DPV Processing
Summary
Tells CODE-1 Plus to produce this report when
checked.
REPORT
DPV Processing by
List Code
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Working With CODE-1 Plus
67
1
Working With CODE-1 Plus in Dispatcher4
Table 34: Options on the Choose Reports Dialog Box (Part 2 of 2)
This option...
68
And maps to this
parameter...
Performs this function...
RDI Processing
Summary
Tells CODE-1 Plus to produce this report when
checked.
REPORT
RDI Processing by
List Code
Tells CODE-1 Plus to produce this report when
checked.
REPORT
Print Reports All
UPPER-CASE
Tells CODE-1 Plus to print all of the reports you
selected in upper-case, as opposed to mixed
case, format.
REPORT
Software Release 4.0.0/March 2015
Configuring the Options on the Report Menu
1
Advanced Report Options
1. If you click on the [Advanced...] options button on the Reports dialog box, the
Override CASS Certification Data dialog box will appear.
Use this dialog box to override CASS certification data as it appears in box A1 on
the PS Form 3553.
Table 35: Options on the Advanced Report Options Dialog Box
This option...
Performs this function...
And maps to this
parameter...
Override CASS Certification Data
Company Name
Tells CODE-1 Plus the CASS-certified company
name as it appears on your CASS certificate.
CASSA1
Software Name
Tells CODE-1 Plus the CASS-certified software
name as it appears on your CASS certificate.
CASSA1
Software Version
Number
Tells CODE-1 Plus the CASS-certified software
version number in V.RR.MM format.
CASSA1
NOTE: Your particular licensing agreement may not permit your company to
certify the CODE-1 Plus product under your company name. See your software
licensing agreement for permitted scope and use of the product.
Working With CODE-1 Plus
69
1
Working With CODE-1 Plus in Dispatcher4
Headers/Footers
1. Click on the Reports menu, and a list of options appears.
2. Select Headers/Footers... from the Reports menu, and the Headers and Footers
dialog box appears.
Use this dialog box to enter the header and footer information to print on all
reports.
Table 36: Options on the Define Input Client Code Dialog Box (Part 1 of 2)
This option...
70
And maps to this
parameter...
Performs this function...
Main Header
Tells CODE-1 Plus what you would like to have
printed as the main header on all of your reports.
HEADER
Date
Tells CODE-1 Plus which date you would like to
have printed on the top of all your report under
the main header.
HEADER
Header Lines
Tells CODE-1 Plus any additional information you
wish to have printed in the header areas of your
reports beneath the main header and date.
UHDXX
Footer Lines
Tells CODE-1 Plus any additional information you
wish to have printed in the footer areas of your
reports above the main footer.
UFTXX
Software Release 4.0.0/March 2015
Configuring the Options on the Report Menu
1
Table 36: Options on the Define Input Client Code Dialog Box (Part 2 of 2)
This option...
Performs this function...
And maps to this
parameter...
Lines Per Page —
Ex. Log
Tells CODE-1 Plus how many lines per page you
wish to appear on your Execution Log Report.
PAGESZ
Lines Per Page —
Reports
Tells CODE-1 Plus how many lines per page you
wish to appear on all of your other reports.
PAGESZ
List/Mailer Attributes
1. Click on the Reports menu, and a list of options appears.
2. Select List/Mailer Attributes... from the Reports menu, and the List and Mailer
dialog box appears.
Working With CODE-1 Plus
71
1
Working With CODE-1 Plus in Dispatcher4
Use this dialog box to enter information to print in the appropriate boxes on your
CASS form to eliminate the need to hand-write in all list attributes and mailers.
Table 37: Options on the List and Mailer Dialog Box
This option...
And maps to this
parameter...
Performs this function...
List Attributes
Processor Name
Identifies the organization(s) that coded the
name and address list(s) and/or performed the
ZIP+4 barcoding using CASS-certified software.
The name can be up to 20 characters long.
LISTNM
NOTE: You can use the three text boxes to enter
the name and address information of your list
processor.
Identifier
Identifies the name or ID of the current nameand-address list.
LISTID
NOTE: You can use the two text boxes for this
information.
Number of Lists
Indicates the number of lists you used to produce
your mailing. The number you enter in this text
box must be right-justified.
Mailer Name and Address In the text boxes in this section of the dialog box, you can enter the name
and address information for your mailer.
72
Software Release 4.0.0/March 2015
Dispatcher4 Field Labels
1
Dispatcher4 Field Labels
This section describes the field labels for the File Format Module and CODE-1 Plus
dialog boxes used in CODE-1 Plus Dispatcher4 and references them to the associated
field names in the parameters.
Input File Field Labels
In Dispatcher4, there are predefined field labels that CODE-1 Plus requires you use
to identify the fields found in your input file. In the File Format Module dialog box,
click on the Name and ID fields to do this, as shown below. For the input fields, you
can define any Name you want, but you must select the ID from the options provided
in the program’s drop-down list.
If you are linking additional job steps in Dispatcher4, it is important to use the proper
field IDs. CODE-1 Plus uses these to identify this information for matching.
Additionally, if the output from your CODE-1 Plus job step is used in
MailStream Plus. MailStream Plus needs the ZIP Code, ZIP + 4, DPBC, Carrier Route,
and LOT information properly identified.
Working With CODE-1 Plus
73
1
Working With CODE-1 Plus in Dispatcher4
It is important to use the proper field IDs for address lines, city, state, and ZIP Code.
The table below lists the input file field labels in Dispatcher4 and the associated ID
field labels that you should use, as well the associated parameters.
Table 38: Input File Field Labels Used in Dispatcher4 (Part 1 of 2)
Name Field Label
Name Label can
be the same as
ID Label or userdefined.
74
Predefined ID Field
Label
Purpose
Parameter
Notes
Address 1
Defines Input
Address Lines 1
ADDRDF
Address 2
Defines Input
Address Lines 2
ADDRDF
Address 3
Defines Input
Address Lines 3
ADDRDF
Address 4
Defines Input
Address Lines 4
ADDRDF
Address 5
Defines Input
Address Lines 5
ADDRDF
Address 6
Defines Input
Address Lines 6
ADDRDF
City
Defines Input City
CS ZIP
Use if City in
separate field.
Otherwise...
State
Defines Input
State
CS ZIP
Use if State in
separate field.
Otherwise...
ZIP Code
Defines Input ZIP
Code
CS ZIP
Use if ZIP Code in
separate field.
Otherwise...
ZIP+4 Code
Defines Input
ZIP+4 Code
CS ZIP
Carrier Route
Defines Input
Carrier Route
CS ZIP
Firm Name
Defines Input
Firm Name
FIRMNM
Urbanization
Name
Defines Input
Urbanization
Name
ADDRDF
City & State
City & State
Defines Input City
and State Field
CS ZIP
Use if City and
State in a single
field.
City, State, ZIP
City, State, ZIP
Defines Input City,
State, and ZIP
CS ZIP
Use if City, State,
and ZIP are in
single field.
Software Release 4.0.0/March 2015
Dispatcher4 Field Labels
1
Table 38: Input File Field Labels Used in Dispatcher4 (Part 2 of 2)
Name Field Label
Predefined ID Field
Label
Purpose
Parameter
Notes
List Code
List Code
Defines Input List
(file) Code for List
Conversion Plus,
Merge/Purge
Plus
FLCODE
Add if linking
Merge/Purge Plus
step in job.
Piece ID
Piece ID
Defines Piece ID
for MailStream
Plus
P ATTR
Add if linking
MailStream Plus
step in job.
Output Layout File Definition Field Labels
The CODE-1 Plus job definition screen below displays some of the predefined output
data field options. The left side of the screen shows the options that are available for
selection and the right side of the screen shows the selected output data fields that
CODE-1 Plus will append to the records. Output from CODE-1 Plus has the American
flag icon next to it.
Working With CODE-1 Plus
75
1
Working With CODE-1 Plus in Dispatcher4
The table below lists the output layout file definition field labels used in
Dispatcher 4/CODE-1 Plus.
Table 39: Output Layout File Definition Field Labels Used
in Dispatcher4 (Part 1 of 5)
Predefined Name Field
Label
Purpose
Parameter
Description
Standardized Address
Address with
Apartment
Defines Output Address
Line with Apartment
Number
SA OUT
123 MAIN ST APT 3
Address without
Apartment
Defines Output Address
Line without Apartment
Number
SA OUT
123 MAIN ST
Apartment/PMB
Number
Defines Output Address
Line with Apartment
Number only or PMB
Number only
SA OUT
APT 3
Private Mail Box
Defines Output Address
Line with Private Mail Box
(PMB) only
SA2OUT
PMB 100
Defines Output Firm Name
FIRMNM
Standardized City/State
Line
Defines City/State Name
CS OUT
City, State, ZIP, ZIP+4
returned in a single
field. Format: City ST
ZIP-ZIP+4
Long City Name
Defines Output Long City
Name
CS OUT
Maximum length — 28
characters
Short City Name
Defines Output Short City
Name
CS OUT
Maximum length — 13
characters
State Abbreviation
Defines Output State
Abbreviation
CS OUT
2 characters
Urbanization Name
Defines Output
Urbanization Name
CS OUT
Standardized Firm Name
Standardized Firm
Name
City and State
76
Software Release 4.0.0/March 2015
Dispatcher4 Field Labels
1
Table 39: Output Layout File Definition Field Labels Used
in Dispatcher4 (Part 2 of 5)
Predefined Name Field
Label
Extracted Urbanization
Name
Working With CODE-1 Plus
Purpose
Defines Output for the
Urbanization Name
Parameter
ADDRDF
column 52
has a U
meaning
the
Urbanizati
on Name
is
amongst
the
address
lines.
Description
“Extracted” from the
address lines and then
posted to the output
file.
77
1
Working With CODE-1 Plus in Dispatcher4
Table 39: Output Layout File Definition Field Labels Used
in Dispatcher4 (Part 3 of 5)
Predefined Name Field
Label
Purpose
Parameter
Description
County Name
Defines Output County
Name
CS OUT
25 characters
FIPS County Code
Defines FIPS County Code
CS OUT
3-digit code
Congressional District
Defines Congressional
District
CS OUT
2-digit code
ZIP Code
Defines Output ZIP Code
Z5 OUT
5 digits
ZIP+4 Code
Defines Output ZIP+4 Code
Z4 OUT
4 digits
Delivery Point Barcode
Defines Output ZIP+4 Code
and Add-on +2
Z4 OUT
6 digits
DPBC with Check Digit
Defines Output Add-on +2
and check digit
Z4 OUT
3 digits
Carrier Route Code
Defines Output Carrier
Route
Z4 OUT
4 characters —
alphanumeric
Extracted ZIP Code
Defines the location to
extract the input ZIp Code
CS ZIP
5 digits — used for
packed, binary, or
floating within address
line or field.
DPBC Add-on
Defines Output Add-on +2
Z4 OUT
2 digits
DPBC Add-on Check
Digit
Defines Output check digit
Z4 OUT
1 digit
Final ZIP Code Source
Defines Output source of
ZIP Code (return code)
Z5 OUT
1 character
RR/HC Route Type
Defines Output Route type:
RR, HC
AE OUT
Used for parsing
address elements.
RR/HC Route Number
Defines Output route
number
AE OUT
Used for parsing
address elements.
Box Number
Defines Output (PO) Box
number
AE OUT
Used for parsing
address elements.
House Number
Defines Output house
number
AE OUT
Used for parsing
address elements.
ZIP, ZIP+4, DPBC, CR-RT
NOTE: Do not use if
adding a MailStream
Plus step to your job.
Address Elements
78
Software Release 4.0.0/March 2015
Dispatcher4 Field Labels
1
Table 39: Output Layout File Definition Field Labels Used
in Dispatcher4 (Part 4 of 5)
Predefined Name Field
Label
Purpose
Parameter
Description
Pre-Directional
Defines Output leading
directional
AE OUT
Used for parsing
address elements.
Street Name
Defines Output street name
AE OUT
Used for parsing
address elements.
Street Suffix
Defines Output street suffix
AE OUT
Used for parsing
address elements.
Post Directional
Defines Output post
directional
AE OUT
Used for parsing
address elements.
Apartment Designator
Defines Output unit
designator: Apt, Ste, Flr,
etc.
AE OUT
Used for parsing
address elements.
Apartment Number
Defines Output unit number
AE OUT
Used for parsing
address elements.
Private Mail Box
Designator
Defines Output designator
Private Mail Box
AE OUT
Used for parsing
address elements.
Private Mail Box
Defines Output Private Mail
Box number
AE OUT
Used for parsing
address elements.
Normalized Primary
Address
Defines Output normalized
primary address line
AP OUT
Used for normalizing
(standardizing) nonmatched address
information.
Normalized Secondary
Address
Defines Output normalized
secondary address line
AP OUT
Used for normalizing
(standardizing) nonmatched address
information.
Dropped Primary Care
of
Defines Output dropped
c/o, ATTN: and MSC
address information
AP OUT
Used to store dropped
address information.
Dropped Secondary
Care of
Defines Output dropped
c/o, ATTN: and MSC
address information
AP OUT
Used to store dropped
address information.
Normalized Address Lines
Dropped Information
Return Codes
Working With CODE-1 Plus
79
1
Working With CODE-1 Plus in Dispatcher4
Table 39: Output Layout File Definition Field Labels Used
in Dispatcher4 (Part 5 of 5)
Predefined Name Field
Label
Return Codes
Purpose
Parameter
Description
Defines Output Return
Codes
AM OUT
(and
Return
Codes on
XX OUT
options)
Defines Output Return
Codes
AM OUT
AM2OUT
(and
Return
Codes on
XX OUT
options)
Line of Travel Numeric
Code
Defines the Line of Travel
numeric code
LOTOUT
4 digits
USPS Sequence Code
Defines the Line of Travel
sequence code
LOTOUT
1 character:
A(scending)
D(escending)
1-character Sequence
Code
Defines the Line of Travel
sequence code
LOTOUT
1 character
Hexidecimal
2-character Sequence
Code
Defines the Line of Travel
sequence code
LOTOUT
2 characters
Alphanumeric
Delivery Point
Validation RC
Defines Output DPV Return
Code
DPVOUT
1 character
Alphanumeric
Delivery Point
Validation CMRA
Defines Output DPV CMRA
Return Code
DPVOUT
1 character
Alphanumeric
DPV False/Positive
Flag
Defines Output False/
Positive Flag
DPVOUT
1 character
Alphanumeric
DPV Footnote Codes
Defines Output DPV
Footnote Codes
DPVOUT
1 character
Alphanumeric
Residential Flag
Defines the Residential
Flag (RDI processing)
DPVOUT
1 character
Alphanumeric
Business Flag
Defines the Business Flag
(RDI processing)
DPVOUT
1 character
Alphanumeric
Other Match Results
Other Match Results
Line of Travel
Delivery Point Validation
80
Software Release 4.0.0/March 2015
Dispatcher4 Field Labels
1
Output File Definition Field Labels
In some cases, the output Name field labels are different from the output ID field
labels. As shown below, the standardized address Name field is “Address with
Apartment” and the ID field is “Address 1.”
The table below lists the Output File Definition Field Labels for CODE-1 Plus.
Table 40: Output File Definition Field Labels (Part 1 of 4)
Predefined Name Field
Label
Predefined ID Field Label
Description
Standardized Address
Standardized Address with
Apartment
OR
Standardized Address
without Apartment
Working With CODE-1 Plus
Address 1
If INP Option used, the field labels
for Address lInes 1 through 6 (if
defined) will be retained on the
output file layout.
81
1
Working With CODE-1 Plus in Dispatcher4
Table 40: Output File Definition Field Labels (Part 2 of 4)
Predefined Name Field
Label
Apartment/PMB Number
(only)
Predefined ID Field Label
Description
Address 2
Address 3
Address 4
Address 5
Address 6
Standardized Firm
Standardized Firm Name
Firm Name
City and State
Standardized City/State
Line
City, State, ZIP
City, State, ZIP, ZIP+4 returned in
a single field.
Format: City ST ZIP-ZIP+4
Long City Name
City
Maximum of 28 characters
Short City Name
City
Maximum of 13 characters
State Abbreviation
State
2 characters
Urbanization Name
Urbanization Name
Extracted Urbanization
Name
Custom Field
County Name
Custom Field
FIPS County Name
Custom Field
Congressional District
Custom Field
Final ZIP Code Source
Custom Field
Extracted ZIP Code
Custom Field
ZIP, ZIP+4, DPBC, CR-RT
ZIP Code
ZIP Code
ZIP+4 Code
ZIP+4 Code
Delivery Point Barcode
Custom Field
4 digits
6 digits
NOTE: Do not use if adding a
MailStream Plus step to your job.
82
Software Release 4.0.0/March 2015
Dispatcher4 Field Labels
1
Table 40: Output File Definition Field Labels (Part 3 of 4)
Predefined Name Field
Label
Predefined ID Field Label
DPBC with Check Digit
DPBC with Check Digit
3 digits
DPBC Add-on
DPBC 2-digit Code
2 digits
DPBC Add-on Check Digit
DPBC Check Digit
1 digit
Final ZIP Code Source
Custom Field
1-character return code
Carrier Route Code
Carrier Route Code
4 characters
Description
Address Elements
RR/HC Route Type
Custom Field
RR/HC Route Number
Custom Field
Box Number
Custom Field
House Number
House Number
Pre-Directional
Custom Field
Street Name
Custom Field
Street Suffix
Custom Field
Post Directional
Custom Field
Apartment Designator
Custom Field
Apartment Number
Custom Field
Private Mail Box Designator
Custom Field
Private Mail Box
Custom Field
Normalized Address
Normalized Primary
Address
Address n or Custom
Field
Address line number or ID label
dependent on the number of
address lines and posting option.
Normalized Secondary
Address
Address n or Custom
Field
Address line number or ID label
dependent on the number of
address lines and posting option.
Dropped Primary Care of
Address n
Address line number dependent
on the number of address lines.
Dropped Secondary Care of
Address n
Address line number dependent
on the number of address lines.
Dropped Information
Working With CODE-1 Plus
83
1
Working With CODE-1 Plus in Dispatcher4
Table 40: Output File Definition Field Labels (Part 4 of 4)
Predefined Name Field
Label
Predefined ID Field Label
Description
Return Codes and Other Match Results
Name dependent on Return
Code
Custom Field
Name dependent on Return
Code
Custom Field
Line of Travel
Line of Travel Numeric
Code
Custom Field
4 digits
USPS Sequence Code
Custom Field
1 character
A(scending)
D(escending)
1-character Sequence Code
Custom Field
1 character
Hexidecimal
2-character Sequence Code
Custom Field
2 characters
Alphanumeric
Delivery Point Validation
Return Code
Custom Field
1 character
Delivery Point Validation
CMRA
Custom Field
1 character
Delivery Point Validation
False/Positive Flag
Custom Field
1 character
Delivery Point Validation
Footnote Codes
Custom Field
Up to 20 characters
Residential Flag
Custom Field
1 character
Business Flag
Custom Field
1 character
Delivery Point Validation
Output File Definition Field Labels for GeoCoding Plus
In some cases, the output Name field labels are different from the output ID field
labels. As shown below, the standardized address Name field is “FIPS County Code”
and the ID field is “Custom Field.”
84
Software Release 4.0.0/March 2015
Dispatcher4 Field Labels
1
The table on the following pages lists the Output File definition field labels for
Geographic Coding Plus within CODE-1 Plus.
Table 41: Output Layout File Definition Field Labels for Geographic
Coding Plus (Part 1 of 3)
Predefined Name Field
Label
Purpose
Parameter
Description
Geographic Coding Fields
Geographic Coding Return
Code
Defines the Geographic
Coding return code
G9 OUT
1 character
alphanumeric code
Census GEOCODE
Defines Geographic
Coding Census code
G9 OUT
12 digits
FIPS State Code
Defines the FIPS state
code
G9 OUT
2 digits
FIPS County Code
Defines the FIPS county
code
G9 OUT
3 digits
Census Tract
Defines the Census Tract
code
G9 OUT
6 digits
Census Block Group
Defines the Census Block
code
G9 OUT
1 digit
Working With CODE-1 Plus
FIPS = Federal
Information Processing
Standard
85
1
Working With CODE-1 Plus in Dispatcher4
Table 41: Output Layout File Definition Field Labels for Geographic
Coding Plus (Part 2 of 3)
Predefined Name Field
Label
Purpose
Parameter
Description
State Abbreviation
State Abbreviation
G9 OUT
2 character state code
County Name
Defines the county name
G9 OUT
20 characters
MSA Code
Defines MSA code
G9 OUT
4 digits
MSA = Metropolitan
Statistic Area)
MSA Name
Defines MSA name
G9 OUT
50 characters —
maximum
Latitude/Longitude
Defines the latitude/
longitude
G9 OUT
16 alphanumeric.
Latitude/Longitude Level
Defines the latitude/
longitude level
G9 OUT
1 character,
alphanumeric
Latitude/Longitude
Coordinate
Defines the latitude/
longitude coordinate
G9 OUT
20 alphanumeric.
Format: 7 digits, alpha,
7 digits, alpha
Format: 9 digits, alpha,
9 digits, alpha
Geographic Coding Plus Fields
Confidence Code
Defines the confidence
code
G9XOUT
4 digits
PRIZM Cluster Code
Defines the PRIZM
cluster code
G9XOUT
2 digits
PRIZM Cluster Name
Defines the PRIZM
cluster name
G9XOUT
20 characters —
maximum
PRIZM Social Group Code
Defines the PRIZM social
group code
G9XOUT
2 characters,
alphanumeric
PRIZM Social Group Name
Defines the PRIZM social
group name
G9XOUT
20 characters —
maximum
Place Code
Defines the place code
G9XOUT
5 digits
Place Name
Defines the place name
G9XOUT
20 characters —
maximum
MCD/CCD
Defines the MCD/CCD
code
G9XOUT
5 digits
GeoTAX Fields
86
MCD/CCD = Minor Civil
Division/Census County
Division
Software Release 4.0.0/March 2015
Dispatcher4 Field Labels
1
Table 41: Output Layout File Definition Field Labels for Geographic
Coding Plus (Part 3 of 3)
Predefined Name Field
Label
Purpose
Parameter
Description
Place Class Code
Defines the place class
code
G9XOUT
2 characters
Place Incorporated Flag
Defines the incorporated
flag
G9XOUT
1 character
Last Annexed Date
Defines the last annexed
date
G9XOUT
7 digits
Defines the last updated
date
G9XOUT
Defines the last verified
date
G9XOUT
GEOTAX Output Key
Defines the GEOTAX
output key
G9XOUT
9 characters
GEOTAX Return Code
Defines the GEOTAX
return code
G9XOUT
1 character
Last Updated Date
Last Verified Date
Working With CODE-1 Plus
Format: MMCCYY
7 digits
Format: MMCCYY
7 digits
Format: MMCCYY
87
1
88
Working With CODE-1 Plus in Dispatcher4
Software Release 4.0.0/March 2015
CHAPTER 2
Parameter Reference
This chapter is a comprehensive technical reference for each parameter. For each
parameter, we include the function, a picture, a table of all of the fields and possible
values, and an example.
NOTE: For any of the parameters that specify file positions and lengths, you can use
the open position to the left of the range indicated, if you have records which are
more than 999 bytes or field lengths that are greater than 99 bytes.
Pitney Bowes may require up to 80 bytes for the definition of our products
parameter records. If sequence numbers are posted in positions 73-80 of the
defined parameter records, then abnormal terminations may result when processing.
ADDRDF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
AE OUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
AM OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
AM2OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
AP OUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
AUXIL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
BYPEXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
CASSA1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
CASSA4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
CASSA7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
CHCKPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
CONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
CONFRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
CONTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
CR OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
CS OUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
CS ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Working With CODE-1 Plus
89
2
Parameter Reference
DPVIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DPVOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EXITOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FILEDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FIRMNM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G9 OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G9XOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G9ZIP9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HEADER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LACS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L CODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LISTID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LISTNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAILER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MOVE I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MOVE O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NTHSEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGESZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PGMNAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SA OUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SA2OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEQCHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STELNK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TESTIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UFTxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UHDxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Z4 OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Z5 OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
90
146
152
157
159
165
168
170
173
174
175
177
178
179
180
182
183
185
186
189
190
192
197
206
208
210
213
214
215
216
221
Software Release 4.0.0/March 2015
ADDRDF
2
ADDRDF
The required ADDRDF parameter is used to define the location, length, and format
of the addresses in the input record. This parameter comprises the following:
•
Format of the address information
•
Location and length of each address line or field
•
Location and length of the urbanization name field.
In this context, the term “field” means any continuous series of characters in the
input file. You can define a field to start at any position in the input file, and extend
fields for any length you choose. For example, you could specify that positions 100140 in the input file make up one field.
A line is also a continuous series of characters in the input file. The difference is that
CODE-1 Plus assumes that a line contains all of the information that would appear
on one line of an address label.
NOTE: If you specify that your input address is in lines, you should define the lines
in the order in which the USPS would like them to appear on a mailing label. In
other words, the first line (left-most) is the least significant, and the last line (rightmost) is the most significant.
CODE-1 Plus will treat the last line you define (that actually contains data) as the
primary address line unless you include the formatted City/State/ZIP in the last
line.
The length of an address cannot exceed 99 bytes.
Table 1: ADDRDF Parameter Fields (Part 1 of 3)
Position
Field Name
Description
Comments
1-6
KEYWORD
ADDRDF is the only acceptable entry.
Required.
8
ADDRESS FORMAT
Enter one of the following codes to
describe the format of the street address
information in the input record:
Required.
No default.
• M — A single line
• L — 2, 3, 4, 5, or 6 lines (with or
without city, state, and ZIP Code)
• F — 2, 3, 4, 5, or 6 fields.
10-12
Working With CODE-1 Plus
Location of
ADDRESS 1
Location of the first field or line.
Required.
No default.
91
2
Parameter Reference
Table 1: ADDRDF Parameter Fields (Part 2 of 3)
Position
Description
Comments
14-15
Length of
ADDRESS 1
Length of the first field or line.
Required.
No default.
17-19
Location of
ADDRESS 2
Location of the second field or line.
Optional.
No default.
21-22
Length of
ADDRESS 2
Length of the second field or line.
Optional.
No default.
24-26
Location of
ADDRESS 3
Location of the third field or line.
Optional.
No default.
28-29
Length of
ADDRESS 3
Length of the third field or line.
Optional.
No default.
31-33
Location of
ADDRESS 4
Location of the fourth field or line.
Optional.
No default.
35-36
Length of
ADDRESS 4
Length of the fourth field or line.
Optional.
No default.
38-40
Location of
ADDRESS 5
Location of the fifth field or line.
Optional.
No default.
42-43
Length of
ADDRESS 5
Length of the fifth field or line.
Optional.
No default.
45-47
Location of
ADDRESS 6
Location of the sixth field or line.
Optional.
No default.
49-50
Length of
ADDRESS 6
Length of the sixth field or line.
Optional.
No default.
52-54
Location of
INPUT
URBANIZATION
NAME
Location of the urbanization name in the
input record.
Optional.
No default.
Length of
INPUT
URBANIZATION
NAME
Length of the urbanization name in the
input record.
Location for
EXTRACTED
URBANIZATION
NAME
Storage location for the extracted (input)
urbanization name in the output record.
56-57
59-61
92
Field Name
NOTE: If the urbanization name can be
found among the address lines, enter a U
in position 52. If you enter a U, CODE-1
Plus attempts to locate the name in the
locations you have already identified for
the address.
Optional.
No default.
NOTE: If you put a U in position 52, do not
enter a value in this field.
Optional.
No default.
Software Release 4.0.0/March 2015
ADDRDF
2
Table 1: ADDRDF Parameter Fields (Part 3 of 3)
Position
Field Name
Description
Comments
63-64
Length of
EXTRACTED
URBANIZATION
NAME
Length of the extracted (input)
urbanization name in the output record.
Optional.
No default.
65
LEFT JUSTIFY
Code indicating whether to left justify:
Optional.
Default is
blank.
• Contents of the primary and
secondary address lines
• Firm name (if assigned)
• Urbanization name (if assigned)
Enter one of the following codes:
• L — Left justify all fields listed above.
• Blank — Do not left justify the fields
listed above.
Working With CODE-1 Plus
93
2
Parameter Reference
AE OUT
The optional AE OUT parameter defines the location on the output file to store the
individual address elements.
Notice that you must specify a length for the street name element and the Private
Mailbox Number only. Each of the other elements have predetermined lengths. The
following figure shows the different address elements.
4235
House
Number
RR
Rural Route/
Highway
Route Type
PMB
Private
Mailbox
Designator
N
MAIN
Leading
Directional
123
ST
Street
Name
BOX
Rural Route/
Highway
Contract
Number
NW
Suffix
Trailing
Directional
STE
100
Apartment
Designator
Apartment
Number
19
Rural/Route Highway
Contract or PO Box
Number
456
Private
Mailbox
Number
NOTE: These elements are stored from the base street name, not the alias, if you
have specified Y in column 51 of the SA OUT parameter.
Table 2: AE OUT Parameter Fields (Part 1 of 3)
Position
94
Field Name
Description
Comments
1-6
KEYWORD
AE OUT is the only acceptable entry.
Required.
8-10
Location for
HOUSE NUMBER
Location on the output record for the
left-justified 10-character house number.
Optional.
No default.
12-14
Location for
LEADING
DIRECTIONAL
Location on the output record for the
left-justified 2-character leading directional.
Optional.
No default.
16-18
Location for
STREET NAME
Location on the output record for the
left-justified street name.
Optional.
No default.
Software Release 4.0.0/March 2015
AE OUT
2
Table 2: AE OUT Parameter Fields (Part 2 of 3)
Position
Field Name
Description
Comments
20-21
Length of
STREET NAME
Length of the street name on the output
record (the maximum is 40).
Optional.
No default.
23-25
Location for
SUFFIX
Location on the output record for the
left-justified 4-character street suffix.
Optional.
No default.
27-29
Location for
TRAILING
DIRECTIONAL
Location on the output record for the
left-justified 2-character trailing directional.
Optional.
No default.
31-33
Location for
APARTMENT
DESIGNATOR
Location on the output record for the
left-justified 4-character apartment
designator.
Optional.
No default.
35-37
Location for
APARTMENT
NUMBER
Location on the output record for the
left-justified 8-character apartment number.
Optional.
No default.
39-41
Location for
RURAL ROUTE/
HIGHWAY
CONTRACT
ROUTE TYPE
Location on the output record for the
2-character rural route/highway contract
route type code.
Optional.
No default.
43-45
Location for
RURAL ROUTE/
HIGHWAY
CONTRACT
NUMBER
Location on the output record for the
left-justified 3-character rural route/highway
contract route number.
Optional.
No default.
47-49
Location for
BOX NUMBER
Location on the output record for the
left-justified 10-character box number.
Optional.
No default.
51
DISPOSITION
INDICATOR
Code indicating what should be stored in
cases where standardized elements could not
be stored (because no match was found).
Enter one of the following codes:
Optional.
Default is B.
• B — Store blanks.
• M — Store elements from normalized
address merging secondary address line
elements with primary address line
elements. In cases where an element
appears in both the primary and secondary
address lines, use the element from the
primary address line.
• N — Store elements from normalized
address using the primary address line
only.
• X — Store nothing.
Working With CODE-1 Plus
95
2
Parameter Reference
Table 2: AE OUT Parameter Fields (Part 3 of 3)
Position
53-55
Field Name
Location for
PRIVATE
MAILBOX
DESIGNATOR
Description
Comments
Location on the output record for the
left-justified 4-character Private Mailbox
Designator.
Optional.
No default.
• PMB — Standard Private Mailbox
Designator
• # — Nonstandard Private Mailbox
Designator
NOTE: In order to have a designator in your
output record, you must specify a length and
location for your Private Mailbox Number in
positions 57-59 and 61-62.
57-59
Location for
PRIVATE
MAILBOX
NUMBER
Location on the output record for the Private
Mailbox Number.
Required if
location
information
exists in
positions
53-55.
No default.
61-62
Length of
PRIVATE
MAILBOX
NUMBER
Length of the Private Mailbox Number on the
output record (the maximum is 16
characters).
Required if
data exists in
positions
57-59.
No default.
64
PRIVATE
MAILBOX
DESIGNATOR/
NUMBER
STORAGE OPTION
Enter one of the following codes:
Optional.
Default is
blank.
• X — Store all Private Mailbox Designator/
Numbers
• Blank — Store only Standard Private
Mailbox Designator/Numbers
NOTE: If X is chosen, a non-CASS certified
configuration will be created. No PS Form
3553 will be generated.
NOTE: CODE-1 Plus only produces a standardized address if an SA OUT
parameter is used to store a standardized address. Therefore, if you request
elements of the standardized address on the AE OUT parameter, you must also
complete an SA OUT parameter.
96
Software Release 4.0.0/March 2015
AM OUT
2
AM OUT
The optional AM OUT parameter tells CODE-1 Plus where to store the return codes
on the output record.
The address matching return codes provide you with the results of the attempt to
match the records against the information in the CODE-1 Plus database. These codes
are very useful when you are analyzing the results you received from CODE-1 Plus.
If you do not specify a location for a return code, CODE-1 Plus does not store that
return code on the output record.
Delivery Sequence File (DSF2) footnotes are 2-character, USPS-defined codes that
represent the changes that were made to the input address during the matching
process. Up to 50 of these codes can be stored by CODE-1 Plus for each record,
resulting in a 100-character output field. After CODE-1 Plus finishes processing, you
can run your output file through a delivery sequence program (not provided by
Pitney Bowes) to sort your records into delivery sequence. The delivery sequence
program will look at these footnotes when sorting the records.
Table 3: AM OUT Parameter Fields (Part 1 of 6)
Position
Field Name
Description
Comments
1-6
KEYWORD
AM OUT is the only acceptable entry.
Required.
8-10
Location for
USPS RECORD
TYPE CODE
Location on the output record for the
1-character record type code. One of the
following codes is stored:
Optional.
No default.
• Blank — No match found.
• F — Firm
• G — General delivery
• H — High rise (apartment complex)
• P — Post office box
• R — Rural route or highway contract
• S — Normal street address
NOTE: CODE-1 Plus will not produce the
USPS 3553 form if the USPS Record Type
Code is posted.
Working With CODE-1 Plus
97
2
Parameter Reference
Table 3: AM OUT Parameter Fields (Part 2 of 6)
Position
12-14
Field Name
Location for
GENERAL
RETURN CODE
Description
Comments
Location on the output record for the
1-character general return code. One of the
following codes is stored.
Optional.
No default.
• Blank — Successful address match
attempt.
• A — Apartment number missing or not
found in database, and an apartment-level
match was required.
• B — Insufficient (or blank) address
information.
NOTE: When CODE-1 Plus determines
address information is insufficient (or
blank) and returns a “B” for a specific
address record, the record is skipped.
• 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 in database.
16-18
Location for
DIRECTIONAL
RETURN CODE
Location on the output record for the
1-character directional return code. One of
the following codes is stored:
Optional.
No default.
• Blank — The directional match was
successful, or no address match was
found.
• N — No directional was found on the input
address, but a directional was present on
the database.
• F — The directional was correct, but was in
the wrong location (e.g., trailing directional
should have been leading directional).
• D — The directional does not match the
database.
• L — New address obtained from LACS
processing.
98
Software Release 4.0.0/March 2015
AM OUT
2
Table 3: AM OUT Parameter Fields (Part 3 of 6)
Position
20-22
Field Name
Location for
SUFFIX
RETURN CODE
Description
Location on the output record for the
1-character suffix return code. One of the
following codes is stored:
Comments
Optional.
No default.
• Blank — The suffix match was successful,
or no
address match was found.
• L — New address obtained from LACS
processing.
• N — No suffix was found on the input
address, but a suffix was present on the
database.
• S — The suffix does not match the
database.
24-26
Location for
APARTMENT
RETURN CODE
Location on the output record for the
1-character apartment return code. One of
the following codes is stored:
Optional.
No default.
• Blank — No address match was found, or
the apartment (or lack thereof) matches
the database.
• L — New address obtained from LACS
processing.
• N — No apartment was found on the input
address, but an apartment was present on
the database at the street address.
• A — The apartment does not match the
database.
• F — Suite number appended due to a firm
name match.
28-30
Location for
FIRM NAME
RETURN CODE
Location on the output record for the
1-character firm name return code. One of
the following codes is stored:
Optional.
No default.
• Blank — No address match was found, or
the firm name match successful, or no
input firm name was found.
• F — The input firm name does not match
the database.
• L — New address obtained from LACS
processing.
• M — A firm name was present in the input
record, but there were no firm names on
the database for the matched address.
Working With CODE-1 Plus
99
2
Parameter Reference
Table 3: AM OUT Parameter Fields (Part 4 of 6)
Position
32-34
Field Name
Location for
OVERALL
PROBABLE
CORRECTNESS
CODE
Description
Comments
Location on the output record for the
1-character overall probability of
correctness. One of the following codes is
stored:
Blank
Optional.
No default.
No match was found.
• 0 — The match is exact.
• 1-8 — The match has an intermediate
probability of correctness on a sliding
scale.
• 9 — The match is least likely to be correct.
36-38
Location for
ALTERNATE
ADDRESS
SCHEME
INDICATOR
Location on the output record for the type of
alternate address scheme to use to obtain a
match. One of the following codes is stored:
Optional.
No default.
• Blank — No alternate address scheme
used.
• D — Delivery point alternate logic used.
• E — Enhanced high rise alternate match
logic used.
• L — New address obtained from LACS
processing.
• U — Unique ZIP Code logic used.
40-42
Location for
STREET NAME
MATCH SCORE
A 1-digit score, on a scale of 0 - 9, reflecting
the closeness of the street-name match (after
transformations by the analyzer, if any),
where 0 indicates an exact match and 9
indicates the least likely match. If no match
was found, this field is blank.
Optional.
No default.
44-46
Location for
FIRM NAME
MATCH SCORE
Location on the output record for the
1-character firm name match score. This
number represents the number of “errors”
that were found when matching the firm name
to the database.
Optional.
No default.
48-50
Location for
ADDRESS
PROBABLE
CORRECTNESS
CODE
Location on the output record for the
1-character address probability of
correctness. One of the following codes is
stored:
Optional.
No default.
• Blank — No match was found.
• 0 — The match is most likely to be correct.
• 1-8 — The match has an intermediate
probability of correctness on a sliding
scale.
• 9 — The match is least likely to be correct.
• L — New address obtained from LACS
processing.
100
Software Release 4.0.0/March 2015
AM OUT
2
Table 3: AM OUT Parameter Fields (Part 5 of 6)
Position
52-54
Field Name
Location for
DELIVERY
SEQUENCE
FILE
FOOTNOTES
Description
Location on the output record for up to 50
2-character delivery sequence footnotes.
Comments
Optional.
No default.
• AA — The record matched the ZIP+4
database the CODE-1 Plus database.
• A1 — No match was found.
• A2 — The 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 — The input address matched to DPV
(all components).
• CC — The input address primary number
matched to DPV but secondary number did
not match (present but invalid).
• D — City name or state was changed.
• E — Primary address was changed.
• F — Secondary address was changed.
• F1 — Input address matched to a military
ZIP Code.
• G1 — Input address matched to a General
Delivery Address.
• H — ZIP Code was changed.
• J — City, state, and ZIP Code 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.
• M1 — Missing street number.
• M2 — Address not found.
• M3 — No such primary number.
• 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.
• Q1 — Missing PO Box number.
• Q2 — PO Box number not found on file.
NOTE: Although there are currently only 25
footnote codes defined, CODE-1 Plus uses
the entire 100-character array, back-filling
with spaces as necessary.
Working With CODE-1 Plus
101
2
Parameter Reference
Table 3: AM OUT Parameter Fields (Part 6 of 6)
Position
56-58
Field Name
Location for
OUTPUT ZIP
CODE STATUS
Description
Comments
Location on the output record for the
1-character code indicating the status of the
INPUT ZIP Code. One of the following codes is
stored:
Optional.
No default.
• A — Altered—the original ZIP Code was
altered via an address match.
• B — Blank—a unique address match could
not be obtained; the original ZIP Code was
blank.
• C — Confirmed—the input ZIP Code was
confirmed by an address match.
• I — Invalid -- No match could be obtained;
the output ZIP code contains blanks
because the input ZIP code was invalid.
• O — Original—a unique address match
could not be obtained; the original ZIP Code
was kept.
• 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.
60-62
Location for
ALTERNATE/
BASE
INDICATOR
Location on the output record for a
1-character code indicating whether the input
address matched a ZIP+4 base record or a
ZIP+4 alternate record. One of the following
codes is stored:
Optional.
No default.
• A — Input address matched an alternate
ZIP+4 record.
• B — Input address matched a base ZIP+4
record.
102
64-66
Location for
LAST LINE
NUMBER
Location on the output file for the USPS
6-character last line number from the output
ZIP+4 Code.
Optional.
No default.
68-70
Location for
FINANCE
NUMBER
Location on the output file for the USPS
6-character finance number from the output
city.
Optional.
No default.
72-74
Location for
250 BYTES OF
ADDITIONAL
INFORMATION
FOR VERIMOVE
Location on the output file to attach 250 bytes
of additional information codes to your output
file. This parameter was designed for use with
the Pitney Bowes VeriMove move update
product.
Optional.
No default.
Software Release 4.0.0/March 2015
AM2OUT
2
AM2OUT
The optional AM2OUT parameter, a continuation of the AM OUT parameter, tells
CODE-1 Plus where to store the various return codes on the output record.
The USPS considers a match to a default record when the input address matches to a
high rise default record OR when the input address had the potential to match a
USPS high rise record, but is either missing an input secondary number or does not
match the USPS high rise records and no high rise default record exists in the
database. When this second circumstance occurs, the ZIP+4 code is assigned
according to the USPS street record type. This is also reported as a high rise default
match.
For rural route and military addresses with box numbers, the default is set when the
input box number does not match the box range on the USPS database.
Table 4: AM2OUT Parameter Fields (Part 1 of 3)
Position
Field Name
Description
Comments
1-6
KEYWORD
AM2OUT is the only acceptable entry.
Required.
8-10
Location for
HIGH RISE DEFAULT
The output location for the High Rise
Default. One of the following codes is
stored:
Optional.
No default.
• H — Record matched to a High Rise
Default record.
• Blank — No match was made.
Matched record was not a default
record.
12-14
Location for
RURAL ROUTE
DEFAULT
The output location for the Rural Route
Default. One of the following codes is
stored:
Optional.
No default.
• R — Record matched to a Rural Route
Default record.
• Blank — No match was made.
Matched record was not a default
record.
16-18
Location for
MILITARY DEFAULT
The output location for the Military
Default. One of the following codes is
stored:
Optional.
No default.
• M — Record matched to a Military
Default record.
• Blank — No match was made.
Matched record was not a default
record
Working With CODE-1 Plus
103
2
Parameter Reference
Table 4: AM2OUT Parameter Fields (Part 2 of 3)
Position
20-22
Field Name
Location for
UNIQUE ZIP CODECITY/STATE
CORRELATION
RETURN CODE
Description
Comments
The output location for the Unique ZIP
Code-City/State Correlation Return
Code. One of the following codes is
stored:
Optional.
No default.
• U — The original ZIP Code was unique
and did not correspond to the input
city/state.
• Blank — Input ZIP Code was either not
unique or was unique and
corresponded to the input city/state.
28-30
32-34
Location for
AUXILIARY FILE
NAME MATCH
The output location for the Auxiliary File
Name Match code. Only one code option:
Location for
SECONDARY
COMPONENT
PROCESSING
INDICATOR
The output location for the Secondary
Component Processing Indicator; one of
the following codes is stored:
Optional.
• 1 — Early Warning System (EWS) File.
Optional.
• Blank — No multiple secondary
component logic used.
• E — Exact match.
• S — Multiple Secondary Match logic
used.
36-38
Location for
OVERRIDE CITY
NAME INDICATOR
The output location for the Override City
Name refers to the city name for the
Preferred Last Line Key (PLL) from the
USPS ZIP+4 File. The Default City Name
refers to the city name for the PPL Key on
the USPS City/State File.
Optional.
The output location for the Override City
Name Indicator. One of the following
codes is stored:
• Blank — Default City Name stored.
• O — Override City Name stored.
40-42
Location for
INPUT CITY TYPE
INDICATOR
The output location for the Indicator of
Input city type:
Optional.
• P — Primary city
• S — Secondary city
• V — Vanity city.
44-46
104
Location for
MILITARY ADDRESS
INDICATOR
The output location for the Indicator of
military address:
Optional.
• M — Indicates a military address.
Software Release 4.0.0/March 2015
AM2OUT
2
Table 4: AM2OUT Parameter Fields (Part 3 of 3)
Position
48-50
Field Name
Location for
ESM INDICATOR
Description
The output location for the Indicator that
enhanced street matching (ESM) or all
street matching (ASM) was performed for
matching:
Comments
Optional.
• Blank — No ASM or ESM performed.
• A — Matched using All Street Matching
(matched misspelled first letter)
• F — ASM performed but no match
found
• M — Matched using ESM
• P — ESM performed but no match
found.
52-54
Location for
LACSLink RETURN
CODE
The output location for the Indicator of
the success of the LACSLink process:
Optional.
• Blank — No LACS processing
occurred.
• A — LACS record match
• 00 — No match
• 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.
56-58
Location for
LACSLink INDICATOR
The output location for the Indicator of
whether a table was matched:
Optional.
• 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.
60-62
Location for Street
Default Flag
The output location for the Street Default
flag:
Optional.
No default.
• Blank — Record matched is not a
Street Default record.
• S — Record is matched to a Street
Default record.
Working With CODE-1 Plus
105
2
Parameter Reference
AP OUT
Optional. The AP OUT parameter identifies where, on the output file, to store the
information that was dropped during the analysis process, as well as the normalized
address lines. This parameter defines the following:
•
Format, location, and length of additional input data
•
Format, location, and length of extra data from the matcher (unmatched data)
•
Conditions under which to store the first normalized address line
•
Location and length of the first normalized address line
•
Conditions under which to store the second normalized address line
•
Location and length of the second normalized address line
•
Location and length of the “care of” information dropped from the parsed address
lines
•
Type of address normalization
Normalized address information is formatted to conform to USPS conventions.
Dropped address information is data that CODE-1 Plus ignored during the analysis
and matching process.
106
Software Release 4.0.0/March 2015
AP OUT
2
Table 5: AP OUT Parameter Fields (Part 1 of 6)
Position
Field Name
Description
Comments
1-6
KEYWORD
AP OUT is the only acceptable entry.
Required.
8
Format of EXTRA
DATA IN OUTPUT
RECORD
This field defines how two types of extra
data display in the output record.
Optional.
Default is F.
• Additional input data - Any information
that is defined on the input address
lines but is not sent to the matcher for
processing is identified as additional
input data.
• Unmatched data - Any information
passed to the matcher that is not used
in the matching process is identified as
unmatched data.
Enter one of the following codes:
• F - Fixed length format. Extra data will
be posted “as is” in eleven output
fields:
–
Six 100-byte length fields will
contain additional input data
(information that is defined on the
input address lines but is not sent
to the matcher for processing).
–
Five 100-byte length fields will
contain unmatched data
(information passed to the matcher
that was not used in the matching
process).
• C - Concatenated format.
Additional input data (information that
is defined on the input address lines
but is not sent to the matcher for
processing) is concatenated and
written into one field that:
–
Starts in the location specified in
position 10 of this parameter.
–
Is separated by the character
specified in position 26 of this
parameter.
Any information passed to the matcher
that is not used in the matching
process is identified as unmatched
data. Unmatched data is concatenated
and written into one field that:
Working With CODE-1 Plus
–
Starts in the location specified in
position 18 of this parameter.
–
Is separated by the character
specified in position 26 of this
parameter.
107
2
Parameter Reference
Table 5: AP OUT Parameter Fields (Part 2 of 6)
Position
Field Name
Description
Comments
10-12
Location for
ADDITIONAL INPUT
DATA
Location on the output record for
additional input data. (Any information
that is defined on input address lines but
is not sent to the matcher for processing
is identified as additional input data.)
Optional.
No default.
14-16
Length of
ADDITIONAL INPUT
DATA
Length of the additional input data
specified in position 10 of this parameter.
Optional.
Default is 600.
• If you specify F in position 8 and a value
other than 600 in this field, CODE-1
Plus generates an error and stops
processing.
• If you specify C in position 8, CODE-1
Plus truncates any data posted beyond
the length specified here.
18-20
Location for EXTRA
DATA FROM
MATCHER
Location on the output record for extra
data from the matcher. (Any information
passed to the matcher that is not used in
the matching process is identified as
unmatched data.)
Optional.
No default.
22-24
Length of EXTRA
DATA FROM
MATCHER
Length of output extra data from the
matcher (unmatched data) specified in
position 18.
Optional.
Default is 500.
• If you specified F in position 8 of this
parameter and some value other than
500 is posted in this field, CODE-1 Plus
generates an error and stops
processing.
• If you specified C in position 8 of this
parameter, CODE-1 Plus truncates any
data posted beyond the length specified
here.
26
DATA SEPARATOR
If you specified C in position 8 of this
parameter, specify a character to
separate the additional input data or the
extra data from the matcher (unmatched
data).
Optional.
Default is
semicolon “;”.
30
Storage conditions
— NORMALIZED
PRIMARY ADDRESS
LINE
Conditions under which the normalized
primary address line should be stored.
Enter one of the following codes:
Optional.
Default is X.
• A — Store for all records.
• X — Store only when standardized
address is not stored.
32-34
108
Location for
NORMALIZED
PRIMARY ADDRESS
LINE
Location on the output record for the
normalized primary address line.
Optional.
No default.
Software Release 4.0.0/March 2015
AP OUT
2
Table 5: AP OUT Parameter Fields (Part 3 of 6)
Position
Field Name
Description
Comments
36-37
Length of
NORMALIZED
PRIMARY ADDRESS
LINE
Length of the normalized primary address
line.
Optional.
No default.
39
Storage conditions
— NORMALIZED
SECONDARY
ADDRESS LINE
Conditions under which the normalized
secondary address line should be stored.
Enter one of the following codes:
Optional.
Default is X.
• A — Store for all records.
• D — Store dropped dual address from
matched address.
• X — Store only when standardized
address is not stored.
41-43
Location for
NORMALIZED
SECONDARY
ADDRESS LINE
Location on the output record for the
normalized secondary address line.
Optional.
No default.
45-46
Length of
NORMALIZED
SECONDARY
ADDRESS LINE
Length of the normalized secondary
address line.
Optional.
No default.
Working With CODE-1 Plus
109
2
Parameter Reference
Table 5: AP OUT Parameter Fields (Part 4 of 6)
Position
48-50
Field Name
Location for
DROPPED
PRIMARY “CARE
OF” DATA
Description
Comments
Location on the output record for the
“Care of” data dropped from the primary
address line. Valid "Care of" data
includes:
Optional.
No default.
• CO
• C/O
• C/O/
• ATTN
• %
• MC:
• MS:
• MAILSTOP
• MAIL STOP
• CAMPUS BOX
• CAMPUS BX
• COLLEGE BOX
• HALL:
• DORM:
• LEAVE ON PORCH
• REAR ENTRANCE
• CIMS:
• BLDG:
• BLD:
• FL:
• FLR:
NOTE: All "Care of" prefixes must be
separated by a space from the content
(e.g. C/O Mary, not C/OMary or
"DORM: 123", not "DORM:123").
52-53
110
Length of
DROPPED
PRIMARY “CARE
OF” DATA
Length of the "care of" data dropped from
the primary address line.
Optional.
No default.
Software Release 4.0.0/March 2015
AP OUT
2
Table 5: AP OUT Parameter Fields (Part 5 of 6)
Position
55-57
Field Name
Location for
DROPPED
SECONDARY “CARE
OF” DATA
Description
Location on the output record for the
“Care of” data dropped from the
secondary address line. Valid "Care of"
data includes:
Comments
Optional.
No default.
• CO
• C/O
• C/O/
• ATTN
• %
• MC:
• MS:
• MAILSTOP
• MAIL STOP
• CAMPUS BOX
• CAMPUS BX
• COLLEGE BOX
• HALL:
• DORM:
• LEAVE ON PORCH
• REAR ENTRANCE
• CIMS:
• BLDG:
• BLD:
• FL:
• FLR:
NOTE: All "Care of" prefixes must be
separated by a space from the content
(e.g. C/O Mary, not C/OMary or
"DORM: 123").
59-60
Working With CODE-1 Plus
Length of
DROPPED
SECONDARY “CARE
OF” DATA
Length of the “care of” data dropped from
the secondary address line.
Optional.
No default.
111
2
Parameter Reference
Table 5: AP OUT Parameter Fields (Part 6 of 6)
Position
70
Field Name
NORMALIZATION
TYPE (No match)
Description
Comments
Code indicating whether all address types
or only selected address types should be
normalized. The selected address types
are the following: “GENERAL DELIVERY”
keywords, PO BOX keywords, and RR/HC
keywords.
• Blank — Normalize specified address
line regardless of address type.
Optional.
Default is
blank.
If X is selected,
position 19 of
SA OUT must
be I.
• X — Normalize select address types
otherwise return input.
112
Software Release 4.0.0/March 2015
AP OUT
2
Example of Storing Additional Input Data/Unmatched Data - Fixed Format
The following is an example that stores the additional input data and unmatched data
to the output (COK) file in a fixed format. The AP OUT parameter looks like this:
....5...10....5...20....5...30....5...40....5...50....5...60....5...70....5...80
AP OUT F 701
1301
Where:
AP OUT position 8 = F (Fixed length format). Extra data will be posted “as is” in eleven
output fields (six additional input data fields and five unmatched data fields).
Additional input data is stored in position 701 for the default length of 600.
Unmatched data is stored in position 1301 for the default length of 500.
Input Address:
GROUP 1
ATTN ALICE ROSE SMITH
VILLAGE LOCALE PROPERTY
4200 PARLIAMENT PL STE 600 PO BOX 8511
6 W GLEN ST SUITE 201
LANHAM MD 20706
COK File - Additional Input Data:
Example of additional input data stored in position 701 for the default length of 600:
..701.. … ..801..
…
ATTN ALICE ROSE SMITH
..901..
…
VILLAGE LOCALE PROPERTY
COK File - Unmatched Data:
Example of unmatched data stored in position 1301 for the default length of 500:
..1301.. …
..1401..
PO BOX 8511
…
..1501..
6 W GLEN ST SUITE 201
NOTE: All data used in this example is for illustration purposes only and should
not be interpreted as actual USPS address data.
Working With CODE-1 Plus
113
2
Parameter Reference
Example of Storing Additional Input Data/Unmatched Data - Concatenated
Format
The following is an example that stores the additional input data and unmatched data
to the output (COK) file in concatenated format using the default semicolon as the
data delimiter. The AP OUT parameter looks like this:
....5...10....5...20....5...30..
AP OUT C 701 4001101 400
Where:
AP OUT position 8 = C (Concatenated format).
Additional input data is stored in position 701 for a length of 400.
Unmatched data is stored in position 1101 for a length of 400.
Input Address:
GROUP 1
ATTN ALICE ROSE SMITH
VILLAGE LOCALE PROPERTY
4200 PARLIAMENT PL STE 600 PO BOX 8511
6 W GLEN ST SUITE 201
LANHAM MD 20706
COK File - Additional Input Data:
Example of additional input data stored in position 701 for a length of 400:
..701..
;ATTN ALICE ROSE SMITH;VILLAGE LOCALE PROPERTY OWNERS;…
COK File - Unmatched Data:
Example of unmatched data stored in position 1101 for a length of 400:
..1101...
PO BOX 8511;6 W GLEN ST SUITE 201;…
NOTE: All data used in this example is for illustration purposes only and should
not be interpreted as actual USPS address data.
114
Software Release 4.0.0/March 2015
AUXIL1
2
AUXIL1
The optional AUXIL1 parameter identifies the presence of an auxiliary reference file
for matching purposes. This file must be preprocessed through the Pitney Bowessupplied C1AUXBLD program (using the specified Pitney Bowes input format). There
is flexibility in the record size, allowing for additional user-defined data. For more
information on using the C1AUXBLD program, refer to Chapter 7, "Auxiliary File
Processing".
Table 6: AUXIL1 Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
AUXIL1 is the only acceptable entry.
Required.
70
Location of
FILE
Code indicating where to write the
auxiliary file in the output:
Optional
Default is N.
• N — Write record to the NCO file.
• C — Write record to the COK file.
Working With CODE-1 Plus
115
2
Parameter Reference
BYPEXP
The optional BYPEXP parameter indicates whether to override an expired database.
This parameter only takes effect when the database is truly expired, that is, the
database is beyond the USPS grace period as defined in DMM 708. If your CODE-1
Plus database is expired and you use this parameter, CODE-1 Plus will not produce a
USPS Form 3553.
NOTE: It is very important to use a current CODE-1 Plus database. The BYPEXP
parameter is provided for use in an emergency situation only and should not be
used in “normal” processing.
Table 7: BYPEXP Parameter Fields
Position
1-6
116
Field Name
KEYWORD
Description
Comments
BYPEXP is the only acceptable entry.
Required.
Software Release 4.0.0/March 2015
CASSA1
2
CASSA1
The optional CASSA1 parameter tells CODE-1 Plus to override the CASS
certification data as it appears in box A1 of USPS Form 3553. This allows you to
CASS-certify CODE-1 Plus and use your own company name and/or software name
and version number.
NOTE: Using this parameter will invalidate the USPS Form 3553 if you have not
previously received a CASS certificate from the USPS for the vendor name and
software name.
Using the CASSA1 parameter with no values will cause a parameter error. The
software version number must be presented in the V.RR.MM format, including the
periods. The software version number in box A1 of USPS Form 3553 is very
specific and cannot be modified. This format is a USPS requirement.
If you specify a new software name, the new name will replace the CODE-1 Plus
product name on all report headers with the exception of the parameter Listing
report and the Execution Log. Any other information can be added to the report
heading by using the UHDxx and UFTxx parameters.
NOTE: Your particular licensing agreement may not permit your company to
certify the CODE-1 Plus product under your company name. See your software
licensing agreement for permitted scope and use of the product.
Table 8: CASSA1 Parameter Fields (Part 1 of 2)
Position
1-6
Working With CODE-1 Plus
Field Name
KEYWORD
Description
CASSA1 is the only acceptable entry.
Comments
Required.
117
2
Parameter Reference
Table 8: CASSA1 Parameter Fields (Part 2 of 2)
Position
8-32
Field Name
Description
Comments
CASS-CERTIFIED
COMPANY NAME
CASS-certified company name as it
appears on your CASS certificate (up to
25 characters).
34-63
CASS-CERTIFIED
SOFTWARE NAME
CASS-certified software name as it
appears on your CASS certificate (up to
30 characters).
65-71
CASS-CERTIFIED
SOFTWARE
VERSION NUMBER
CASS-certified software version
number, in V.RR.MM format. CASS
requires the following information:
• V — Version number
• R — Release number
These three
fields are all
optional.
However, you
must fill in at
least one field, or
an error will
occur. Any field
not filled in will
retain its current
Pitney Bowes
value.
• M — Modification number
118
Software Release 4.0.0/March 2015
CASSA4
2
CASSA4
The optional CASSA4 parameter allows you to override the Z4CHANGE certification
data as it appears in boxes A4 - A5 of the USPS Form 3553. For more information on
Z4CHANGE certification, refer to Chapter 4, "Using the Z4CHANGE Option".
Table 9: CASSA4 Parameter Fields
Position
Field Name
Description
1-6
KEYWORD
CASSA4 is the only acceptable entry.
8-32
Z4CHANGECERTIFIED
COMPANY NAME
Z4CHANGE-certified company name as
it is to appear on your USPS certificate
(up to 25 characters).
Z4CHANGECERTIFIED
SOFTWARE NAME
and VERSION
NUMBER
Z4CHANGE-certified software name as it
is to appear on your USPS certificate (up
to 30 characters) and Z4CHANGEcertified software version number in
V.RR.MM format.
34-67
• V — Version number
• R — Release number
Comments
Required.
These two fields
are optional.
However, you
must fill in at
least one field, or
an error will
occur. Any field
not filled in will
retain its current
Pitney Bowes
value.
• M — Modification number
Working With CODE-1 Plus
119
2
Parameter Reference
CASSA7
The optional CASSA7 parameter allows you to override LOT certification data as it
appears in boxes A7 - A8 of the USPS Form 3553. For more information on LOT
certification, refer to Chapter 5.
Table 10: CASSA7 Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
CASSA7 is the only acceptable entry.
8-32
ELOT-CERTIFIED
COMPANY NAME
LOT-certified company name as is to
appear on your USPS certificate (up to 25
characters).
ELOT-CERTIFIED
SOFTWARE NAME
LOT-certified software name as it is to
appear on your USPS certificate (up to 30
characters). and LOT-certified software
version number in V.RR.MM format.
34-67
• V — Version number
• R — Release number
• M — Modification number
120
Required.
These two fields
are optional.
However, you
must fill in at
least one field, or
an error will
occur. Any field
not filled in will
retain its current
Pitney Bowes
value.
Software Release 4.0.0/March 2015
CHCKPT
2
CHCKPT
The optional CHCKPT parameter specifies to take a checkpoint every n records
(where n is a number you specify) so that if your job is terminated for any reason, you
can restart the job from the last successful checkpoint, instead of running the entire
job again. A checkpoint is simply the number of records processed up to that point.
For example, if you take a checkpoint every 500 records, and your job terminates in
the middle, you could look at the checkpoint file and determine the last checkpoint
taken. If the last checkpoint was 47,500, you would know that you could skip the first
47,500 records when you restarted your job.
NOTE: This parameter is only used in IBM mainframe environments. Refer to the
IBM z/OS/DFP Checkpoint/Restart Manual for details on using checkpoints.
Checkpoints cannot be issued using CBUF processing of VSAM files (shareoptions
3,3). You must ensure that your CODE-1 Plus database is defined with
shareoptions specified as (1,3) or (2,3).
z/OS Checkpoints
You must make modifications to your z/OS JCL if you are using the CHCKPT
parameter. Define the checkpoint file with a C1BMCHK DD statement. To have your
checkpoints written serially to the file, specify DISP=MOD. To store only the latest
checkpoint, specify DISP=NEW.
NOTE: If you use DISP=NEW to save only the latest checkpoint, and for some
reason a checkpoint cannot be taken successfully, there will be no checkpoint
available for restart until another checkpoint is successfully taken.
Table 11: CHCKPT Parameter Fields (Part 1 of 2)
Position
1-6
Working With CODE-1 Plus
Field Name
KEYWORD
Description
CHCKPT is the only acceptable entry.
Comments
Required.
121
2
Parameter Reference
Table 11: CHCKPT Parameter Fields (Part 2 of 2)
Position
Field Name
Description
Comments
8-16
CHECKPOINT
COUNT
The number of records that are to be
processed before each checkpoint is
taken. You must enter leading zeros.
Required.
No default.
18-21
DEVICE TYPE
The type of device on which this file
resides. Enter one of the following
codes:
Not used for
z/OS.
Default is 2314.
TAPE
2311
2314
3310
3330
3340
3350
3370
3375
3380
FBA
122
Software Release 4.0.0/March 2015
CONFIG
2
CONFIG
The optional CONFIG parameter is used to identify the matching configuration that
is being used in this job. If this configuration matches one of the configurations that
Pitney Bowes has CASS-certified with the USPS, a USPS Form 3553 prints at the end
of the CODE-1 Plus job. For more information on CASS-certified configurations, refer
to Chapter 3 of the CODE-1 Plus Reference Guide.
NOTE: If you do not include this parameter in your job, the CASS report will not
be generated. If you mix strictness of Street name match, firm name match and
directional/suffix match, DPV process will be disabled.
This feature enables you to specify configuration information for CASS certification.
Some of the information that is stored on this parameter is the same as information
stored on other parameters.
NOTE: If you specify values for the fields on the CONFIG parameter, they override
the values specified on the other parameters.
This configuration information is particularly useful when you want to use an existing
job, but you want to make sure that it qualifies for automation-based discounts.
Instead of checking all of the information stored on the other parameters, you could
just add CONFIG information, which overrides the information in the other
parameters.
NOTE: A USPS form 3553 will be printed only when the information on a job’s
parameters corresponds to a configuration that Pitney Bowes has previously
certified.
Working With CODE-1 Plus
123
2
Parameter Reference
Table 12: CONFIG Parameter Fields (Part 1 of 6)
Position
Field Name
Description
Comments
1-6
KEYWORD
CONFIG is the only acceptable entry.
Required.
8
STREET NAME
MATCH CODE
Code indicating the strictness of the
street name match. Enter one of the
following codes:
Optional.
Default is M.
• E — Equal
• T — Tight
• M — Medium
• L — Loose.
10
FIRM NAME MATCH
CODE
Code indicating the strictness of the firm
name match. Enter one of the following
codes:
Optional.
Default is M.
• E — Equal
• T — Tight
• M — Medium
• L — Loose.
12
DIRECTIONAL/
SUFFIX MATCH
CODE
Code indicating the strictness of the
directional/suffix match. Enter one of the
following codes:
Optional.
Default is M.
• E — Equal
• T — Tight
• M — Medium
• L — Loose.
14
MULTIPLE MATCH
ACCEPTANCE
Code indicating if standardized
components should be stored if multiple
matches are found. Enter one of the
following codes:
Optional.
Default is N.
• Y — Accept multiple matches. The
standardized address that will be
returned will be the last one in the
stack of multiple matches that were
found.
• N — Do not accept multiple matches.
NOTE: A Y in this position will result in a
non-CASS certified configuration. No
CASS report will be generated.
16
124
MAXIMUM ADDRESS
CORRECTNESS
Maximum acceptable address
probability of correctness. Enter a
number between 0 and 9, where 0
indicates the best case and 9 indicates
the worst case.
Optional.
No default.
Software Release 4.0.0/March 2015
CONFIG
2
Table 12: CONFIG Parameter Fields (Part 2 of 6)
Position
Field Name
Description
Comments
18
MAXIMUM OVERALL
CORRECTNESS
Maximum acceptable overall probability
of correctness. Enter a number between
0 and 9, where 0 indicates the best case
and 9 indicates the worst case.
Optional.
No default.
20-21
USER-SPECIFIED
CONFIGURATION
NUMBER
Two-digit ID number to assign to this
configuration.
Optional.
No default.
TERMINATE IF NONCASS
Terminate the CODE-1 Plus job if an
option has been selected that results in a
non-CASS-certified configuration.
23
NOTE: This has no relation to
the Pitney Bowes' CASS-certified
configuration IDs; it is for your reference
only.
Optional.
Default is N.
• Y — Terminate if non-CASS-certified
configuration
• N — Do not terminate if non-CASScertified configuration.
25-27
EXECUTION LOG
COUNTER
Number of records (in thousands) to
trigger progress reporting in execution
log.
Optional.
Default is 10,000
(100 for VAX).
(100=100,000)
36
OUTPUT CASE
OPTION
Code indicating whether to return mixed
case in all address components. Enter
one of the following codes:
Optional.
Default is Blank.
• Blank — Matched output will be
returned in all uppercase.
• C — All address components that
contain text will be returned in mixed
case.
• L — All address components that
contain text will be returned in lower
case.
Working With CODE-1 Plus
125
2
Parameter Reference
Table 12: CONFIG Parameter Fields (Part 3 of 6)
Position
38
Field Name
DUAL ADDRESS
MATCH LOGIC
Description
Comments
Code indicating how to handle addresses
with multiple non-blank address lines or
multiple address types on the same
address line.
Optional.
Default is blank.
• Blank — Normal match scoring for
street address elements, input ZIP
Code, matching address line, and so
on.
• S — Return a street match,
regardless of the address line.
• P — Return a PO Box match,
regardless of the address line.
NOTE: Under normal conditions, a PO
Box cannot match if the city name and
input ZIP Code are both changed.
NOTE: If S or P is selected, a non-CASScertified configuration will be generated.
No PS Form 3553 will be generated.
DMM 708 states to match to a PO Box
first when on the same address line or
the PO Box address is the primary
address line.
40
UNIQUE ZIP
HANDLING
Code indicating whether the Input ZIP
Code should be returned when there is
no correlation between the input city/
state and ZIP Code.
Optional.
Default is blank.
• Blank — Do NOT store the Input ZIP
Code.
• X — Store the Input ZIP Code.
NOTE: If X is chosen, a non-CASS
certified configuration will be created.
No PS Form 3553 will be generated.
42
PMB HANDLING
Code indicating whether to store nonstandard private mailbox numbers.
Optional
Default is blank.
• Blank — Store ONLY standard private
mailbox numbers.
• X — Store ALL private mailbox
numbers.
NOTE: If X is chosen, a non-CASS
certified configuration will be created.
No PS Form 3553 will be generated.
126
Software Release 4.0.0/March 2015
CONFIG
2
Table 12: CONFIG Parameter Fields (Part 4 of 6)
Position
44
Field Name
ENHANCED
HIGH RISE
ALTERNATE
MATCHING
Description
Enhanced High Rise Alternate Matching
allows you to convert a building name
used as a street address to the correct,
USPS-preferred address street name
associated with that building.
Comments
Optional
Default is Y.
• Y — Yes, attempt to match to the base
record when an alternate match is
made and the input address contains
secondary address information.
• N — No, do not attempt to match to
the base record.
NOTE: Selecting N will create a NonCASS-certified configuration.
46
Working With CODE-1 Plus
MULTIPLE
SECONDARY
COMPONENT
PROCESSING
• Y — Attempt secondary match.
• N — Assign default ZIP+4 Code.
Optional
Default is Y.
NOTE: Selecting N will create a NonCASS-certified configuration.
127
2
Parameter Reference
Table 12: CONFIG Parameter Fields (Part 5 of 6)
Position
49
Field Name
USE NONSTANDARD CITY
NAMES
Description
Comments
Code indicating whether or not the
matcher should return vanity city names
when they most closely match the input
record. Enter one of the following codes:
Optional.
Default is blank.
• Blank — No, never return vanity city
names.
• X — Yes, return vanity city names
when they most closely match the
input city names. When this option is
selected, if you input a city name that
is not a USPS primary city, but is a
valid vanity name, the vanity name is
returned.
NOTE: Please note the following when
defining the Use Non-Standard City
Names field:
• If X is chosen, a CASS certified
configuration will be created, but you
will not be able to get a postal
automation presort discount.
• If you leave this field blank, and the
only matching city on the database is a
vanity city, the word “ZIP” and the ZIP
Code is stored in the Standardized
City location on your output record.
• If you define this field to return the
short city name, and a vanity city
name is greater than 13 characters,
CODE-1 Plus will not return the input
vanity city name if CODE-1 Plus is set
up to accept vanity city names.
Instead, CODE-1 Plus will return the
primary city name or, if the primary
city name has a short city name, the
primary short city name will be
returned. The USPS does not store
short city names for vanity cities and
CASS regulations state that the
software will return the primary city
name/primary short city name when
the input vanity long city name is
entered.
51
ENHANCED STREET
MATCHING OPTION
Code indicating whether to use
enhanced street matching during
CODE-1 Plus processing.
Optional.
Default is blank.
• Blank — Do not use enhanced street
matching
• A — Use all street matching.
• S — Use enhanced street matching.
128
Software Release 4.0.0/March 2015
CONFIG
2
Table 12: CONFIG Parameter Fields (Part 6 of 6)
Position
53
Field Name
LIMITED LOCALITY
OPTION
Description
Code indicating whether to perform
address matching against multiple
localities during CODE-1 Plus
processing.
Comments
Optional.
Default is blank.
• Blank — Conduct standard
processing
• X — Limit address match to ZIP Code
locality.
NOTE: Setting this option to X will
produce a non-CASS-certified
configuration. No USPS Form 3553 will
be generated.
55
SPLIT INDICA
Code indicating whether to perform Split
Indicia processing:
Optional.
Default is Y.
• Y — Perform split indicia processing
• N — Do not perform split indicia
processing.
NOTE: Setting this option to N will
produce a non-CASS-certified
configuration. No USPS Form 3553 will
be generated.
57
C/O DATA FLAG
Code indicating whether to append careof (C/O) data to the end of the output
address line.
Optional.
Default is blank.
• Blank — Do not append C/O data
• Y — Append C/O data.
59
Reserved
•
NOTE: Remember that only the “MMM” strictness code is a CASS-certified
configuration which will print a USPS form 3553. Any other combination of
strictness code (for example, “MEM”) will not generate a USPS form 3553.
NOTE: The values in the Maximum Address Correction and Maximum Overall
Correction fields must match the values in similar fields in the CR OUT, CS OUT,
SA OUT, Z4 OUT, and Z5 OUT parameters. If these fields do not match in all
parameters, an invalid CASS form will be generated.
Working With CODE-1 Plus
129
2
Parameter Reference
CONFRM
The optional CONFRM parameter is used to specify that records containing either
special ZIP Codes or “confirmation flag values” should be confirmed without
undergoing the matching process. These special ZIP Codes are APO/FPO, military
base, and government agency ZIP Codes.
This feature enables you to have special records automatically confirmed, without
CODE-1 Plus attempting to match them to the contents of the database. Often
CODE-1 Plus is unable to successfully match APO/FPO, military base, and
government agency ZIP Codes. This parameter enables you to have these types of
records written to the confirmed records output file instead of the rejected records
file.
Using confirmation flags in your records enables you to automatically confirm
records you know are correct, even though CODE-1 Plus does not match them.
As an example, let’s look at an insurance agency that wants to mail solicitations to new
homeowners. This agency has a standard mailing list, and has also bought lists of
addresses from several builders that have just finished new housing developments.
Because the streets in these new developments are so new, they have not yet been put
on the USPS database. The insurance agency will merge these new lists with its
standard mailing list, but will first insert confirmation flags in the records on the
builders’ lists. In their CODE-1 Plus job, they will include a CONFRM parameter that
looks for these confirmation flags and confirms the records automatically. In this way,
the records will be confirmed, even though the addresses are not on the CODE-1 Plus
database.
You can enter up to 4 confirmation values on each parameter, up to a maximum of
250 confirmation values. You can use as many CONFRM parameters as are necessary
to indicate the confirmation values you desire. If a string of blank spaces is one of the
confirmation values, it must be the first value on a parameter.
130
Software Release 4.0.0/March 2015
CONFRM
2
Table 13: CONFRM Parameter Fields (Part 1 of 2)
Position
Field Name
Description
Comments
1-6
KEYWORD
CONFRM is the only acceptable entry.
Required.
8-10
Location for OUTPUT
CONFIRMATION
CODE
Code indicating whether or not the record
was confirmed without processing, and if so,
why. One of the following codes is stored:
Optional.
No default.
• Blank — Not confirmed (record was
address-matched)
• V — Confirmed by comparison to an input
confirmation flag value
• A — Confirmed as an APO/FPO ZIP Code
• M — Confirmed as a military ZIP Code
• G — Confirmed as a government agency.
12
CONFIRM APO/FPO
ZIP CODES
Code indicating whether or not to confirm
APO/FPO ZIP Codes automatically. Enter
one of the following codes:
• Blank — Process APO/FPO ZIP Codes as
normal records.
Optional.
Default is to
process the
records.
• A — Confirm APO/FPO ZIP Codes.
14
CONFIRM MILITARY
BASE ZIP CODES
Code indicating whether or not to confirm
military base ZIP Codes automatically. Enter
one of the following codes:
Blank — Process military base ZIP Codes as
normal records.
Optional.
Default is to
process the
records.
M — Confirm military base ZIP Codes.
16
CONFIRM
GOVERNMENT
AGENCY ZIP CODES
Code indicating whether or not to confirm
government agency ZIP Codes
automatically. Enter one of the following
codes:
Optional.
Default is to
process the
records.
• Blank — Process government agency ZIP
Codes as normal records.
• G — Confirm government agency ZIP
Codes.
18-20
Location of
CONFIRMATION
FLAG
Location in the input record of the
confirmation flag.
Optional.
No default.
22
Length of
CONFIRMATION
FLAG
Length of the confirmation flag in the input
record. Must be 9 or less.
Optional.
No default.
Working With CODE-1 Plus
131
2
Parameter Reference
Table 13: CONFRM Parameter Fields (Part 2 of 2)
Position
24-25
Field Name
EQUAL/NOT EQUAL
CODE
Description
Comments
Code indicating whether the confirmation
flag in the records should be equal to or not
equal to the confirmation value(s) on this
parameter. Enter one of the following codes:
Optional.
No default.
• EQ — The confirmation flag in the record
must be equal to one of the confirmation
values on this parameter for the record to
be confirmed automatically.
• NE — The confirmation flag in the record
must not be equal to any of the
confirmation values on this parameter for
the record to be confirmed automatically.
NOTE: The EQUAL/NOT EQUAL CODE must
be the same on all CONFRM parameters.
132
27-35
CONFIRMATION
VALUE 1
A value to which the confirmation flag in the
input record is compared. If positions 24-25
above are EQ, and the confirmation flag in
the record is equal to this value, the record
will be confirmed. Conversely, if positions
24-25 above are NE, and the confirmation
flag in the record is not equal to this value,
the record will be confirmed.
Optional.
No default.
37-45
CONFIRMATION
VALUE 2
A value to which the confirmation flag in the
input record is compared. If positions 24-25
above are EQ, and the confirmation flag in
the record is equal to this value, the record
will be confirmed. Conversely, if positions
24-25 above are NE, and the confirmation
flag in the record is not equal to this value,
the record will be confirmed.
Optional.
No default.
47-55
CONFIRMATION
VALUE 3
A value to which the confirmation flag in the
input record is compared. If positions 24-25
above are EQ, and the confirmation flag in
the record is equal to this value, the record
will be confirmed. Conversely, if positions
24-25 above are NE, and the confirmation
flag in the record is not equal to this value,
the record will be confirmed.
Optional.
No default.
57-65
CONFIRMATION
VALUE 4
A value to which the confirmation flag in the
input record is compared. If positions 24-25
above are EQ, and the confirmation flag in
the record is equal to this value, the record
will be confirmed. Conversely, if positions
24-25 above are NE, and the confirmation
flag in the record is not equal to this value,
the record will be confirmed.
Optional.
No default.
Software Release 4.0.0/March 2015
CONTRL
2
CONTRL
CONTRL is a required parameter with no individual fields.
As shown in the following table, the parameter keyword field is the only field on the
CONTRL parameter.
Table 14: CONTRL Parameter Field
Position
1-6
Working With CODE-1 Plus
Field Name
KEYWORD
Description
CONTRL is the only acceptable entry.
Comments
Required.
133
2
Parameter Reference
CR OUT
The optional CR OUT parameter tells CODE-1 Plus where on the output record to
store the carrier route data.
NOTE: The carrier route is stored in USPS standard format, as defined under
positions 12-14 of this parameter.
Table 15: CR OUT Parameter Fields (Part 1 of 3)
Position
Field Name
Description
Comments
1-6
KEYWORD
CR OUT is the only acceptable entry.
Required.
8-10
Location for
CARRIER ROUTE
RETURN CODE
Location on the output record for the
1-character carrier route return code. One
of the following codes is stored:
Optional.
No default.
• Blank — The match attempt was
successful.
• A — Apartment number missing or not
found in database, and an apartmentlevel match was required.
• B — Insufficient (or blank) address
match information.
• C — The address probable correctness
or overall probable correctness was too
high.
• D — Information was dropped.
• H — House/box number not found on
street.
• L — The standardized address was too
long.
• M — Multiple matches of equal quality
were found.
• N — The carrier route wasn't stored
because the processing requirements
specified that it was not to be stored.
• S — Street name not found in ZIP Code.
• U — Unavailable—auxiliary file
processing.
• Z — ZIP Code not found in database.
134
Software Release 4.0.0/March 2015
CR OUT
2
Table 15: CR OUT Parameter Fields (Part 2 of 3)
Position
12-14
Field Name
Location for
CARRIER ROUTE
CODE
Description
Location on the output record for the
4-character carrier route code, which is
stored in one of the following formats:
Comments
Optional.
No default.
• Bnnn — PO box address
• Cnnn — Street address
• Gnnn — General delivery address
• Hnnn — Highway contract route address
• Rnnn — Rural route address.
60
Storage conditions
— INFORMATION
DROPPED
Code indicating whether the carrier route
code should be stored in cases in which
information was dropped during the match
process. Enter one of the following codes:
• Blank — Store the carrier route code
anyway.
Optional.
Default is to
store the
carrier
route code
anyway.
• X — Do not store the carrier route code.
62
MAXIMUM ADDRESS
CORRECTNESS
Maximum acceptable address probability of
correctness to store the carrier route. Enter
a number between 0 and 9, where 0
indicates the best case and 9 indicates the
worst case.
Optional.
Default is 9.
64
MAXIMUM OVERALL
CORRECTNESS
Maximum acceptable overall probability of
correctness to store the carrier route. Enter
a number between 0 and 9, where 0
indicates the best case and 9 indicates the
worst case.
Optional.
Default is 9.
68
Storage conditions
— MULTIPLE
CARRIER ROUTE
Code indicating whether or not the
standardized carrier route code should be
stored if multiple matching carrier route
codes were found. Enter one of the
following codes:
Optional.
Default is to
store
whatever is
indicated in
position 72.
• Blank — Do not store the returned
carrier route code. Instead, store the
information indicated in position 72.
• M — Store the returned carrier route
code.
Working With CODE-1 Plus
135
2
Parameter Reference
Table 15: CR OUT Parameter Fields (Part 3 of 3)
Position
70
Field Name
Storage conditions
— MULTIPLE ZIP
CODE
Description
Comments
Code indicating whether the standardized
carrier route code should be stored if
multiple matching ZIP codes were found.
Enter one of the following codes:
• Blank — Do not store the returned
carrier route code. Instead, store the
information indicated in position 72.
Optional.
Default is to
store
whatever is
indicated in
position 72.
• M — Store the returned carrier route
code.
72
DISPOSITION
INDICATOR
Code indicating what should be stored when
the standardized carrier route code was not
stored, either because no match was found,
or due to storage conditions. Enter one of
the following codes:
Optional.
Default is B.
• B — Store blanks.
• I — Store carrier route code from the
input record.
• X — Store nothing.
136
Software Release 4.0.0/March 2015
CS OUT
2
CS OUT
The optional CS OUT parameter is used to define the location in the output record
to write the standardized city and state information.
NOTE: If a vanity city name is greater than 13 characters, CODE-1 Plus will not
return the input vanity city name if CODE-1 Plus is set up to accept vanity city
names. Instead, CODE-1 Plus will return the primary city name or, if the primary
city name has a short city name, the primary short city name will be returned. The
USPS does not store short city names for vanity cities and CASS regulations state
that the software will return the primary city name/primary short city name when
the input vanity long city name is entered.
Remember, standardized city/state information is formatted to conform to USPS
conventions and matched against the master file. Dropped information is data that
was present in the input city/state line, but was ignored during the analysis process.
Working With CODE-1 Plus
137
2
Parameter Reference
Table 16: CS OUT Parameter Fields (Part 1 of 4)
Position
Field Name
Description
Comments
1-6
KEYWORD
CS OUT is the only acceptable entry.
Required.
8-10
Location for
CITY/STATE
RETURN CODE
Location on the output record for the 1-character
city/state return code. One of the following codes
is stored to indicate the reason the output city and
state were or were not stored.
Optional.
No default.
• Blank — An output city/state was stored.
• A — Apartment number missing or not found in
database, and an apartment-level match was
required.
• B — Insufficient (or blank) address match
information.
• C — The probable correctness was higher than
the specified maximum.
• D — Information was dropped during the
match.
• H — House/box number not found on street.
• M — Multiple matches of equal quality were
found.
• P — Primary City/State information returned
for input ZIP Code when no match found to
database.
• S — Street name not found in ZIP Code.
• U — Unavailable—auxiliary file processing.
• X — The only match was the default record.
• Z — ZIP Code not found in database.
12-14
Location for
CITY NAME
Location on the output record for the returned city
name.
Optional.
No default.
16-17
Length of
CITY NAME
Length of the returned city name.
Optional.
No default.
18
Storage
conditions —
SHORT CITY
NAME
Code indicating what should be stored, on the
output record, in the position pointed to by
columns 12-14.
Optional.
Default is
blank.
• Blank — Store the standardized city name
anyway.
• I — Store the short city name (regardless if it
was the input city name).
138
Software Release 4.0.0/March 2015
CS OUT
2
Table 16: CS OUT Parameter Fields (Part 2 of 4)
Position
19
Field Name
Storage
conditions — NO
ADDRESS
MATCH
Description
Code indicating what should be stored when no
address match is found. Enter one of the following
codes:
• Blank — Store the information indicated in
position 72.
• I — Store the input city.
Comments
Optional.
Default is to
store blanks
or nothing,
whichever is
indicated in
position 72.
• Z — Store the primary city for the valid input ZIP
Code. If you specify “Z”, CODE-1 Plus does not
generate a USPS Form 3553 (CASS Summary
Report).
21-23
Location for
SHORT CITY
NAME
Location on the output record for the 13-character
short city name. When no short city name
available, ZIP xxxxx will be returned in this output
area.
Optional.
No default.
25-27
Location for
STATE
ABBREVIATION
Location on the output record for the 2-character
state abbreviation.
Optional.
No default.
29
Storage
conditions — NO
STATE MATCH
Code indicating what should be stored when no
state match is found. Enter one of the following
codes:
Optional.
Default is to
store blanks
or nothing,
whichever is
indicated in
position 72.
• Blank — Store the information indicated in
position 72.
• I — Store the input state abbreviation.
• NOTE: These options are ignored when position
19 contains an I.
31-33
Location for
STANDARDIZED
CITY/STATE
LINE
Location on the output record for the standardized
city/state line. Enter a 3-digit location, or “INP” to
specify the standardized city/state line should be
stored in the same location as the input city/state
line. (INP is only valid if CS ZIP col. 8 is C or A.)
Optional.
No default.
35-36
Length of
STANDARDIZED
CITY/STATE
LINE
Length of the standardized city/state line.
Optional.
No default.
38
Format of
STANDARDIZED
CITY/STATE
LINE
Format of the standardized city/state line. Enter
one of the following codes:
Optional.
No default.
• 9 — City, state, ZIP Code, and ZIP+4 Code
• S — City and state only
• Z — City, state, and 5-digit ZIP Code.
40-42
Working With CODE-1 Plus
Location of
STANDARDIZED
URBANIZATION
NAME
Location on the output record for the standardized
urbanization name.
Optional.
No default.
139
2
Parameter Reference
Table 16: CS OUT Parameter Fields (Part 3 of 4)
Position
Field Name
Description
Comments
44-45
Length of
STANDARDIZED
URBANIZATION
NAME
Length of the standardized urbanization name.
Optional.
No default.
47-49
Location for
USPS COUNTY
NAME
Location for the 25-character USPS county name
on the output record.
Optional.
No default.
51-53
Location for
USPS FIPS
COUNTY CODE
Location for the 3-character USPS FIPS county
code on the output record.
Optional.
No default.
55-57
Location for
CONGRESSIONAL DISTRICT
Location for the 2-character congressional
district code on the output record.
Optional.
No default.
59
Storage
conditions —
PREFERRED
LAST LINE CITY
NAME
Code indicating whether the preferred last line
city name should be stored:
Optional.
Default is Z.
NOTE: You may want to post the FIPS county code
to your record if you plan on handling IN-COUNTY
Periodicals Mailings in MailStream Plus. MSP
now needs the FIPS county code to determine the
county for in and out of county presort coding.
• C — Store the USPS-preferred City Name from
USPS City/State File.
NOTE: If you select C, CODE-1 Plus does not
generate a CASS certified configuration and
does not generate the USPS 3553 Report.
• Z — Store the Preferred Last Line City Name
from the USPS ZIP+4 File (Override City Name).
(See the AM2OUT parameter for a description
of the Override City Name.)
NOTE: If you select Z, CODE-1 Plus generates a
CASS certified configuration and the USPS
3553 Report.
• P — Store the Primary City Name from the
USPS City/State File.
NOTE: If you select P, CODE-1 Plus does not
generate a CASS certified configuration and
does not generate the USPS 3553 Report.
60
Storage
conditions —
INFORMATION
DROPPED
Code indicating whether the standardized city/
state line should be stored when information was
dropped during the standardization process.
Enter one of the following codes:
Optional.
Default is
blank.
• Blank — Store the information anyway.
• X — Do not store if information was dropped.
140
Software Release 4.0.0/March 2015
CS OUT
2
Table 16: CS OUT Parameter Fields (Part 4 of 4)
Position
Field Name
Description
Comments
62
MAXIMUM
ADDRESS
CORRECTNESS
Maximum acceptable address probability of
correctness to store the standardized city/state
line. Enter a number between 0 and 9, where 0
indicates the best case and 9 indicates the worst
case.
Optional.
Default is 9.
64
MAXIMUM
OVERALL
CORRECTNESS
Maximum acceptable overall probability of
correctness to store the standardized city/state
line. Enter a number between 0 and 9, where 0
indicates the best case and 9 indicates the worst
case.
Optional.
Default is 9.
66
Storage
conditions — NO
CITY MATCH
Code indicating what should be stored when no
city name match was found. Enter one of the
following codes:
Optional.
Default is
blank.
• Blank — Store the default city name.
• X — Store the information indicated in position
72.
68
Storage
conditions —
MULTIPLE ZIP+4
Code indicating whether the standardized city/
state line should be stored when multiple ZIP+4
matches were found. Enter one of the following
codes:
• Blank — Store the information indicated in
position 72.
• M — Store the standardized city/state line
anyway.
69
Storage
Conditions—
MULTIPLE
URBANIZATION
NAME
Code indicating whether to store the standardized
urbanization name when multiple matches were
found on the database.
• Blank — Store the information indicated in
position 72.
• M — Store the standardized urbanization
name.
70
Storage
conditions —
MULTIPLE ZIP
CODE
Code indicating whether the standardized city/
state line should be stored when multiple ZIP
Code matches were found. Enter one of the
following codes:
• Blank — Store the information indicated in
position 72.
• M — Store the standardized city/state line
anyway.
72
DISPOSITION
INDICATOR
Code indicating what should be stored in cases
where the standardized city/state line was not
stored, either because no match was found or due
to storage conditions. Enter one of the following
codes:
Optional.
Default is to
store blanks
or nothing,
whichever is
indicated in
position 72.
Optional.
Default is to
store blanks
or nothing,
whichever is
indicated in
position 72.
Optional.
Default is to
store blanks
or nothing,
whichever is
indicated in
position 72.
Optional.
Default is B.
• B — Store blanks.
• X — Store nothing.
Working With CODE-1 Plus
141
2
Parameter Reference
CS ZIP
The required CS ZIP parameter defines the location, length, and format of the city,
state, and ZIP Code in the input record.
NOTE: CODE-1 Plus considers a ZIP Code of 00000 to be invalid. If you want to
preserve an input ZIP Code that is all zeros, you will have to use either a MOVE I
parameter or an exit routine.
Table 17: CS ZIP Parameter Fields (Part 1 of 3)
Position
Field Name
Description
Comments
1-6
KEYWORD
CS ZIP is the only acceptable entry.
Required.
8
Format of CITY/
STATE/ZIP CODE
Format of the city/state and ZIP Code
information on the input record. Enter one of
the following codes:
Required.
No default.
• A — City/state/ZIP Code are amongst the
address lines (position 8 on ADDRDF must
be L). If you select this value, your city/
state/ZIP must be together in the rightmost (last) non-blank address line
defined.
• C — City/state mixed with address lines;
ZIP separate
• M — City/state together in one field; ZIP in
a separate field
• S — City, state, and ZIP in three separate
fields
• X — City/state/ZIP in a single field
separate from the address.
142
Software Release 4.0.0/March 2015
CS ZIP
2
Table 17: CS ZIP Parameter Fields (Part 2 of 3)
Position
Field Name
Description
Comments
10-12
Location of
SEPARATE ZIP CODE
Location on the input record for the separate
ZIP Code.
Optional.
No default.
Can not be
used with
option A
above.
14
Format of
SEPARATE ZIP CODE
Format of the separate ZIP Code. Enter one of
the following codes:
Optional.
No default.
• 9 — ZIP Code is 9 digits binary stored in 4character format.
• B — ZIP Code is in 3-character binary
format.
• C — ZIP Code is stored in 5-character
format.
• P — ZIP Code is in a 3-character packed
format (the sign digit is ignored so that the
start of a 5-character packed 9-digit ZIP+4
Code can be used with this option).
16-18
Location of
CITY, CITY/STATE, or
CITY/STATE/ZIP
Location on the input record for the field that
contains the city, city/state, or city/state/ZIP.
Required if
“M” is
entered in
position 8.
No default.
20-21
Length of
CITY, CITY/STATE, or
CITY/STATE/ZIP
Length of the city, city/state, or city/state/ZIP
field.
Required if
“M” is
entered in
position 8.
No default.
23-25
Location of
SEPARATE STATE
Location on the input record for the separate
state.
Optional.
No default.
27-28
Length of
SEPARATE STATE
Length of the separate state.
Optional.
No default.
30-32
Location for storage
of EXTRACTED ZIP
CODE
Location on the output record where the
extracted ZIP Code should be stored. If the
input ZIP Code field is non-numeric, or is all
zeros, then blanks are stored in the location
you specify here.
Optional.
No default.
34-36
Location of
ORIGINAL ZIP+4
CODE
Location on the input record of the ZIP+4
add-on code.
Optional.
No default.
Working With CODE-1 Plus
143
2
Parameter Reference
Table 17: CS ZIP Parameter Fields (Part 3 of 3)
Position
38
Field Name
Format of ORIGINAL
ZIP+4 CODE
Description
Comments
Format of the ZIP+4 add-on code. Enter one
of the following codes:
Optional.
No default.
• C — 4-character format
• B — 3-character binary format
• P — 3-character packed format (the sign
digit is ignored so that the start of a
5-character packed 9-digit ZIP+4 code can
be used with this option).
40-42
Location of
ORIGINAL CARRIER
ROUTE CODE
Location on input record of the carrier route
code.
Optional.
No default.
44-46
Location of MASTER
FILE VINTAGE DATE
Location on the input records of the master
file vintage date. This field or the vintage of
MASTER FILE LITERAL in positions 50-55
activate Z4CHANGE processing.
Optional.
No default.
Code indicating the input format of the
master file vintage date in the input records.
This field is ignored if positions 44-46 are
blank. Enter one of the following codes:
Optional.
No default.
48
Format of MASTER
FILE VINTAGE DATE
• B — 2-byte binary format YYMM
• C — 4-byte character format YYMM
• P — 3-byte packed decimal format YYMM
Either a
location is
specified in
this field, or
a date is
specified in
positions
50-55, but
not both.
Required if a
location is
specified in
positions
44-46
• 3 — 3-byte binary format YYYYMM
• 6 — 6-byte character format YYYYMM
• 4 — 4-byte packed decimal format
YYYYMM.
50-55
144
MASTER FILE
LITERAL DATE
Master file vintage date in YYYYMM format.
NOTE: If this field is filled in, positions 50-51
must contain “19” or “20”, and positions 5455 must contain “01” through “12”.
Optional.
No default.
Either a
literal date
is specified
in this field,
or a location
is specified
in positions
44-46, but
not both.
Software Release 4.0.0/March 2015
CS ZIP
2
NOTE: If you specify a location of original ZIP+4 CODE and CARRIER ROUTE
CODE, CODE-1 Plus tracks the number of times the returned ZIP+4 Code and
carrier code were identical to the originals. These statistics are printed on the
Analysis of Matched Records Report.
Working With CODE-1 Plus
145
2
Parameter Reference
DPVIN
The optional DPVIN parameter activates DPV and RDI processing and enables you
to process options on multiple matches to the ZIP+4 database. For more information
on DPV and RDI, refer to Chapter 6, "Using Delivery Point Validation".
Currently, the USPS ZIP+4 file consists of ranges of addresses. This means that if a
given house number is entered on the input and that number falls within the range
of the USPS ZIP+4 file, the address will be validated regardless of whether the house
number actually exists. Delivery Point Validation (DPV) allows you to determine
whether an actual address exists, right down to the apartment or suite level. DPV
allows you to validate that your address information is a physical address served by
the Postal Service. RDI allows you to determine if an address is a residential or
business delivery point.
NOTE: The DPV and RDI processing use a separate license from CODE-1 Plus. The
license must be loaded in order for this parameter to properly function.
146
Software Release 4.0.0/March 2015
DPVIN
2
What is a Multiple Match?
A multiple match occurs when one part of an input address has the possibility of
coding several different ways in CODE-1 Plus. Below are examples of the different
types of multiple matches that can be Delivery Point Validated.
Input Addresses
Example of
Multiple
ZIP Code
Match
Example of
Multiple
ZIP Code and
Street Match
Example of
Multiple
Suffix Match
Example of
Multiple
Suffix/Directional
Correction Match
Example of
Multiple
Street Address
Match
Example of
Multiple
Carrier Route
Match
PO Box 155
New Yor k, N Y
CODE-1 Plus Results
PO Box 155
New York, NY 10002- 0155
PO Box 155
New York, NY 10008- 0155
1559 45th Street
Los Angeles, CA
67 Williams St
Woburn, MA 01801
1050 17th Str eet N
W ashington, DC
4 Calle 1
San Juan, PR
107 Pear l Street
Timpsin, TX 75975
1559 E 45th Street
Los Angeles, CA 90011- 4341
1559 W 45th Str eet
Los Angeles, C A 90062- 2045
67 W illiams Ct
Wobur n, MA 01801-1738
67 Williams Ln
Wobur n, MA 01801-1216
1050 17th St N W
Washington, DC 20036-5503
1050 17th St NE
Washington, DC 20036-7362
4 C alle 1
San Juan PR 00926-1408
4 Calle 1
San Juan PR 00927-4629
Two post
offices
boxes have
the same
number, but
different ZIP
Codes.
Two streets
with the
same name,
but with
different ZIP
Codes.
67 Williams
S treet in
Woburn, MA
does not
exist, but
both 67
W illiams Ct
and 67
Williams Ln
do exist.
17th St N
does not
exist in
Washington
DC, but
there is both
a 17th St
NW and a
17th St NE.
In San Juan,
there are two
streets called
Calle 1 with
the same
hous e
number.
Two different Carrier Routes
result for this address after
processing by CODE-1 Plus:
R002 and R003
Figure 1: Examples of Multiple Matches in CODE-1 Plus
Working With CODE-1 Plus
147
2
Parameter Reference
Table 18: DPVIN Parameter Fields (Part 1 of 4)
Position
Field Name
Description
Comments
1-6
KEYWORD
DPVIN is the only acceptable entry.
Required.
8
Multiple Match
Option - ZIP CODE
AND PO BOX OR
RURAL ROUTE/
HIGHWAY
CONTRACT
ADDRESS TYPE
If your input file contains multiple matches of
the ZIP Code and the PO Box or Rural Route/
Highway Contract:
Optional.
Default is Y.
Multiple Match
Option - ZIP CODE
AND STREET
ADDRESS TYPE
If your input file contains multiple matches of
the ZIP Code and the street address type:
Multiple Match
Option - CARRIER
ROUTE
If your input file contains multiple matches of
the Carrier Route in CODE-1 Plus:
10
12
• Y — Yes, attempt to DPV confirm.
• N — No, do not attempt to DPV confirm.
Optional.
Default is Y.
• Y — Yes, attempt to DPV confirm.
• N — No, do not attempt to DPV confirm.
Optional.
Default is Y.
• Y — Yes, attempt to DPV confirm.
• N — No, do not attempt to DPV confirm.
14
Multiple Match
Option DIRECTIONAL
If your input file contains multiple matches of
the directional:
Optional.
Default is Y.
• Y — Yes, attempt to DPV confirm.
• N — No, do not attempt to DPV confirm.
16
Multiple Match
Option - SUFFIX
If your input file contains multiple matches of
the suffix:
Optional.
Default is Y.
• Y — Yes, attempt to DPV confirm.
• N — No, do not attempt to DPV confirm.
18
148
Multiple Match
Option - SUFFIX/
DIRECTIONAL
CORRECTION
If your input file contains multiple matches of
the suffix/directional correction:
Optional.
Default is Y.
• Y — Yes, attempt to DPV confirm.
• N — No, do not attempt to DPV confirm.
Software Release 4.0.0/March 2015
DPVIN
2
Table 18: DPVIN Parameter Fields (Part 2 of 4)
Position
20
Field Name
Multiple Match
Option - MULTIPLE
INPUT SECONDARY
COMPONENTS WITH
NO DESIGNATOR
Description
If your input file contains multiple matches of
the secondary components with no designator:
Comments
Optional.
Default is Y.
• Y — Yes, attempt to DPV confirm.
• N — No, do not attempt to DPV confirm.
NOTE: By selecting N you will generate a nonCASS-certified configuration. No PS Form
3553 will be generated.
Below is an example of secondary components
with no designator:
John Jones
12 Main St. #12 #5
New York, NY 10012
#12 and #5 have no indication of being an
apartment, PO Box or otherwise.
22
UNIQUE ZIP/SMALL
TOWN DEFAULT
ZIP+4 ASSIGNMENT
OPTION
If an address has been assigned a ZIP+4 by
CODE-1 Plus during regular processing, you
may select one of the following options
regarding this ZIP+4 assignment:
Optional.
Default is Y.
• Y — Yes, attempt to DPV confirm.
• N — No, do not attempt to DPV confirm.
24
DPV SECONDARY
ADDRESS
VALIDATION
DPV automatically attempts to validate
primary and secondary information on input
addresses. Then, if no match is made, DPV will
attempt to validate using the primary
information only. Turning off this option will
reduce the number of look-ups to DPV files
and may increase processing. Select one of
the following:
Optional
Default is Y
• Y — Perform DPV validation using
secondary address information.
• N — No, do not perform DPV validation
using secondary address information.
Selecting this value will generate a nonCASS certified configuration
NOTE: By selecting N you will generate a nonCASS-certified configuration. No PS Form
3553 will be generated.
26
CMRA LOOKUP
This option allows you to determine whether
or not an input address is a Commercial Mail
Receiving Agency (CMRA). Select one of the
following:
Optional
Default is Y
• Y — Yes, perform CMRA lookup.
• N — No, do not perform CMRA lookup.
Working With CODE-1 Plus
149
2
Parameter Reference
Table 18: DPVIN Parameter Fields (Part 3 of 4)
Position
28
Field Name
PBSA LOOKUP
Description
Comments
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. This field
determines whether CODE-1 Plus uses the
PBSA Table to return the PBSA result in
output.
Optional.
Default is N.
• Blank — Do not perform PBSA lookup.
• Y — Yes, perform PBSA lookup.
• N — No, do not perform PBSA lookup.
NOTE: If you specify "Y", you must define a
location for the DPV PBSA Flag in positions
32-34 of the DPVOUT parameter (location on
the output record for a 1-character code
indicating whether this address was found in
the PBSA table).
52
RDI INDICATOR
This option allows you to choose whether to
perform RDI processing.
• Blank — Do DPV processing only.
Optional.
Default is
blank.
• Y — Attempt both DPV and RDI processing.
• N — Do not attempt DPV processing.
Perform RDI processing only. If you specify
“N” in position 52, you will generate a nonCASS-certified configuration and CODE-1
Plus will not generate a USPS Form 3553.
54
DPV FILE OPTION
This option allows you to specify the DPV file to
match against.
• Blank — Process the DPV split file.
Required.
Default is
blank.
• S — Process the DPV split file.
• F — Process the DPV flat file.
• H — Process the DPV full (hash) file.
150
Software Release 4.0.0/March 2015
DPVIN
2
Table 18: DPVIN Parameter Fields (Part 4 of 4)
Position
56
Field Name
DPV MEMORY
MODULE SIZE
INDICATOR
Description
This option allows you to specify size of DPV
module.
• Blank — DPV process will be using Medium
memory model (default).
Comments
Required.
Default is
blank.
• P — Pico memory model (no files in
memory).
• U — Micro memory model (no files in
memory, only indexes).
• S — Small memory model (HSC and HSF in
memory).
• M — Medium memory model (LCD also in
memory).
• L — Large memory model (HSX also in
memory).
• H — Huge memory model (all files in
memory).
58
CMRA/PMB
CONVERSION
INDICATOR
(CONVERT
SECONDARY
INFORMATION TO
PMB)
This option allows you to specify whether to
convert secondary information to PMB.
Optional.
Default is N.
• Blank — Do not convert secondary
information to PMB.
• Y — Yes, convert secondary information to
PMB where appropriate.
• N — No, do not convert secondary
information to PMB.
Working With CODE-1 Plus
151
2
Parameter Reference
DPVOUT
The required DPVOUT parameter posts all answers from DPV and RDI processing.
For more information on DPV and RDI, refer to Chapter 6, "Using Delivery Point
Validation".
DPV Footnote Codes are 2-character, USPS-defined codes that represent the changes
that were made to the input address during the matching process. Up to 10 of these
codes can be stored by CODE-1 Plus for each record. Even if your address is not
presented for DPV processing, those footnote codes that pertain to the match to the
ZIP+4 database will be returned.
NOTE: The DPV and RDI processing add-on options must be licensed in order for
this parameter to properly function.
Table 19: DPVOUT Parameter Fields (Part 1 of 5)
Position
Field Name
Description
Comments
1-6
KEYWORD
DPVOUT is the only acceptable entry.
Required.
8-10
Location for
DPV RETURN CODE
Location on the output record for a
1-character DPV Return Code. The DPV Return
Codes are listed below:
Optional
• M — Unable to Multiple Condition resolve.
• N — No Delivery Point Validation.
• Y — Delivery Point validated. Primary
number valid and second number (when
present) valid.
• S — Valid primary number; but secondary
number (primary for Rural Route) present
and is not confirmed. Also, can indicate that
the house range contained a single trailing
alpha that was dropped to attempt Delivery
Point Validation.
• D — Valid primary number; input missing
secondary number (primary Rural Route).
• Blank — Address not presented to DPV
table.
152
Software Release 4.0.0/March 2015
DPVOUT
2
Table 19: DPVOUT Parameter Fields (Part 2 of 5)
Position
12-14
Field Name
Location for
DPV CMRA FLAG
Description
In this field, you indicate the location on the
output record for a 1-character Commercial
Mail Receiving Agency (CMRA) Flag (indicates
a private business that acts as a mailreceiving agent for specific clients). This field
contains the results of the call to the DPV
CMRA Hash Table (dph.hsc):
Comments
Optional
• Y — Yes, address was found in CMRA table.
• N — No, address was not found in CMRA
table.
• Blank — Address not presented to hash
table.
NOTE: The CMRA lookup automatically occurs
when the DPV return code is Y or S, unless
otherwise specified in the DPVIN parameter
record.
16-18
Location for
DPV FALSE/
POSITIVE FLAG
If the DPV return code is N, CODE-1 Plus will
automatically begin a false/positive look-up. In
this field, you indicate the location on the
output record for a 1-character False/Positive
Flag:
Optional
• Y — False.
• N — Not false.
• Blank — Not presented.
NOTE: A Y indicates that you have hit a “seed
record” in your processing.
Working With CODE-1 Plus
153
2
Parameter Reference
Table 19: DPVOUT Parameter Fields (Part 3 of 5)
Position
20-22
Field Name
Location for
DPV FOOTNOTE
CODES
Description
Comments
Location on the output record for a 20character area to accommodate DPV Footnote
Codes.
Optional
• AA — Input address matched to the ZIP+4
file.
• A1 — Input address not matched to the
ZIP+4 file.
• BB — Input address matched to DPV (all
components).
• CC — Input address primary number
matched to DPV but secondary number not
match (present but not valid).
• F1 — Input address is military; DPV
bypassed.
• G1 — Input address is general delivery; DPV
bypassed.
• M1 — Input address primary number
missing.
• M3 — Input address primary number
invalid.
• N1 — Input address primary number
matched to DPV but high rise address
missing secondary number.
• P1 — Input address missing RR or HC Box
number.
• P3 — Input address missing PO, RR, or HC
Box number.
• PB — Input address is a P. O. Box Street
Address (PBSA).
• RR — Input address matched to CMRA.
• R1 — Input address matched to CMRA but
secondary number not present.
• R7 — Input address matched to phantom
carrier route R777 (not eligible for street
delivery).
• U1 — Input address is unique ZIP; DPV
bypassed.
154
Software Release 4.0.0/March 2015
DPVOUT
2
Table 19: DPVOUT Parameter Fields (Part 4 of 5)
Position
24-26
Field Name
Location for NO
STAT FLAG
Description
A 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.
Comments
Optional.
No default.
• Blank — Not presented
• Y — Found match to ‘No Stat’ DPV hash
table
• N — No match found to “No stat” DPV hash
table.
NOTE: If this option is present in the DPVOUT
parameter, the DPV DLL will look up
addresses in the “No Stat” table. If this
position is blank, CODE-1 Plus will not look
up address in the “No Stat” table.
28-30
Location for VACANT
TABLE FLAG
Location on the output record for a 1character 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.
NOTE: If this option is present in the DPVOUT
parameter, the DPV DLL will perform an
address search in the “Vacant” table;
otherwise, for performance reasons, DPV
will not look up the address in the “Vacant”
table.
32-34
Location for DPV
PBSA FLAG
Location on the output record for the onecharacter code that indicates whether this
address was found in the PBSA table.
Optional.
No default.
• Blank — Not presented
• Y — Found in the DPV PBSA Table.
• N — Not found in the DPV PBSA Table.
NOTE: If you specify a location for the DPV
PBSA Flag, you must specify "Y" in position
28 of the DPVIN parameter (PBSA Lookup).
DPVIN position 28 determines whether
CODE-1 Plus uses the PBSA Table to return
the PBSA result in output. If you specify a
value for DPVOUT positions 32-34 and do not
specify "Y" in position 28 of the DPVIN
parameter (PBSA Lookup), a parameter
error occurs.
Working With CODE-1 Plus
155
2
Parameter Reference
Table 19: DPVOUT Parameter Fields (Part 5 of 5)
Position
50-52
Field Name
Location for
RESIDENTIAL FLAG
Description
Comments
Location on the output record for a 1character Residential Flag:
Optional.
No default.
• Blank — Not a residential delivery point.
• R — Yes, this address is a residential-only
delivery point.
54-56
Location for
BUSINESS FLAG
In this field, you indicate the location on the
output record for a 1-character Business Flag:
Optional.
No default.
• Blank — Not a business delivery point.
• B — Yes, this address is a business-only
delivery point.
• M — Yes, this address is mixed residential
and business delivery point.
NOTE: You can only receive a business flag of
M if you have enabled the business flag option
in position 58.
58
BUSINESS FLAG
OPTION
This option enables you to have two different
business flag values returned in the Business
Flag output location (specified in position 5456):
Optional.
• Blank — Return B for all Business Delivery
Points.
• R — Return Residential Delivery Points.
• M — Return M for Mixed Business and
Residential Delivery Points.
NOTE: The “M” option is a combination of
both residential and business deliveries for
that ZIP+4, but is considered a business
delivery point by the USPS, for example a
Highrise.
59
TERMINATE DPV
PROCESSING
This option allows DPV to stop batch jobs when
a false-positive (seed record) has been
encountered:
Optional
Default: W
• S — Shuts down CODE-1 Plus processing
when a false-positive (seed record) is
encountered.
• W — Allows CODE-1 Plus 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 DPV license.
156
Software Release 4.0.0/March 2015
EXITOP
2
EXITOP
The optional EXITOP parameter names an operating exit routine that you want
CODE-1 Plus to call after the record has been processed but before it is written to an
output file. The only system-defined field on this parameter contains the name of the
operating exit routine. You can use the remaining 63 bytes to specify information
that your exit routine needs.
Note that if you have also specified an output exit routine, the operating exit routine
specified on the EXITOP parameter is called first. The operating exit routine then
does its processing and passes the record back to CODE-1 Plus. CODE-1 Plus then
passes the same record to the output exit routine that you have specified for that
specific output file.
CODE-1 Plus will call your exit routine with the following four parameters in the
linkage section:
•
•
PARM1 — This parameter is 1-character, which will contain one of the following
codes to tell your program what type of processing is to be performed:
–
O for open the output file
–
W for write a record to the output file
–
C for close the output file.
PARM2 — This parameter is the output file indicator.
If you are using a Pitney Bowes Barcoding Option or another exit routine with
CODE-1 Plus, you must place a P in column 7 of the EXITOP parameter, and you
must indicate the file identifiers on your parameter (see your Barcoding Option
documentation for specific placement). CODE-1 Plus will then pass one of the
following 2-byte file identifiers to your exit routine: OK for C1BMCOK; CO for
C1BMNCO; ZP for C1BMIZP; or P4 for C1BMZP4.
If you are not using one of the Pitney Bowes exit routines, and you do not put a
“P” in column 7, one of the following 7-byte file identifiers will be passed:
C1BMCOK, C1BMNCO, C1BMIZP, or C1BMZP4.
•
PARM3 — This parameter contains the output record to be passed from
CODE-1 Plus to your program. The length of this parameter will be the length of
the output record as defined on the FILEDF parameter for the output file named
in PARM2, above. This parameter is only valid when PARM1 is set to “W” in order
to write a record to the output file.
•
PARM4 — This parameter contains the image of your EXITOP parameter, and is
80 bytes in length.
Working With CODE-1 Plus
157
2
Parameter Reference
Table 20: EXITOP Parameter Fields
Position
158
Field Name
Description
Comments
1-6
KEYWORD
EXITOP is the only acceptable entry.
Required.
7
CODE-1 PLUS
IDENTIFIER
If you are going to use this program with
the Pitney Bowes Barcoding Option, or
the Geocoder, you must enter “P” in this
position and then use the 2-character
file identifiers as parameter 2.
Optional.
Use only if you
are using 2character file
identifiers as
parameter 2 in
your linkage
section.
8-17
OPERATING EXIT
ROUTINE NAME
Name of the exit routine that you want
CODE-1 Plus to call before writing each
record to an output file (or before calling
an output exit routine).
Required.
No Default.
Name must be
left-justified.
18-80
USER-DEFINED
DATA
Enter any information that you need
CODE-1 Plus to pass to your exit routine.
Optional.
No default.
Software Release 4.0.0/March 2015
FILEDF
2
FILEDF
The required FILEDF parameter identifies your input and output file structures, as
well as any input or output exit routine to call with this job. This information tells
CODE-1 Plus what files to use, and what to do each time CODE-1 Plus is ready to read
a record from the input file or write a record to an output file.
File Names
CODE-1 Plus has five file names that you will use for your input file and output files,
regardless of their actual dataset names. You use CODE-1 Plus-defined file names on
the FILEDF parameter, but you will use your own file names in the JCL you write to
run a CODE-1 Plus batch file.
The following file names are valid for the FILEDF parameter:
•
C1BMNAM — This is your input name-and-address file. C1BMNAM stands for
CODE-1 Plus Batch Match Name file. This file is designated as C1BMNAM in the
job control file (JCL, DCL, Script, etc.).
•
C1BMCOK — This is the output file to which CODE-1 Plus writes all of the
records that are verified or corrected. C1BMCOK stands for CODE-1 Batch
Match Coded OK. This file is designated as C1BMCOK in the job control file (JCL,
DCL, Script, etc.).
•
C1BMNCO — This is the output file to which CODE-1 Plus writes all of the
records that have valid input ZIP Codes (i.e., the ZIP Code was valid somewhere
in the U.S.) but were not matched for some reason. C1BMNCO stands for
CODE-1 Batch Match Not Coded. This file is designated as C1BMNCO in the job
control file (JCL, DCL, Script, etc.).
•
C1BMIZP — This is the output file to which CODE-1 Plus writes all of the
unmatched records that have invalid input ZIP Codes. An invalid input ZIP Code
is one that is not valid anywhere in the U.S. C1BMIZP stands for CODE-1 Batch
Match Invalid ZIP. This file is designated as C1BMIZP in the job control file (JCL,
DCL, Script, etc.).
•
C1BMZP4 — This is the output file to which CODE-1 Plus writes all of the
records that were ZIP+4 coded. C1BMZP4 stands for CODE-1 Batch Match
ZIP+4. This file is designated as C1BMZP4 in the job control file (JCL, DCL,
Script, etc.).
•
C1BMSTA — This is the output file to which CODE-1 Plus writes all of the output
statistics. These records are fixed length. The only required field on the
parameter is record length, positions 19-22, and may be any numeric value.
Working With CODE-1 Plus
159
2
Parameter Reference
Exit Routines
The FILEDF parameter allows you to specify an input exit routine that CODE-1 Plus
should call each time it is ready to read a record from your input name-and-address
file, or the output exit routine that CODE-1 Plus should call each time it is ready to
write a record to your output file. If you are using an input exit routine, CODE-1 Plus
calls your exit routine—rather than reading the record—and waits for the exit
routine to pass a record back. If you are using an output exit routine, CODE-1 Plus
passes the record to the output exit routine, instead of writing the record to the file.
For example, you might have an input exit routine named CODEIT that adds a special
code to a record. If you want to add that code to each record before the record is
passed to CODE-1 Plus, you would specify CODEIT as the name of the exit routine.
Then, every time CODE-1 Plus is ready to accept a record, it passes control to
CODEIT, which reads the record, adds the code to the record, and then passes the
record to CODE-1 Plus so that CODE-1 Plus can process that record.
When you use the FILEDF parameter to call an exit routine, CODE-1 Plus will call that
exit routine with the following four parameters in the linkage section at each I/O
request.
•
160
PARM1—a total of 9 bytes and has two components, as follows:
–
Bytes 1-8: The file name (C1BMNAM, C1BMCOK, C1BMNCO, C1BMIZP, or
C1BMZP4)
–
Byte 9: Function indicator. This byte will contain one of the following codes
to tell your program the type of processing to perform:
–
O to Open the input or output file
–
R to Read a record from the input file
–
W to Write a record to the output file
–
C to Close the input or output file.
•
PARM2—a 5-digit length (less than or equal to 32,760) packed into a 3-byte
field (COBOL “PIC S9(5) COMP-3”). This parameter must be filled in by your exit
routine if byte 9 of PARM1 is O or R. When byte 9 of PARM1 is R, the input exit
routine signals the end of the file by setting this to 0.
•
PARM3—contains the output record to be passed from CODE-1 Plus to your
program (when EXITFC is W), or the input record to be passed from your program
to CODE-1 Plus (when EXITFC is R). The length of this parameter will be the
length specified by the exit routine in PARM2 above (maximum of 32,760).
•
PARM4— contains the image of your FILEDF parameter and is 80 bytes in
length.
Software Release 4.0.0/March 2015
FILEDF
2
Limiting Processing With FILEDF
There are three ways to limit the number of records CODE-1 Plus processes. First, you
can skip a portion of the file before any records are selected. Second, you can enter
a fraction to select a portion of the records, evenly spaced throughout the file. Third,
you can specify a maximum number of records that should be processed; in this case
CODE-1 Plus will start at the beginning of the file and process every record until the
maximum number is reached.
You can use these fields in conjunction with each other. For example, you could enter
a number of records to skip, and a maximum number of records to read if you wanted
to process the middle of the file, but not the beginning or the end.
Fractional Record Selection
The fractional record selection feature enables you to sample records throughout the
file, from beginning to end, without processing consecutive records. To determine
the number to enter in this 7-byte field, divide the number of records you want to
process by the number of records in the file. This will give you a decimal number.
Drop the decimal, and enter the first 7 digits of the number. For example, you have a
file with 102986 records, and you want to process 2000 records. You would divide
2000 by 102986 and get .0194201153. Dropping the decimal, you would enter
0194201 in the fractional record selection field. This will ensure that the 2,000
records processed are evenly distributed throughout the file.
NOTE: The maximum sample is every other record (half of the file). If you enter a
fraction greater than .5000000, the record selection process yields every record
in the file.
NOTE: Limiting the number of records to process (by skipping records, specifying
a maximum, or sampling the file) should be done on the input FILEDF parameter.
If you limit processing on an output FILEDF parameter, CODE-1 Plus will process
all of your input records, but will limit the number of records written to the output
file.
Working With CODE-1 Plus
161
2
Parameter Reference
Table 21: FILEDF Parameter Fields (Part 1 of 3)
Position
Field Name
Description
Comments
1-6
KEYWORD
FILEDF is the only acceptable entry.
Required.
8-15
FILE NAME
Name of the input or output file. Enter one of
the following names:
Required.
No default.
• C1BMNAM — Input file
• C1BMCOK — Matched records output file
• C1BMNCO — Unmatched records output
file
• C1BMIZP — Invalid ZIP Code output file.
• C1BMZP4 — ZIP+4 coded records output
file.
• C1BMSTA — Output statistics file. The only
required field on the parameter is record
length, positions 19-22, and may be any
numeric value.
17
RECORD FORMAT
Code indicating the format of the input and
output file records. Enter one of the following
codes:
• F — Fixed length with no end of record
delimiter, pads with blanks to set record
length (byte stream, mainframe fixed
blocked and unblocked).
Required.
Default is F.
NOTE: Not
valid for file
C1BMSTA.
• V — Mainframe and HPUX OpenVMS/VAX
input and output files
–
z/OS:4-byte record.
–
OpenVMS: 2- or 4-byte record.
• L — Line-sequential with delimiter(s) at end
of record.
–
Unix: New line, 1 byte.
• U — Records are variable-length and the
file contains an end-of-file indicator. (Unix
environments only)
NOTE: Under Unix, and Windows, variable
means ACUCOBOL-GT variable format files.
Output files can also be variable in Unix and
Windows.
19-22
RECORD LENGTH
The length, in bytes, of the records in the file.
For variable-length records, this is the
maximum record length.
NOTE: If you need to enter a 5-digit number,
use columns 18-22.
162
Required,
except for
z/OS.
No default.
Maximum is
32,760.
Software Release 4.0.0/March 2015
FILEDF
2
Table 21: FILEDF Parameter Fields (Part 2 of 3)
Position
24-28
Field Name
BLOCK SIZE
Description
The size, in bytes, of the blocks in the file.
Comments
Required,
except for
z/OS, Unix, and
VAX.
No default.
NOTE: Not
valid for file
C1BMSTA.
30-33
DEVICE TYPE
The type of device on which this file resides.
Enter one of the following codes:
TAPE
2311
2314
3310
3330
3340
3350
3370
3375
3380
FBA
34
TAPE REEL
HANDLING
Code indicating how to handle tape reels.
Enter one of the following codes:
• Blank — Tape reels are rewound at open or
close operations. For non-labeled tapes,
this will be changed to “U” if a multi-reel
situation is detected.
• M — Tape input file consists of more than
one standard-label file. The operator will be
queried for EOF/EOV at the end of each of
the input files.
Not used for
z/OS, Unix, or
VAX.
Default is
TAPE.
NOTE: Not
valid for file
C1BMSTA.
Not used for
z/OS.
Default is
blank.
NOTE: Not
valid for file
C1BMSTA.
• U — Tape reels are rewound at open
operations and unloaded at close
operations.
• X — Tape reels are not repositioned at
either open or close operations.
In general, use blank for intermediate
references to a single-reel file; “U” for multireel files and for the final reference to a
single-reel file; and “X” for files that require
non-standard positioning of tape reel (which
can be accomplished via MTC commands or
the equivalent).
35
LABEL TYPE
Code indicating whether the records on the file
have standard or omitted labels. Enter one of
the following codes:
• N — No labels
Default is S.
NOTE: Not
valid for file
C1BMSTA.
• S — Standard labels.
Working With CODE-1 Plus
163
2
Parameter Reference
Table 21: FILEDF Parameter Fields (Part 3 of 3)
Position
39-46
50-56
Field Name
EXIT ROUTINE
NAME
NUMBER OF
RECORDS TO SKIP
Description
Comments
Name of the input exit routine that should be
called when CODE-1 Plus is ready to read a
record from this file, or the name of the output
exit routine that should be called when
CODE-1 Plus is ready to write a record to the
file.
Optional.
No default.
Name must be
entered leftjustified.
Number of records CODE-1 Plus should skip
before selecting the first record.
Optional.
No default.
NOTE: Not
valid for file
C1BMSTA.
NOTE: Not
valid for file
C1BMSTA.
58-64
66-72
164
FRACTIONAL
RECORD
SELECTION
MAXIMUM
NUMBER OF
RECORDS
Number indicating the fraction of records in
the file that should be processed. CODE-1 Plus
assumes a decimal point before the first digit.
Optional.
No default.
NOTE: A number greater than 5000000 selects
the entire file.
NOTE: Not
valid for file
C1BMSTA.
Maximum number of records CODE-1 Plus
should read from or write to this file.
Optional.
No default.
NOTE: Not
valid for file
C1BMSTA.
Software Release 4.0.0/March 2015
FIRMNM
2
FIRMNM
The optional FIRMNM parameter defines the location and length of firm names
(company names) in the input record.
The standardized firm name is the firm name derived from an address match and is the
firm name stored from the USPS ZIP+4 database file. Alternatively, it may be the input
firm name in uppercase format when the standardized firm name could not be
derived from a successful address match.
If you include the FIRMNM parameter in your job, when CODE-1 Plus processes a
record, it compares the firm name in the input record with firm names that are
associated with the matched address. Each firm name has a ZIP+4 Code associated
with it. The ZIP+4 Codes associated with firm names are more specific than other
ZIP+4 Codes. If a firm name match is found, CODE-1 Plus will assign that ZIP+4 Code
to the record instead of the ZIP+4 Code that would be assigned based on the address
alone. For example, let’s consider the high-rise office building where an address is
located. The building, which has six floors, has the ZIP+4 Code of 1852. There are 4
firms within this building that are assigned ZIP+4 Codes by the USPS, as follows:
Suite Number
204
300
600
600
Firm Name
State Farm
Maxima
Comnet
PB Software
ZIP+4 Code
1805
1834
1882
1844
Mail that is addressed to one of these suites and does not have a firm name is assigned
a ZIP+4 Code of 1852, which is the default building code for the high-rise building.
Mail that contains one of the firm names shown above is assigned the appropriate
ZIP+4 Code for the firm, regardless of suite number.
For instance:
Input Address
PITNEY BOWES SOFTWARE INC
ONE GLOBAL VIEW
ZIP+4 Code Assigned
ONE GLOBAL VIEW
1852
PITNEY BOWES SOFTWARE INC
ONE GLOBAL VIEW
1844
ONE GLOBAL VIEW
1852
Working With CODE-1 Plus
1844
165
2
Parameter Reference
CODE-1 Plus will append a missing suite to the address if a firm name was obtained.
A missing suite is appended only if the input suite was missing and a match to the firm
name was found. The following example shows how CODE-1 Plus appends a missing
suite:
The apartment return code is “F” when this happens.
NOTE: USPS CASS regulations require SuiteLink processing for CASS certification
and to generate the USPS Form 3553 (USPS CASS Summary Report).
NOTE: The FIRMNM parameter is required when you use the STELNK parameter
to perform SuiteLink processing.
Table 22: FIRMNM Parameter Fields (Part 1 of 2)
Position
Field Name
Description
Comments
1-6
KEYWORD
FIRMNM is the only acceptable entry.
Required.
8-10
Location of
FIRM NAME
Specify one of the following to indicate
the location of the firm name in the input
record.
Required.
No default.
• nnn — Specify 1-4 numerics to
indicate the location of the firm name
in your input record.
• U — Specify U in position 8 to indicate
the firm name is located within
specified input address lines.
NOTE: If U is used in this field, the option
L is required in the ADDRDF parameter
in position 8.
12-13
166
Length of
FIRM NAME
Length of the firm name in the input
record (the maximum is 40).
Required if an
input location is
specified in
positions 8-10.
No default.
Software Release 4.0.0/March 2015
FIRMNM
2
Table 22: FIRMNM Parameter Fields (Part 2 of 2)
Position
Field Name
Description
Comments
15-17
Location for
STANDARDIZED
FIRM NAME
Location for the standardized firm name
on the output record.
Optional.
No default.
19-20
Length of
STANDARDIZED
FIRM NAME
Length of the standardized firm name on
the output record.
Optional.
No default.
72
FIRM NAME
DISPOSITION
INDICATOR
Code indicating what should be stored in
cases where the standardized firm name
was not stored, because no address
match was found, or a multiple address
match was found. Enter one of the
following codes:
Optional.
Default is I.
• I — Store the extracted input.
• B — Store blanks.
• X — Store nothing.
Working With CODE-1 Plus
167
2
Parameter Reference
G9 OUT
The optional G9 OUT parameter defines the output storage locations for the
elements returned by Geographic Coding Plus and GeoTAX. These elements are
written to records in the C1BMCOK and C1BMZP4 files for all records successfully
coded by Geographic Coding Plus or GeoTAX. If you include this parameter in your
CODE-1 Plus job, you must also include the G9ZIP9 parameter. For more
information, refer to the your Geographic Coding or GeoTAX User’s Guide.
NOTE: You must have Geographic Coding Plus or GeoTAX for CODE-1 Plus to
process this parameter.
Table 23: G9 OUT Parameter Fields (Part 1 of 2)
Position
Field Name
Description
Comments
1-6
KEYWORD
G9 OUT is the only acceptable entry.
Required.
8-10
Location for
GENERAL
RETURN CODE
Location on the output record for the
1-character General Return Code. One of
the following codes is stored:
Optional.
No default.
• Blank — No 5-digit ZIP Code match was
found.
• 5 — 5-Digit ZIP Code match was
successful.
• 9 — 9-Digit ZIP Code match was
successful.
12-14
Location for
CENSUS
GEOCODE
The starting location on the output record
for the following information:
Optional.
No default.
2-character FIPS state code
3-character FIPS county code
6-character census tract
1-character census block group.
168
16-18
Location for
FIPS STATE CODE
Location on the output record for the
2-character FIPS state code.
Optional.
No default.
20-22
Location for
FIPS COUNTY
CODE
Location on the output record for the
3-character FIPS county code.
Optional.
No default.
24-26
Location for
CENSUS TRACT
Location on the output record for the
6-character census tract.
Optional.
No default.
28-30
Location for
CENSUS BLOCK
GROUP
Location on the output record for the
1-character census block group.
Optional.
No default.
Software Release 4.0.0/March 2015
G9 OUT
2
Table 23: G9 OUT Parameter Fields (Part 2 of 2)
Position
Field Name
Description
Comments
32-34
Location for
STATE
ABBREVIATION
Location on the output record for the
2-character state abbreviation.
Optional.
No default.
36-38
Location for
COUNTY NAME
Location on the output record for the
20-character county name.
Optional.
No default.
40-42
Location for
MSA CODE
Location on the output record for the
4-character MSA code.
Optional.
No default.
44-46
Location for
MSA NAME
Location on the output record for the
50-character MSA name.
Optional.
No default.
48-50
Location for
LATITUDE/
LONGITUDE
Location on the output record for the
16-character latitude/longitude (4-decimal
precision).
Optional.
No default.
52-54
Location for
LATITUDE/
LONGITUDE
LEVEL
Location on the output record for the
1-character latitude/longitude level.
Optional.
No default.
56-58
Location for
LATITUDE/
LONGITUDE
COORDINATE
Location for latitude/longitude coordinate
(6-decimal precision).The coordinate has a
total length of 20 characters: 9 digits
(decimal implied after sixth position), 1
directional, 9 digits (decimal implied after
sixth position), 1 directional.
Optional.
No default.
Working With CODE-1 Plus
169
2
Parameter Reference
G9XOUT
The optional G9XOUT parameter is used to define output storage locations for
elements returned by Geographic Coding Plus or GeoTAX. These elements are
written records in the C1BMCOK and C1BMZP4 files for all records successfully
coded by Geographic Coding Plus or GeoTAX and are in addition to those returned
via the G9 OUT parameter. If you include this parameter in your CODE-1 Plus job,
you must also include the G9ZIP9 parameter. You must have Open Systems
Geographic Coding Plus or GeoTAX for CODE-1 Plus to process this parameter. For
more information, refer to the your Geographic Coding or GeoTAX User’s Guide.
NOTE: The GeoTAX output key and the GeoTAX Return Code options in this
parameter are only available to GeoTAX customers who are also licensed users of
the Vertex Quantum or ComTax21 products. Additional information on this
subject can be found in the GeoTAX User’s Guide.
Table 24: G9XOUT Parameter Fields (Part 1 of 3)
Position
Field Name
Description
Comments
1-6
KEYWORD
G9XOUT is the only acceptable entry.
Required.
8-10
Location for
PLACE CODE
Location on the output record for the
5-character place code.
Optional.
No default.
NOTE: This option is only available for
GeoTAX customers.
12-14
Location for
PLACE NAME
Location on the output record for the
40-character place name returned by
Geographic Coding Plus.
Optional.
No default.
NOTE: This option is only available for
GeoTAX customers.
16-18
Location for
MCD/CCD
Location on the output record for the
5-character Minor Civil Division/Census
County Division (MCD/CCD) returned by
Geographic Coding Plus.
Optional.
No default.
20-22
Location for
CONFIDENCE CODE
Location on the output record for the
4-character confidence code returned by
Geographic Coding Plus.
Optional.
No default.
NOTE: Spaces are used for the last three
characters for compatibility with prior
Geographic Coding releases.
170
Software Release 4.0.0/March 2015
G9XOUT
2
Table 24: G9XOUT Parameter Fields (Part 2 of 3)
Position
24-26
Field Name
Location for
PRIZM CLUSTER
Description
Location on the output record for the
2-character PRIZM cluster returned by
Geographic Coding Plus.
Comments
Optional.
No default.
NOTE: This option is only available for
Geographic Coding customers.
28-30
Location for
PRIZM CLUSTER
CODE NAME
Location on the output record for the
20-character PRIZM cluster code name
returned by Geographic Coding Plus.
Optional.
No default.
NOTE: This option is only available for
Geographic Coding customers.
32-34
Location for
PRIZM SOCIAL
GROUP CODE
Location on the output record for the
2-character PRIZM cluster social group
code returned by Geographic Coding Plus.
Optional.
No default.
NOTE: This option is only available for
Geographic Coding customers.
36-38
Location for
PRIZM SOCIAL
GROUP NAME
Location on the output record for the
20-character PRIZM cluster social group
name returned by Geographic Coding
Plus.
Optional.
No default.
NOTE: This option is only available for
Geographic Coding customers.
40-42
Location for
CLASS CODE
Location on the output record for the
2-character class code.
Optional.
No default.
NOTE: This option is only available for
GeoTAX customers.
44-46
Location for
INCORPORATED
FLAG
Location on the output record for the
1-character incorporated flag, which
specifies whether the place is
incorporated or unincorporated as stored
in the U.S. Department of Commerce FIPS
Place Code Roster. One of the following
codes is stored:
Optional.
No default.
• Blank — Not in a roster
• I — Incorporated
• O — Unincorporated.
NOTE: This option is only available for
GeoTAX customers.
48-50
52-54
Working With CODE-1 Plus
Location for
LAST ANNEXED
DATE
Location in the output record for the
7-character last annexed date (MM/YYYY).
Location for
LAST UPDATED
DATE
Location in the output record for the
7-character last updated date (MM/YYYY).
Optional.
No default.
NOTE: This option is only available for
GeoTAX customers.
Optional.
No default.
NOTE: This option is only available for
GeoTAX customers.
171
2
Parameter Reference
Table 24: G9XOUT Parameter Fields (Part 3 of 3)
Position
56-58
60-62
64-66
Field Name
Description
Comments
Location for
LAST VERIFIED
DATE
Location in the output record for the
7-character last verified date.
Location for
GEOTAX OUTPUT
KEY
Location in the output record for the
9-character GeoTAX output key.
Location for
GEOTAX RETURN
CODE
Location in the output record for the
GeoTAX return code.
Optional.
No default.
NOTE: This option is only available for
GeoTAX customers.
Optional.
No default.
NOTE: This option is only available for
GeoTAX customers.
Optional.
No default.
• 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.
NOTE: This option is only available for
GeoTAX customers.
172
Software Release 4.0.0/March 2015
G9ZIP9
2
G9ZIP9
The optional G9ZIP9 parameter is used to define the location and format of the ZIP
Code and ZIP+4 Code for Geographic Coding Plus or GeoTAX. If you include the G9
OUT and/or the G9XOUT parameters in your job, you must also include the G9ZIP9
parameter. You must have Geographic Coding Plus or GeoTAX for this parameter to
be processed by CODE-1 Plus. For more information, refer to the your Geographic
Coding or GeoTAX User’s Guide.
Table 25: G9ZIP9 Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
G9ZIP9 is the only acceptable entry.
Required.
8-10
Location of
ZIP CODE
The location on the record, after address
matching has taken place, of the ZIP
Code that should be used for Geographic
Coding.
Required.
No default.
NOTE: In most cases, this is the output
location you specified on the Z5 OUT
parameter. However, you can specify the
location of the input ZIP Code if your
CODE-1 Plus output elements do not
over-write that location.
12
Format of
ZIP CODE
The format of the ZIP Code that can be
found in the location you specified in
positions 8-10. Enter one of the
following codes:
Optional.
Default is C.
• C — 5-character format
• P — 3-character packed decimal
format.
14-16
Location of
ZIP+4 CODE
The location on the record, after address
matching has taken place, of the ZIP+4
Code that should be used for Geographic
Coding. If you leave this field blank, the
Geographic Coding results will be based
on the 5-digit ZIP Code only.
Optional.
No default.
NOTE: In most cases, this is the output
location you specified on the Z4 OUT
parameter. However, you can specify the
location of the input ZIP+4 Code if your
CODE-1 Plus output elements do not
over-write that location.
18
Format of
ZIP+4 Code
The format of the ZIP+4 Code that is
found in the location you specified in
positions 14-16. Enter one of the
following codes:
Optional.
Default is C.
• C — 4-character format
• P — 3-character packed decimal
format.
Working With CODE-1 Plus
173
2
Parameter Reference
HEADER
The required HEADER parameter is used to specify a date and text to be printed at
the top of every page of each report and, if desired, to limit processing to a specified
ZIP Code range.
NOTE: The HEADER parameter is validated for correct start/stop ZIP Code
columns and for a blank in column 18 (between the date and heading text). An
error will occur if your parameter is not adjusted from previous releases.
Table 26: HEADER Parameter Fields
Position
174
Field Name
Description
Comments
1-6
KEYWORD
HEADER is the only acceptable entry.
Required.
8-17
DATE
The date that you want printed at the top
line of the first page of each report.
Optional.
Default is to print
the system date.
19-58
HEADING
The text you want to be printed on the top
line of every page of each report.
Optional.
No default.
60-64
START ZIP CODE
The lowest ZIP Code you want
CODE-1 Plus to process. Records with
lower ZIP Codes are ignored.
Optional.
No default.
67-71
STOP ZIP CODE
The highest ZIP Code you want
CODE-1 Plus to process. Records with
higher ZIP Codes are ignored.
Optional.
No default.
Software Release 4.0.0/March 2015
LACS
2
LACS
The optional LACS parameter indicates whether to perform LACSLink processing and
whether to perform LACSLink processing before or after ZIP + 4 processing.
NOTE: USPS CASS regulations require LACSLink processing for CASS certification
and to generate the USPS Form 3553.
Table 27: LACS Parameter Fields (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:
Required.
Default is blank.
• Z — Perform the ZIP+4 processing
prior to LACSLink.
10
TERMINATE LACS
This option allows LACSLink to stop batch
jobs when a false-positive (seed record)
has been encountered:
Required.
Default is W.
• S — Shuts down CODE-1 Plus
processing when a false-positive
(seed record) is encountered.
• W — Allows CODE-1 Plus to continue
processing to completion of the entire
job, generating Form 3553.
NOTE: For more information, see
LACSLink Seed Record Reporting in
Chapter 11.
Working With CODE-1 Plus
175
2
Parameter Reference
Table 27: LACS Parameter Fields (Part 2 of 2)
Position
14
Field Name
LACSLink Seed
Processing
Description
Comments
This option allows you to specify whether
to produce a “99” return code for LACS
seed record processing.
• Y — Do not produce “99” return code
for LACS seed record processing.
• N — LACS seed record processing
results in “99” return code.
NOTE: An “S” in position. 10 overrides
this option.
16
LACSLink Memory
Module Size
Indicator
This option allows you to specify size of
LACSLink module.
Required
• Blank — LACS process will be using
Medium memory model (default).
• 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).
176
Software Release 4.0.0/March 2015
L CODE
2
L CODE
The optional L CODE parameter defines the location and length of a list code in the
input record.
NOTE: There is an identical C1BM00XL driver program that allows for up to
10,000 list codes, and requires 2.25 MB of memory to run. (The standard
C1BM00 driver program allows for 200 list codes, and requires 390 K of memory.)
To take advantage of the additional list code processing, change your control
language appropriately.
The term list code comes from the practice of merging several mailing lists together,
using a code imbedded in the records to identify the source list of each record. You
can use the L CODE parameter to designate any field of 9 bytes or less in the input
records. CODE-1 Plus has four reports that print information about your job by list
code. The most common use of the L CODE parameter is to identify the list where a
record originated. You can then use the list code reports to analyze the quality of the
addresses on each of your original mailing lists.
Table 28: LCODE Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
L CODE is the only acceptable entry.
Required.
8-10
Location of
LIST CODE
Location on the input record of the list
code.
Required.
No default.
12
Length of
LIST CODE
Length of the list code.
Required.
No default. Must
be 9 bytes or
less.
14-22
CLIENT CODE
1-9 character Client Code.
Optional.
24-31
DATE RECEIVED
The date the file was received in
CCYYMMDD format.
Default is blank.
50-52
Location of SYSTEM
DATE
Location on the output record of the
system date.
Optional.
NOTE: If only this field is specified, all
other fields on this parameter record
become optional. The format is
MMDDCCYY.
Working With CODE-1 Plus
177
2
Parameter Reference
LISTID
The optional LISTID parameter prints the name or ID of the current
name-and-address input file in box B4 of USPS Form 3553, and the number of nameand-address lists used to produce the current mailing in box B5.
NOTE: You can define one LISTID parameter in a job.
Table 29: LISTID Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
LISTID is the only acceptable entry.
Required.
8-27
LIST ID
The name or ID of the current nameand-address list.
Required.
No default.
29-48
LIST ID, CONTINUED
More text indicating the name or ID for
the current name-and-address list.
Optional.
No default.
50-54
NUMBER OF LISTS
A 5-digit number indicating the number
of lists used to produce the mailing.
Optional.
For example, if you want to tell
CODE-1 Plus that you used one list, the
number entered here would be 00001.
178
Software Release 4.0.0/March 2015
LISTNM
2
LISTNM
The optional LISTNM parameter prints the List Processor’s name on the USPS Form
3553 in box B1. The list processor’s name is the name of the company who coded the
name and address list(s) and/or performed the ZIP+4 barcoding using CASS-certified
software. You can define up to three lines of information to identify the list processor,
because box B1 has a limited number of characters across, but has three print lines.
NOTE: You can define one LISTNM parameter in a job.
Table 30: LISTNM Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
LISTNM is the only acceptable entry.
Required.
8-27
LIST PROCESSOR
NAME
A 20-character name that identifies the
organization that coded the name and
address list(s) and/or performed the
ZIP+4 barcoding using CASS-certified
software.
Required.
No default.
29-48
LIST PROCESSOR
NAME CONTINUED 2
Another 20-character field that you can
use to identify the list processor of this
name-and-address list.
Optional.
No default.
50-69
LIST PROCESSOR
NAME CONTINUED 3
Another 20-character field that you can
use to identify the list processor of this
name-and-address list.
Optional.
No default.
Working With CODE-1 Plus
179
2
Parameter Reference
LOTOUT
The optional LOTOUT parameter tells CODE-1 Plus where on the output record to
store the information returned from the Line of Travel Master file.
NOTE: Line of Travel is NOT the same as a Walk Sequence Code. If you are trying
to obtain Walk Sequence Codes, they are provided through licensed DSF2
(Delivery Sequence File) Vendors.
Ordinarily, to sort mail in line of travel sequence, you must sort your mail by ZIP
Code, Carrier Route, Line of Travel code, ZIP+4 Code, and DPBC (delivery point
barcode) add-on. The DPBC must be sorted in either ascending or descending
sequence based on the alphabetic portion of the Line of Travel code. Instead of doing
this cumbersome task, two sequence fields are provided so the entire sortation string
can be sorted in ascending sequence.
A two-character alternate alphanumeric sequence field is returned based upon the
DPBC and the alphabetic portion of the Line of Travel Code. This two-character field
consists of an uppercase letter followed by a single digit. The range of possible values
is from A0 through T9. The one-character hexadecimal sequence field works the same
way but has a range of values from hexadecimal “21” (binary numeric 33) to
hexadecimal “E8” (binary numeric 232). Both alternate sequence fields work the
same way to be used for sortation purposes. In other words, you do not need to post
both alternate sequence fields.
Table 31: LOTOUT Parameter Fields (Part 1 of 2)
Position
Field Name
Description
Comments
1-6
KEYWORD
LOTOUT is the only acceptable entry.
Required.
8-10
Location of
LOT RETURN CODE
Location on the output record for the
1-character LOT return code. One of the
following codes is stored:
Optional.
No default.
• 9 — ZIP+4 matched the LOT master
file.
• C — Call to LOT matcher failed.
• D — Default coded. ZIP+4 not found in
the LOT master file.
• F — Master file access failure
• V — Incompatible Master file
• Blank — ZIP Code and/or ZIP+4 was
neither numeric nor zeroes.
180
Software Release 4.0.0/March 2015
LOTOUT
2
Table 31: LOTOUT Parameter Fields (Part 2 of 2)
Position
Field Name
Description
Comments
12-14
Location of
NUMERIC PORTION
OF LOT CODE
Location on the output record for the
4-character LOT code (numeric portion).
Required.
No default.
16-18
Location of
ALPHABETIC
PORTION OF LOT
CODE
Location on the output record for the
1-character USPS sequence code.
Optional.
No default.
20-22
Location of
2-character
ALTERNATE
SEQUENCE CODE
(alphanumeric)
Location on the output record for the
2-character alternate sequence code
used for sortation purposes.
Optional.
No default.
24-26
Location of
1-character
ALTERNATE
SEQUENCE CODE
(hexadecimal)
Location on the output record for the
1-character alternate sequence code
used for sortation purposes.
Optional.
No default.
28
DISPOSITION
INDICATOR
Code indicating what should be stored in
cases where no LOT code was
determined. Enter one of the following
codes:
Optional.
Default is B.
• B — Store blanks.
• X — Store nothing.
Working With CODE-1 Plus
181
2
Parameter Reference
MAILER
The MAILER parameter is required if you are running DPV and optional if you are
not. It prints the mailer’s name and address on the USPS Form 3553 in box D2. The
name and address is of the individual whose signature appears in box D1. In DPV,
MAILER is used to supply information in the DPV SEED File in the unlikely event a
DPV Seed is encountered.
NOTE: You can define up to six MAILER parameters in a job to accommodate up
to six lines of information that prints on the form.
If you are running DPV, you must have a set of five MAILER parameter records as
input to program C1BM00. The five parameters are necessary in case a DPV seed
record violation occurs. The above information is required in such cases. The format
must be as follows:
Record No.
Contents of Positions 1-137
1
Company name
2
Street address
3
City
4
State abbreviation
5
9-digit ZIP
State abbreviation must be in positions 8-9. ZIP and ZIP+4 may be separated by a
space, a hyphen, or be contiguous.
Table 32: MAILER Parameter Fields
Position
182
Field Name
Description
Comments
1-6
KEYWORD
MAILER is the only acceptable entry.
Required.
8-37
MAILER NAME
The 30-character name and address of the
individual whose signature appears in box D1 of
USPS Form 3553. If you leave this field blank,
the corresponding line in box D2 on USPS Form
3553 remains blank.
Required.
No default.
Software Release 4.0.0/March 2015
MOVE I
2
MOVE I
The optional MOVE I parameter allows you to rearrange the pieces of the input
record before the record is processed. This feature enables you to rearrange the
components of your input records before any other CODE-1 Plus processing takes
place. Note that the information you identify is copied to the location you specify,
but it is not removed from its original location in the input record. This feature is
useful for “saving” data that might otherwise be overwritten by data returned by
CODE-1 Plus. A maximum of 100 MOVE I parameters can be defined for a job. They
are processed one at a time, in sequence from top to bottom.
Before CODE-1 Plus does any processing, it first copies the entire input record into
an input record array. Then, if you specify any MOVE I operations, CODE-1 Plus
copies the entire record into a temporary work area. It then takes data from a
specified position in the work area, and puts it in a specified position in the input
record array. Once CODE-1 Plus executes all of the MOVE I operations, it clears the
work area and processes the record as it now appears in the input record array.
For example, let’s use an input record with a structure as follows:
AAAAABBBBBCCCCC
If we move the information in positions 11-15 to positions 1-5, CODE-1 Plus copies
the record to the work area, and executes the move operation. When the operation is
complete, our input record array and work area is:
Input Record Array
Work Area
CCCCCBBBBBCCCCC
AAAAABBBBBCCCCC
Then, if we move the information from positions 1-5 to positions 11-15, our input
record array and work area appear as follows:
Input Record Array
Work Area
CCCCCBBBBBAAAAA
AAAAABBBBBCCCCC
NOTE: This feature does not alter your input name-and-address file.
Working With CODE-1 Plus
183
2
Parameter Reference
Table 33: MOVE I Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
MOVE I is the only acceptable entry.
Required.
8-10
Location of
SOURCE
Location in the work area of the
information to be copied. Optionally, you
can enter one of the following codes to
copy one of the following types of generic
information to the target location:
Required.
No default.
• SPC — Spaces
• X00 — Binary zeros
• ZRO — Character zeros.
184
12-13
Length of
SOURCE/TARGET
Length of the information to be copied to
the target location.
Required.
No default.
15-17
Location of
TARGET
Location in the input array to which you
want the source information copied.
Required.
No default.
Software Release 4.0.0/March 2015
MOVE O
2
MOVE O
The optional MOVE O parameter allows you to rearrange pieces of the output record
before the record is written to the output file. CODE-1 Plus processes the record and
copies it to an output record array. Then, if you specify any output move operations,
CODE-1 Plus copies the entire record to a temporary work area, and then copies data
from a specific location in the work area back to a specific location in the output
record array. This information is then written directly to your output file (or passed
to an output exit routine). A maximum of 100 MOVE O parameters can be defined for
a job. They are processed one at a time, in sequence from top to bottom.
Table 34: MOVE O Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
MOVE O is the only acceptable entry.
Required.
8-10
Location of SOURCE
Location in the work area of the
information to be copied. Optionally, you
can enter one of the following codes to
copy different types of generic
information to the target location:
Required.
No default.
• SPC — Spaces
• X00 — Binary zeros
• ZRO — Character zeros.
12-13
Length of SOURCE/
TARGET
Length of the information to be copied to
the target location.
Required.
No default.
15-17
Location of TARGET
Location in the output record to which
you want the source information copied.
Required.
No default.
Working With CODE-1 Plus
185
2
Parameter Reference
NTHSEL
The optional NTHSEL parameter specifies that, when you run your job, CODE-1 Plus
processes a fraction of your input records or every nth input record and ignores the
others.
NOTE: You can define one NTHSEL parameter per job. You can use the NTHSEL
parameter in conjunction with the fractional sampling option on the FILEDF
parameter.
.
Table 35: NTHSEL Parameter Fields
Position
1-6
Field Name
KEYWORD
Description
Comments
Must be NTHSEL.
Required.
8-14 Sampling Method 1 — Including or Excluding Nth Number of Input Records
8-10
Nth NUMBER
The nth number of records the user
wants to either include or exclude from
the input records to be read.
Required if you do
not use Sampling
Method 2.
Valid numbers include 002 through 999.
12-14
INCLUDE/
EXCLUDE
OPTION
An option indicating whether to include
or exclude the specified nth number of
input records for processing:
Required if you do
not use Sampling
Method 2.
• INC — Include the nth number of
input records.
No default.
• EXC — Exclude the nth number of
input records.
16-22 Sampling Method 2 — Selecting a Fraction of Input Records
16-22
FRACTION OF
RECORDS
A 7-digit positive number specifying the
fraction of total input records to
process. A decimal point is implied
before the first digit.
Required if you do
not use Sampling
Method 1.
If FILEDF fractional processing is also
defined, CODE-1 Plus will select a
fraction (defined by FILEDF) of a
fraction (defined by NTHSEL).
186
Software Release 4.0.0/March 2015
NTHSEL
2
Performing Cross-Sectional Sampling
Cross-sectional sampling allows you to sample records throughout the file, from
beginning to end. You can specify cross-sectional sampling for the input name-andaddress file using a FILEDF parameter. With the NTHSEL parameter, you can specify
cross-sectional for the input name-and-address file only.
NOTE: If you specify cross-sectional sampling for the input name-and-address file
on the FILEDF and the NTHSEL parameter, a fraction of a fraction of the file will
be selected for processing.
To determine the number to enter in the FILEDFs 7-character DECIMAL FRACTION
field, divide the number of records you want to process by the number of records in
the file. This gives you a decimal number. Drop the decimal, and type the first 7 digits
of the number. For example, suppose you wanted to process 2,000 records from a file
containing 102,986 records. To select 2,000 records for processing, divide 102,986
into 2,000. The answer is .0194201153. Drop the decimal and keep 7 digits
(0194201) to type in the DECIMAL FRACTION field. This ensures that the 2,000
records processed are evenly distributed throughout the file. You can use this
sampling with the NTHSEL parameter as well.
Cross-Sectional Sampling of a File
First Record
Evenly Select
0.0194201 Records = 2,000 Records
Last Record
1 . . . . . . . . . . . . . . . . ......... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102,986
Figure 2: Example - Skipping and Limiting Records
Working With CODE-1 Plus
187
2
Parameter Reference
Including/Excluding Nth Records
Including or excluding every nth record in the input name-and-address file allows
you to process or bypass every user-specified number of records in the file. For
example, we want to specify to process every third record in the input file.
Nth Record Selection
First Record
Select Every Third Record
. . 3. .6 . .9 . .12 . .15 . .18 . .21 . .24 . .27 . .30 . .33 . .36 . .39 . .42 . .45 . .48.. etc.
Figure 3: Example - Including Every Third Record
NOTE: For the input name-and-address file, you can use the NTHSEL inclusion
and exclusion sampling function in conjunction with a FILEDF cross-sectional
function. This allows you to include/exclude a fraction of every nth record.
Table 36: NTHSEL Parameter
These Specifications
188
Define the Following
NTHSEL in positions 1
through 6
KEYWORD — Specify record sampling specifications.
003 in positions 8 through
10
Nth NUMBER — Three is the user-specified “nth” number.
INC in positions 12 through
14
INCLUDE/EXCLUDE OPTION — CODE-1 Plus will process (include)
every third record in the input name-and-address file.
Software Release 4.0.0/March 2015
PAGESZ
2
PAGESZ
The optional PAGESZ parameter indicates how many lines to print on each page of
either the Execution Log or the reports in the reports file.
NOTE: If you want to specify the number of lines to print on each page for both
the Execution Log and all of the other reports, you must include two PAGESZ
parameters in your job.
Table 37: 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 Execution Log or the
other reports.
Required.
Default is 60.
Minimum is 25;
maximum is 225.
12-14
REPORT OR LOG
CODE
Code indicating whether the specified
line number applies to the Execution Log
or to all of the other reports. Enter one of
the following codes:
Required.
Default is RPT.
• RPT — Reports
• XLG — Execution Log.
Working With CODE-1 Plus
189
2
Parameter Reference
PGMNAM
The optional PGMNAM parameter enables you to call an alternate address matching
module, instead of the standard C1MATCHB module. Additionally, the PGMNAM
parameter enables you to select an alternate module for your RDI processing. The
alternate address matching modules offer different memory models, from which you
can select one appropriate for your site. The default C1MATCHB module uses 3MB
of memory. A larger memory model generally improves performance.For more
information on DPV and RDI processing, turn to Chapter 6. The alternate memory
modules are the following:
•
Small (1 MB)
•
Medium (6 MB)
•
Large (12 MB)
•
Huge (28 MB).
NOTE: You can have multiple PGMNAM parameters in your C1BM00 job. One for
each RDI large memory model and one for a CODE-1 Plus memory model.
190
Software Release 4.0.0/March 2015
PGMNAM
2
Table 38: PGMNAM Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
PGMNAM is the only acceptable entry.
Required.
8-15
INTERNAL
PROGRAM NAME
The only acceptable entries for this field
are C1MATCHB and DPV040.
Required.
C1MATCHB — Address matching module.
C1MATCHB is the internal program name
of the CODE-1 Plus batch address
matching module (Pitney Bowes
delivered). The program in positions 17-24
will be called instead of C1MATCHB.
FOR RDI PROCESSING ONLY:
DPV040 — RDI Program override.
DPV040 is the internal program name of
the Residential Delivery Point Validation
module. If you wish to use the Alternate
RDI Large Memory Module for your RDI
processing, you must place DPV040 in this
position.
17-24
MEMORY
CONFIGURATION
PROGRAM NAME
The name of the program called instead of
C1MATCHB. You can choose the program
with a memory model appropriate for your
site. Enter one of the following program
names (memory models):
Required.
• C1MATCHS — Small memory model (1
MB)
• C1MATCHM — Medium memory model
(6 MB)
• C1MATCHL — Large memory model
(12 MB)
• C1MATCHH — Huge memory model
(28 MB). (This is not available on the
OpenVMS platforms.)
CODE-1 Plus customers should be aware
that batch jobs running with DPV Split,
LACSLink, and SuiteLink may require up to
377M of GETVIS.
FOR RDI PROCESSING ONLY:
DPV040L will be called instead of DPV040:
DPV040L — Alternate RDI Large Memory
Module.
NOTE: When DPV040 is in positions 8-15,
DPV040L is required in positions 17-24.
Working With CODE-1 Plus
191
2
Parameter Reference
REPORT
The optional REPORT parameter specifies the reports to print at the end of your
CODE-1 Plus job. The default, in all cases except the NDI report and the separate
USPS Form 3553, is to print the report. If you want to print all reports except the NDI
report and the separate USPS Form 3553, you do not have to define this parameter.
NOTE: NOTES: There are four reports that are printed automatically for all jobs:
parameter List; Execution Log; Control Totals; and Address Match Execution
Statistics. You cannot specify whether or not you want to print these reports. You
also cannot specify whether or not you want to print the USPS Form 3553. If you
are using a CASS-certified configuration, the report will print; otherwise, it will
not.
The Line of Travel reports will print only if the LOTOUT parameter is defined.
The REPORT parameter also gives you the option of printing the reports in all upper
case or in mixed case (upper and lower case).
NOTE: If you want to print the reports in mixed case, you must specify the
REPORT parameter at the top of the parameter list. If you include the REPORT
parameter near the bottom of the parameter list, it is possible that some of the
reports will still print in all upper case.
Table 39: REPORT Parameter Fields (Part 1 of 5)
Position
Field Name
Description
Comments
1-6
KEYWORD
REPORT is the only acceptable entry.
Required.
8
ANALYSIS OF
MATCHED RECORDS
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
10
ZIP+4 CODING BY
STATE
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
192
Software Release 4.0.0/March 2015
REPORT
2
Table 39: REPORT Parameter Fields (Part 2 of 5)
Position
12
Field Name
CARRIER CODING BY
STATE
Description
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Comments
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
14
ZIP+4 CODING BY
LIST CODE
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
Working With CODE-1 Plus
193
2
Parameter Reference
Table 39: REPORT Parameter Fields (Part 3 of 5)
Position
16
Field Name
CARRIER CODING BY
LIST CODE
Description
Comments
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• YPrint the report.
• NDo not print the report.
18
ZIP+4 CODING BY
3-DIGIT ZIP
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
20
CARRIER CODING BY
3-DIGIT ZIP
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
22
SUMMARY BY STATE
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
24
SUMMARY BY LIST
CODE
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
26
SUMMARY BY 3DIGIT ZIP
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
28
PRINT UPPER/
LOWER
CASE
Code indicating whether or not the
reports should be printed in all upper
case. Enter one of the following codes:
Optional.
Default is Y.
• Y — Print the reports in all upper
case.
• N — Print the reports in mixed case.
30
NATIONAL
DELIVERABILITY
INDEX (NDI) REPORT
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is N.
• Y — Print the report.
• N — Do not print the report.
194
Software Release 4.0.0/March 2015
REPORT
2
Table 39: REPORT Parameter Fields (Part 4 of 5)
Position
32
Field Name
LINE OF TRAVEL
CODING BY STATE
Description
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Comments
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
34
LINE OF TRAVEL
CODING BY LIST
CODE
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
36
LINE OF TRAVEL
CODING BY 3-DIGIT
ZIP CODE
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
38
DELIVERY POINT
VALIDATION
PROCESSING
SUMMARY
Code indicating whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
40
DELIVERY POINT
VALIDATION
PROCESSING BY
LIST CODE
Code indication whether this report is to
be printed. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print the report.
• N — Do not print the report.
42
44
Working With CODE-1 Plus
RESIDENTIAL
DELIVERY
INDICATOR (RDI)
PROCESSING
SUMMARY COUNTS
Code indicating whether the RDI counts
are to be printed on the DPV/RDI
Summary Report:
RESIDENTIAL
DELIVERY
INDICATOR (RDI)
PROCESSING
COUNTS BY LIST
CODE
Code indicating whether or not to print
this report. Enter one of the following
codes:
Optional.
Default is Y.
• Y — Print RDI counts.
• N — Do not print RDI counts.
Optional.
Default is Y.
• Y — Print the RDI List Code Report.
• N — Do not print the RDI List Code
Report.
195
2
Parameter Reference
Table 39: REPORT Parameter Fields (Part 5 of 5)
Position
70
Field Name
USPS FORM 3553
SEPARATE PRINT
FILE
Description
Comments
Code indicating whether or not to print
the USPS CASS Form 3553 in a separate
print file. Enter one of the following
codes:
Optional.
Default is N.
• Y — Print in a separate print file.
• N — Do not print in a separate print
file.
NOTE: To print the above reports, type an Y in the appropriate position on the
REPORT parameter. For all other reports, except the NDI report, the reports print
by default.
The NDI report is suppressed by default. The USPS CASS Form 3553 by default
does not print in a separate print file. The Y in position 70 specifies to print the
USPS CASS Form 3553 in a separate print file. The N in position 28 specifies to
print the reports in mixed case.
196
Software Release 4.0.0/March 2015
SA OUT
2
SA OUT
The optional SA OUT parameter allows you to specify where in the output file you
want the standardized address to be stored. The standardized address information is
formatted to conform to USPS conventions and matched against the master file.
Dropped information is dropped from the address during the standardization
process.
NOTE: Standardized addresses with and without apartment information do not
refer to individual records that can or cannot have apartment information
included in their addresses. Rather, we assume that all records have apartment
information, and we specify whether or not to store that information separately
from the rest of the standardized address.
Alias and Base Street Names
It is possible for a single street to have more than one name. In such cases, the USPS
differentiates between a base street name and one or more alias street names.
Typically, either the alias or the base refers to only a portion of the street (i.e., a
particular house range or ranges). A base name is the preferred name for the entire
street. Every street in the USPS database has one and only one base name. However,
a base street can have multiple alias names. The USPS has identified three types of
alias street names:
•
USPS preferred street name
•
Official street name change (as a result of a Chamber of Commerce Action)
•
Other.
If the alias street name is preferred, CODE-1 Plus always stores the alias name instead
of the base name. If the alias street name is an official street name change,
CODE-1 Plus always stores the base name. However, if the alias street name is of type
“other,” CODE-1 Plus stores the alias or base, depending on the option you chose on
the SA OUT parameter. Note that you never have the option of returning the alias
street name if the input address matches the base street name. It is important to
remember, however, that both the base street and the alias street are valid,
deliverable addresses.
For example, in Bethesda, Maryland there is a street called Rockville Pike. Another
valid name for Rockville Pike in Bethesda is Wisconsin Avenue. In this case, the USPS
designated Rockville Pike as the base street name and Wisconsin as the alias street
name.
Working With CODE-1 Plus
197
2
Parameter Reference
Let’s look at some sample input addresses to see what CODE-1 Plus would return (this
example assumes that all alias street names are of type “other”).
Table 40: Alias and Base Street Name Output
Input Address
Return Base Street if
Alias Street is Matched?
Output Address
9650 Wisconsin Avenue
Yes
9650 Rockville Pike
9650 Rockville Pike
Yes
9650 Rockville Pike
9650 Wisconsin Avenue
No
9650 Wisconsin Avenue
9650 Rockville Pike
No
9650 Rockville Pike
Using the INP Option
Instead of storing your output standardized address in a new location, you have the
option of storing it where the input address lines were located. To understand how
CODE-1 Plus stores your output address when you use the INP option in columns 1214 of the SA OUT parameter, it is important to remember that CODE-1 Plus
considers the most significant address line to be the one that was defined last on the
ADDRDF parameter. CODE-1 Plus follows the rules listed below when you specify the
INP option in columns 12-14 on the SA OUT parameter.
1. When an apartment number is located in an address line by itself, and the rest of
the street address is located in another address line, CODE-1 Plus will combine
the two lines into a single address line and store the new line where the most
significant of the two input lines was located.
2. If only one input address line actually contains data, the output address line will
be moved to the next most significant location, and the location that contained
the original address line will be blank. If the address line that is provided is
already in the most significant location, then no adjustment in address line
positions takes place.
3. If more than one address line is provided, and they are separated by one or more
blank address lines, no movement of address lines takes place.
4. If an address line is provided that is not part of a valid street address (i.e., C/O
JOHN DOE), then the following rules apply:
If this address line is the only one supplied, the match fails and no adjustment in
address line positions takes place.
If this address line is in the most significant location, and more than one other
address line is supplied, the match fails and no adjustment in address line
positions takes place.
198
Software Release 4.0.0/March 2015
SA OUT
2
If this address line is in the most significant location and only one other address
line is supplied, the match succeeds and the positions of the two address lines are
swapped.
NOTE: This swapping can only occur if the lengths of the input lines are the same.
If you use the INP option, and you also choose to store nothing if your standardized
address is too long, the standardized address is stored unless it is longer than two
input lines put together. In other words, even if CODE-1 Plus used only address
information from one input address line, it will overwrite two input address lines if
there is not enough room on one line alone.
The LACS Indicator
The Locatable Address Conversion Service (LACS) indicator describes records that
have been converted to the LACS system (which allows mailers to identify and convert
a rural route address to its new city-style address). Rural route addresses are being
converted and some city-style addresses are being modified so that emergency
vehicles (ambulances, police cars, etc.) can find these locations.
Private Mailbox Designation (PMB)
Commercial Mail Receiving Agents (CMRA) are private companies offering mailbox
rental services to individuals and businesses.
The USPS requires a private mailbox (PMB) designator within the address on mail
destined for delivery through a CMRA. The PMB address information is required to
exist separately from the delivery address of the CMRA, as shown in the following
example address:
John Doe
PMB 234
123 Main St Ste 10
Anytown, ST 12345-1234
Recipient
Private Mailbox within the CMRA
CMRA street address
CMRA City, State, and ZIP
If a PMB is present, CODE-1 Plus concatenates the PMB to the Address with
Apartment field.
Working With CODE-1 Plus
199
2
Parameter Reference
Table 41: SA OUT Parameter Fields (Part 1 of 6)
Position
Field Name
Description
Comments
1-6
KEYWORD
SA OUT is the only acceptable entry.
Required.
8-10
Location for
ADDRESS RETURN
CODE
Location on the output record for the
1-character address return code. One of the
following codes is stored:
Optional.
No Default.
• Blank — The address match attempt was
successful.
• A — Apartment number missing or not
found in database, and an apartment-level
match was required.
• B — Insufficient (or blank) address
information for a match.
• C — The record's probable correctness was
higher than the specified maximum.
• D — Information was dropped during the
address match attempt.
• H — House/Box number not found on this
street.
• L — The returned address was too long to
be stored.
• M — Multiple matches were found.
• S — Street name not found in ZIP Code.
• T — The complete standardized address
was too long to be stored and there is no
location specified in which to store the
address with secondary information. This
only occurs if you are storing the address
without the secondary information.
• U — Unavailable—auxiliary file processing.
• Z — ZIP Code was not found on database.
200
Software Release 4.0.0/March 2015
SA OUT
2
Table 41: SA OUT Parameter Fields (Part 2 of 6)
Position
Field Name
Description
Comments
12-14
Location for
ADDRESS WITH
APARTMENT
Location on the output record for the
standardized address, including apartment
information. Enter a location, or “INP” to store
the standardized address in the same location
as the input address. (INP is only valid if
ADDRDF col. 8 is L or M.)
Required.
No default.
16-17
Length of
ADDRESS WITH
APARTMENT
Length of the standardized address with
apartment information.
Required.
No default.
18
BLANK UNUSED
ADDRESS LINES
This option is only allowed when the “INP”
option is specified in columns 12-14. If set to
“X” then the unused address lines are blanked
out.
Optional
Storage conditions
— ADDRESS WITH
APARTMENT
Code indicating what should be stored when
the standardized address with apartment
number is too long, or if there was no match
found. Enter one of the following codes:
Optional.
Default is to
store
nothing.
19
Default: Do
not blank
out the input
address
lines.
• Blank — Store information indicated in
position 72.
• I — Store the input address
21-23
Location for
ADDRESS
WITHOUT
APARTMENT
Location on the output file for the
standardized address, excluding apartment
information.
Optional.
No default.
25-26
Length of
ADDRESS
WITHOUT
APARTMENT
Length of the standardized address without
apartment information.
Optional.
No default.
28
Storage conditions
— ADDRESS
WITHOUT
APARTMENT
Code indicating whether or not the
standardized address without apartment
number should be stored if the standardized
address with apartment has already been
stored. Enter one of the following codes:
Optional.
Default is to
store
nothing.
• Blank — Store nothing.
• X — Store the information anyway.
NOTE: If you enter “X,” this information is
stored even if it is longer than the specified
length for the receiving field. If it is too long,
the information will be truncated. A return
code of “L” will not be stored.
30-32
Working With CODE-1 Plus
Location for
APARTMENT/PMB
Location on the output record for the
apartment information. Use this output area
to store the PMB number when presented
separately in secondary input address line.
Optional.
No default.
201
2
Parameter Reference
Table 41: SA OUT Parameter Fields (Part 3 of 6)
Position
Field Name
Description
Comments
34-35
Length of
APARTMENT/PMB
Length of the apartment/PMB information on
the output record.
Optional.
No default.
37
Storage conditions
— APARTMENT/
PMB
Code indicating what should be stored in
positions 30-32. Enter one of the following
codes:
Optional.
Default is
blank.
• Blank — Do not store apartment
information if successfully stored in
standardized address with apartment.
• P — Store PMB number when unable to
store in primary address line due to
truncation.
• X — Store the apartment information
anyway.
39-41
Location for
ADDRESS SOURCE
CODE
Location on the output record for the
1-character code indicating which input
address line CODE-1 Plus used to obtain a
standardized address. One of the following
codes is stored:
Optional.
No default.
• M — Both address lines
• P — Primary address line only
• S — Secondary address line only
• Blank — No match was found.
43-45
Location for
DROPPED
INFORMATION
CODE
Location on the output record for the
1-character code indicating the type of
information dropped during the
standardization process. One of the following
codes is stored:
Optional.
No default.
• Blank — Either no match was obtained, or
no information was dropped.
• A — A street address was dropped in order
to obtain a Rural Route/Highway Contract/
or PO Box match.
• R — A Rural Route/Highway Contract/PO
Box/General Delivery address was dropped
in order to obtain a street address match.
• W — One or more characters were dropped
during the address parsing process.
202
Software Release 4.0.0/March 2015
SA OUT
2
Table 41: SA OUT Parameter Fields (Part 4 of 6)
Position
47-49
Field Name
Location for
LACS INDICATOR
Description
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:
Comments
Optional.
No default.
• Blank — Address was not LACS converted
(no change).
• L — Address was LACS converted (changed
to an urban address).
51
ALIAS/BASE
RETURN OPTION
Code indicating whether or not you want
CODE-1 Plus to return the base street name if
the input address matched an alias street.
Enter one of the following codes:
Optional.
Default is N.
• Y — Return the base street name.
• N — Return the alias street name.
NOTE: This option is only used when the alias
type code is “O” or “A.”
NOTE: No CASS Report is generated if you
enter Y. For a CASS-certified configuration
you must enter N.
53-55
Location for
ALIAS RETURN
CODE
Location on the output record for the
1-character alias return code. One of the
following codes is stored:
Optional.
No default.
• Blank — The address did not match an alias
street name.
• A — The address matched an alias street.
57-59
Location for
ALIAS TYPE CODE
Location on the output record for the
1-character alias type code. One of the
following codes is stored:
Optional.
No default.
• Blank — Street record matched was not an
alias street.
• A — Street record was abbreviated.
• 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.
Working With CODE-1 Plus
203
2
Parameter Reference
Table 41: SA OUT Parameter Fields (Part 5 of 6)
Position
60
Field Name
Storage conditions
— INFORMATION
DROPPED
Description
Comments
Code indicating whether the standardized
address should be stored when information
was dropped during the standardization
process. Enter one of the following codes:
• Blank — Store the information anyway.
Optional.
Default is to
store the
information
anyway.
• X — Do not store if information was
dropped.
62
MAXIMUM
ADDRESS
CORRECTNESS
Maximum acceptable address probability of
correctness to store the standardized
address. Enter a number between 0 and 9,
where 0 indicates the best case and 9
indicates the worst case.
Optional.
Default is 9.
64
MAXIMUM
OVERALL
CORRECTNESS
Maximum acceptable overall probability of
correctness to store the standardized
address. Enter a number between 0 and 9,
where 0 indicates the best case and 9
indicates the worst case.
Optional.
Default is 9.
66-68
Location for
PMB RETURN
CODE
Location on the output record for the
1-character code indicating the disposition of
the PMB number.
• Blank — No PMB found.
• A — Appended to standardized address.
• S — Secondary address input.
• L — Returned address was too long to be
stored.
69
Storage conditions
— MULTIPLE
STANDARDIZED
ADDRESSES
Code indicating whether the standardized
address should be stored when multiple
address matches were found. Enter one of the
following codes:
• Blank — Store the information indicated in
position 72.
• M — Store the standardized address
anyway.
70
Storage conditions
— MULTIPLE ZIP
CODE
Code indicating whether the standardized
address should be stored when multiple ZIP
Code matches were found. Enter one of the
following codes:
• Blank — Store the information indicated in
position 72.
• M — Store the standardized address
anyway.
204
Optional.
Default is to
store blanks
or nothing,
whichever is
indicated in
position 72.
Optional.
Default is to
store blanks
or nothing,
whichever is
indicated in
position 72.
Software Release 4.0.0/March 2015
SA OUT
2
Table 41: SA OUT Parameter Fields (Part 6 of 6)
Position
72
Field Name
DISPOSITION
INDICATOR
Description
Code indicating what should be stored in
cases where the standardized address was
not stored, either because no match was
found or because of specified storage
conditions. Enter one of the following codes:
Comments
Optional.
Default is B.
• B — Store blanks.
• X — Store nothing.
Working With CODE-1 Plus
205
2
Parameter Reference
SA2OUT
The optional SA2OUT parameter is a continuation of the SA OUT parameter which
allows you to specify where in the output file you want CODE-1 Plus to store the
standardized address.
Table 42: SA2OUT Parameter Fields (Part 1 of 2)
Position
Field Name
Description
Comments
1-6
KEYWORD
SA2OUT is the only acceptable entry.
Required.
8-10
Location for
PRIVATE MAILBOX
(PMB)
Location on the output record for the
formatted PMB when presented in a
separately-defined input address line.
Optional.
12-13
Length of
PRIVATE MAILBOX
(PMB)
Length of the PMB information on the
output record.
Required if the
location is
specified in
position 8-12.
15
Preferred Alias
Processing Indicator
Indicates if preferred alias processing
should be performed:
Required for
CASS
certification
• Y — Perform preferred alias
processing.
• N — Do not perform preferred alias
processing. (default)
NOTE: A “Y” in this position is required
to generate a CASS report. Selecting
“N” will generate a non-CASS-certified
configuration. No PS FORM 3553 will
be generated.
17-19
Location for
Preferred Alias
Processing Return
Code
Location on the output record for a
1-byte flag.
• Blank — No preferred alias
processing attempted.
• A — Input address matched to an alias
(preferred alias processing is only
attempted for base addresses).
• N — Did not match to preferred alias.
• Y — Matched to preferred alias.
21
Abbreviated Alias
Processing Indicator
Indicates if abbreviated alias processing
should be performed:
• Y — Perform abbreviated alias
processing.
• N — Do not perform abbreviated alias
processing. (default)
206
Software Release 4.0.0/March 2015
SA2OUT
2
Table 42: SA2OUT Parameter Fields (Part 2 of 2)
Position
23-25
Field Name
Location for
Abbreviated Alias
Processing Return
Code
Description
Comments
Location on the output record for a
1-byte flag.
• Blank — No abbreviated alias
processing attempted.
• B — Output address set to base
address.
• L — Original standardized address
length already <= max.
• N — Abbreviated alias not found for
input address.
• Y — Abbreviated alias found for input
address and used in output
standardized address.
50
Enhanced Alternate
High Rise Match
Storage Options
Code indicating whether the enhanced
alternate high rise match should be
returned. Enter one of the following
codes:
Optional.
Default is B
• B — Return Base Address.
• A — Return Alternate Address.
NOTE: Selecting A will generate a nonCASS-certified configuration. No PS
FORM 3553 will be generated.
52-54
Location for
Seasonal Delivery
Flags
Location of the 12-byte code indicating
when mail can be delivered to a specific
address:
• Y — Mail can be delivered.
• N — Mail cannot be delivered.
Working With CODE-1 Plus
207
2
Parameter Reference
SEQCHK
The optional SEQCHK parameter enables you to specify up to nine fields on the
input record, by which to check the sequence of the input file. Sequence errors are
indicated on the Execution Log, and if a record is bypassed, it does not affect the
Control Totals report. Field segments contain pieces of data in the input record.
NOTE: The total length of all sequence field lengths cannot exceed 255 bytes.
Table 43: SEQCHK Parameter Fields (Part 1 of 2)
Position
Field Name
Description
Comments
1-6
KEYWORD
SEQCHK is the only acceptable entry.
Required.
8
SEQUENCE ERROR
TREATMENT
Code indicating the action to take when a
sequence error is encountered in the input
file. Enter one of the following codes:
Optional.
No default.
• B — (Bypass) Bypass the offending record
and continue sequence checking.
• C — (Continue) Continue processing the
offending record and continue sequence
checking.
• E — (End of file) Bypass the offending
record, and then gracefully end the
process as if the input file had reached an
end-of-file.
• I — (Ignore) Continue processing the
offending record, but abandon any further
sequence checking.
NOTE: If there is a sequence error, it is
indicated in the Execution Log. If a record is
bypassed, it does not affect the Control
Totals report.
(10-15) Sequence Field Segment 1
10-12
17-19
24-26
31-33
38-40
45-47
52-54
59-61
66-68
208
Location of
SEQUENCE FIELD
SEGMENTS
Location of segments of the data to be
checked for an input file sequence error.
Required.
No default.
Software Release 4.0.0/March 2015
SEQCHK
2
Table 43: SEQCHK Parameter Fields (Part 2 of 2)
Position
Field Name
13
20
27
34
41
48
55
62
69
Format of
SEQUENCE FIELD
SEGMENTS
14-15
21-22
28-29
35-36
42-43
49-50
56-57
63-64
70-71
Length of
SEQUENCE FIELD
SEGMENTS
Working With CODE-1 Plus
Description
Code indicating whether or not a field
segment is in a packed format that should be
unpacked before checking the sequence.
Enter one of the following codes for each
segment:
Comments
Optional.
Default is
blank.
• Blank — Field segment is not packed.
• P — Field segment is packed.
Length of field segments. The total number
of field segments cannot exceed 255 bytes. If
the field segment is packed (“P” in previous
field), the field length cannot exceed 9.
Required.
No default.
209
2
Parameter Reference
STELNK
The optional STELNK parameter record allows you to activate the SuiteLink feature
of CODE-1 Plus. The following criteria must be met to call SuiteLink:
•
This parameter record is present.
•
A firm name is present and a valid ZIP Code, ZIP+4 Code, and primary number
exist.
•
A match has been made to a high-rise default record.
•
The CODE-1 Plus and SuiteLink databases are current.
NOTE: USPS CASS regulations require SuiteLink processing for CASS certification
and to generate the USPS Form 3553 (USPS CASS Summary Report).
NOTE: The FIRMNM parameter is required when you use the STELNK parameter.
Table 44: STELNK Parameter Fields (Part 1 of 3)
Position
Field Name
Description
Comments
1-6
KEYWORD
STELNK is the only acceptable entry.
Required.
8
SuiteLink Error
Shutdown Indicator
Determines whether to shut down when
SuiteLink reports an error.
Optional
Default is S.
• 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”.
• 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”.
210
Software Release 4.0.0/March 2015
STELNK
2
Table 44: STELNK Parameter Fields (Part 2 of 3)
Position
10
Field Name
SuiteLink Memory
Model Flag
Description
This option allows you to specify size of
SuiteLink memory module.
Comments
Required
• Blank — SuiteLink process will use the
Medium memory model (default.)
• 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:
Optional
• A — Business name matched.
• 00 — Business name not matched.
16-18
SuiteLink Match Code
Location
Location for SuiteLink match code:
Optional
• A — Matched
• 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:
Optional
• 1 — Exact match
• 2 — Acceptable match (one word not
matched)
• 3 — Unacceptable match (more than
one word not matched).
NOTE: You should ignore the Fidelity
Code if the MatchCode is not 'A'. The
Fidelity Code is '0' if the MatchCode is
B (no match), C (business name
consisted entirely of "noise" words), or
D (9-digit zip not recognized as a high
rise default).
Working With CODE-1 Plus
211
2
Parameter Reference
Table 44: STELNK Parameter Fields (Part 3 of 3)
Position
24
Field Name
Include/Exclude
Secondary
Description
Comments
Use this option 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.
Optional
• I — Include secondary information
from SuiteLink on the output address
line.
• 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.
Optional. Default
is I.
• I — Include the invalid input
secondary information.
• E — Exclude the invalid input
secondary information.
• Blank — Defaults to I.
212
Software Release 4.0.0/March 2015
TESTIT
2
TESTIT
The optional TESTIT parameter allows you to check the syntax of your job setup and
parameters before you run the entire job. This parameter has no fields.
If you have this parameter in your job, CODE-1 Plus will check the syntax of your
parameters, and print a parameter report so that you can ensure that the information
stored on the parameters is really what you intended to store. Then, if all looks good
and there are no errors, you can remove this parameter and submit the job to run.
Table 45: TESTIT Parameter Fields
Position
1-6
Working With CODE-1 Plus
Field Name
KEYWORD
Description
TESTIT is the only acceptable entry.
Comments
Required.
213
2
Parameter Reference
UFTxx
The optional UFTxx parameter allows you to specify text to print at the bottom of
every page of each report. You can specify up to four footer lines.
Table 46: 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:
Required.
No default.
• A — Left side of the line
• B — Right side of the line.
7-72
214
FOOTER TEXT
The text that you want to appear at the
bottom of every page of each report.
Required.
No Default.
Software Release 4.0.0/March 2015
UHDxx
2
UHDxx
The optional UHDxx parameter allows you to specify additional text to print at the
top of every page of each report. You can specify up to four header lines.
Table 47: UHDxx parameter Fields
Position
Field Name
Description
1-3
KEYWORD
UHD is the only acceptable entry.
4
LINE NUMBER
The header line number. Enter 1, 2, 3, or
4.
5
LINE SIDE
The side of the header line on which this
text should appear. Enter one of the
following codes:
Comments
Required.
Required.
No default.
• A — Left side of the line
• B — Right side of the line.
7-72
Working With CODE-1 Plus
HEADER TEXT
The text that you want to appear at the
top of each page of every report.
Required.
No Default.
215
2
Parameter Reference
Z4 OUT
The optional Z4 OUT parameter tells CODE-1 Plus where on the output record to
store the ZIP+4 Code and Delivery Point Barcode (DPBC) information.
Table 48: Z4 OUT Parameter Fields (Part 1 of 5)
Position
Field Name
Description
Comments
1-6
KEYWORD
Z4 OUT is the only acceptable entry.
Required.
8-10
Location for
ZIP+4 RETURN
CODE
Location on the output record for the
1-character ZIP+4 return code. One of the
following codes is stored:
Optional.
No default.
• Blank — The match attempt was
successful.
• 7 — The ZIP+4 was suppressed. Record
matched to an R777 (phantom) carrier
route.
• A — Apartment number missing or not
found in database, and an apartment-level
match was required.
• B — Insufficient (or blank) address match
information.
• C — The address probable correctness or
overall probable correctness was too high.
• D — Information was dropped.
• H — House/box number not found on
street.
• L — The standardized address was too
long.
• M — Multiple matches of equal quality were
found.
• N — The ZIP+4 Code wasn't stored because
the processing requirements specified that
it was not to be stored.
• S — Street name not found in ZIP Code.
• U — Unavailable—auxiliary file processing.
• V — The record was matched to a nondeliverable street address (in this case, the
ZIP+4 will be blank, but the carrier route
could have a value).
• Z — ZIP Code not found in database.
12-14
216
Location for
ZIP+4 CODE
Location on the output record for the ZIP+4
Code.
Optional.
No default.
Software Release 4.0.0/March 2015
Z4 OUT
2
Table 48: Z4 OUT Parameter Fields (Part 2 of 5)
Position
16
Field Name
Format of
ZIP+4 CODE
Description
Format of the ZIP+4 Code on the output
record. Enter one of the following codes:
Comments
Optional.
Default is C.
• C — 4-byte number
• P — 3-byte packed number
• - — 4-byte number stored with a preceding
hyphen (-).
18-20
Location for
DELIVERY POINT
BARCODE
Location on the output record for the
6-character delivery point barcode.
Optional.
No default.
22-24
Location for
DELIVERY POINT
BARCODE ADDON WITH CHECK
DIGIT
Location on the output record for the
2-character delivery point barcode add-on
with the 1-character check digit (a total of 3
characters is stored).
Optional.
No default.
26-28
Location for
MASTER FILE
VINTAGE DATE
Location on the output records for the master
file vintage date of the current master file.
Optional.
No default.
30
Format of
MASTER FILE
VINTAGE DATE
Code indicating the format of the master file
vintage date on the output records. Enter one
of the following formats:
Optional.
Default is C.
If a location
is specified in
this position,
a location for
ZIP+4 Code
and format of
ZIP+4 Code
must be
specified in
positions 1214 and 16 of
this
parameter.
• B — 2-byte binary format YYMM
• C — 4-byte character format YYMM
• P — 3-byte packed decimal format YYMM
• 3 — 3-byte binary format YYYYMM
• 6 — 6-byte character format YYYYMM
• 4 — 4-byte packed decimal format
YYYYMM.
32-34
Location for
Z4 CHANGE
RETURN CODE
Location on the output records for the Z4
Change Return Code. One of the following
codes is stored:
Optional.
No default.
• 0 — Address matching was not performed
for this record.
• 4 — Address matching was performed for
this record.
• 8 — A fatal error occurred.
Working With CODE-1 Plus
217
2
Parameter Reference
Table 48: Z4 OUT Parameter Fields (Part 3 of 5)
Position
Field Name
Description
Comments
36-38
Location for
DPBC ADD-ON
Location on the output record for the
2-character DPBC Add-on. Valid only when
positions 12-14 are defined.
Optional.
No default.
40-42
Location for
DPBC ADD-ON
CHECK DIGIT
Location on the output record for the
1-character DPBC Add-on Check Digit. Valid
only when positions 18-20 or 36-38 are
defined.
Optional.
No default.
58
Storage
conditions —
R777 CARRIER
ROUTE FOUND
Addresses with Carrier Route R777 are
phantom routes and are not eligible for street
delivery. Since these addresses are assigned
a ZIP + 4 code by the USPS, CODE-1 Plus
marks these addresses as deliverable. If you
do not want addresses with Carrier Route
R777 marked as deliverable, set this option to
Y and the following actions are performed for
the address:
Optional.
Default is to
store ZIP+4
(DPBC).
• No ZIP + 4 Code is assigned
• Address is not counted on the USPS Form
3553 (CASS Summary Report)
• DPV Footnote of R7 is returned
Valid values are:
• Y — Yes, if Carrier Route R777 is found, add
to the ZIP + 4 Suppressed Count on the
USPS Form 3553. R777 addresses are not
deliverable. Do not store the ZIP + 4
(DPBC).
• Blank — If Carrier Route R777 is found, do
not add to the ZIP + 4 Suppressed Count on
the USPS Form 3553. R777 addresses are
deliverable. Store the ZIP + 4 (DPBC).
60
Storage
conditions —
INFORMATION
DROPPED
Code indicating whether the standardized
ZIP+4 and DPBC should be stored when
information was dropped during the
standardization process. Enter one of the
following codes:
Optional.
Default is to
store the
information.
• X — Do not store if information was
dropped.
• Blank — Store the information anyway.
218
62
MAXIMUM
ADDRESS
CORRECTNESS
Maximum acceptable address probability of
correctness to store the standardized ZIP+4
and DPBC. Enter a number between 0 and 9,
where 0 indicates the best case and 9
indicates the worst case.
Optional.
Default is 9.
64
MAXIMUM
OVERALL
CORRECTNESS
Maximum acceptable overall probability of
correctness to store the standardized ZIP+4
and DPBC. Enter a number between 0 and 9,
where 0 indicates the best case and 9
indicates the worst case.
Optional.
Default is 9.
Software Release 4.0.0/March 2015
Z4 OUT
2
Table 48: Z4 OUT Parameter Fields (Part 4 of 5)
Position
68
Field Name
Storage
conditions —
MULTIPLE ZIP+4
Description
Code indicating whether the standardized
ZIP+4 and DPBC should be stored when
multiple ZIP+4 matches were found. Enter
one of the following codes:
• Blank — Store the information indicated in
position 72.
Comments
Optional.
Default is to
store
whatever is
indicated in
position 72.
• M — Store the standardized ZIP+4 and
DPBC anyway.
• N — Store the information indicated in
position 72 and write the record to the NCO
file.
70
Storage
conditions —
MULTIPLE ZIP
CODE
Code indicating whether the standardized
ZIP+4 and DPBC should be stored when
multiple ZIP Code matches were found. Enter
one of the following codes:
• Blank — Store the information indicated in
position 72.
Optional.
Default is to
store
whatever is
indicated in
position 72.
• M — Store the standardized ZIP+4 and
DPBC anyway.=
71
FILE
ALLOCATION —
ZIP+4 OF ZEROS
OR 9999
Indicator that specifies which output file to
write the record when ZIP+4 is zeros or
“9999.”
Default is
blank.
• Blank — Write the record to the COK file
• N — Write the record to the NCO file.
Working With CODE-1 Plus
219
2
Parameter Reference
Table 48: Z4 OUT Parameter Fields (Part 5 of 5)
Position
72
Field Name
DISPOSITION
INDICATOR
Description
Comments
Code indicating what should be stored in
cases where the standardized ZIP+4 and
DPBC were not stored, either because no
match was found, or due to storage
conditions. Enter one of the following codes:
Optional.
Default is B.
• B — Store blanks.
• I — Store input ZIP+4 Code.
• X — Store nothing.
NOTE: If you specify I, and the input ZIP+4
Code is non-numeric or all zeros, then
blanks are stored.
220
Software Release 4.0.0/March 2015
Z5 OUT
2
Z5 OUT
The optional Z5 OUT parameter specifies the location on the output record to store
the 5-digit ZIP Code information.
NOTE: Although Z5 OUT is an optional parameter, if you run a job without it,
CODE-1 Plus will not write any results to the C1BMCOK output file.
NOTE: CODE-1 Plus considers an input ZIP Code of 00000 to be invalid. If you
want to preserve an input ZIP Code that is all zeros, you will have to do so with
either a MOVE I parameter or an exit routine.
Working With CODE-1 Plus
221
2
Parameter Reference
Table 49: Z5 OUT Parameter Fields (Part 1 of 3)
Position
Field Name
Description
Comments
1-6
KEYWORD
Z5 OUT is the only acceptable entry.
Required.
8-10
Location for
ZIP CODE RETURN
CODE
Location on the output record for the
1-character ZIP Code return code. One of the
following codes is stored:
Optional.
No default.
• Blank — The match attempt was successful.
• 7 — The ZIP + 4 was suppressed. Record
matched to a Carrier Route R777 (phantom).
• A — Apartment number missing or not
found in database, and an apartment-level
match was required.
• B — Insufficient (or blank) address match
information.
• C — The address probable correctness or
overall probable correctness was too high.
• D — Information was dropped.
• E — External match—auxiliary file
processing.
• H — House/box number not found on street.
• L — The standardized address was too long.
• M — Multiple matches of equal quality were
found.
• N — The ZIP Code wasn't stored because
the processing requirements specified that
it was not to be stored.
• S — Street name not found in ZIP Code.
• Z — ZIP Code not found in database.
12-14
Location for
ZIP CODE
Location on the output record for the
standardized ZIP Code.
Optional.
No default.
16
Format of
ZIP CODE
Format of the standardized ZIP Code. Enter
one of the following codes:
Optional.
Default is C.
• C — 5-byte number
• P — 3-byte packed number.
222
Software Release 4.0.0/March 2015
Z5 OUT
2
Table 49: Z5 OUT Parameter Fields (Part 2 of 3)
Position
18-20
Field Name
Location for
SOURCE OF FINAL
ZIP CODE
Description
Comments
Location on the output record for the source of
the final ZIP Code, a 1-character code
reflecting the source of the final ZIP Code.
• B — No ZIP Code was determined.
• F — The final ZIP Code was determined from
the finance number.
• L — New address obtained from LACS
processing.
• M — The final ZIP Code was determined
from the ZIPMOVE database.
• Z — The original ZIP Code was retained.
22-24
Location for PO
BOX-ONLY ZIP
CODE
Location on the output record for the P. O. Boxonly ZIP Code indicator. Addresses located
within a P. O. Box-only delivery zone can only
receive postal delivery through the use of a
P. O. Box. No other postal delivery method is
available for these addresses.
Optional.
No default.
• Y — P. O. Box-only ZIP Code.
• Blank — Not a P. O. Box-only ZIP Code.
26-28
Location for VALID
ZIP CODE FLAG
Location on the output record for the Valid ZIP
Code flag.
Optional.
No default.
• Y — Input City, State, and ZIP Code
correspond.
• N — Input city, state, ZIP Code do not
correspond, or is invalid.
• Blank — ZIP Code could not be determined
for input address.
60
Storage conditions
— INFORMATION
DROPPED
Code indicating whether the standardized ZIP
Code should be stored when information was
dropped during the standardization process.
Enter one of the following codes:
Optional.
Default is to
store the
information.
• Blank — Store the information anyway.
• X — Do not store if information was dropped.
62
MAXIMUM
ADDRESS
CORRECTNESS
Maximum acceptable address probability of
correctness to store the standardized ZIP
Code. Enter a number between 0 and 9, where
0 indicates the best case and 9 indicates the
worst case.
Optional.
Default is 9.
64
MAXIMUM
OVERALL
CORRECTNESS
Maximum acceptable overall probability of
correctness to store the standardized ZIP
Code. Enter a number between 0 and 9, where
0 indicates the best case and 9 indicates the
worst case.
Optional.
Default is 9.
Working With CODE-1 Plus
223
2
Parameter Reference
Table 49: Z5 OUT Parameter Fields (Part 3 of 3)
Position
66
Field Name
UNIQUE ZIP CODE
HANDLING
Description
Comments
Code indicating whether the Input ZIP Code
should be returned if it is unique and does not
correlate with the input city/state.
• Blank — Do not store the Input ZIP Code.
• X — Store the information indicated in
position 72.
Optional.
Default is to
not store the
input ZIP
Code.
NOTE: If X is chosen, a non-CASS certified
configuration will be created. No PS 3553 Form
will be generated.
70
Storage conditions
— MULTIPLE ZIP
CODE
Code indicating whether the standardized
ZIP+4 and DPBC should be stored when
multiple ZIP Code matches were found. Enter
one of the following codes:
• Blank — Store the information indicated in
position 72.
Optional.
Default is to
store
whatever is
indicated in
position 72.
• M — Store the standardized ZIP+4 and
DPBC anyway.=
72
DISPOSITION
INDICATOR
Code indicating what should be stored in cases
where the standardized ZIP Code was not
stored either because no match was found, or
due to storage conditions. Enter one of the
following codes:
Optional.
Default is I.
• B — Store blanks.
• I — Store input ZIP Code.
• X — Store nothing.
NOTE: If you specify I, and the input ZIP Code
is non-numeric or all zeros, then blanks is
stored.
224
Software Release 4.0.0/March 2015
CHAPTER 3
Interactive Screen Reference
This chapter provides a complete reference for the CODE-1 Plus interactive screens.
Each screen is presented, along with its fields and function keys.
NOTE: The screens pictured in this chapter are shown as they appear under every
platform except VAX/VMS. Under VAX/VMS, the function keys shown on the screens
are not available. VAX/VMS users must enter commands in the Command field,
instead of pressing function keys.
The Command Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Concatenated Commands. . . . . . . . . . . . . . . . . . . . . . . . . .
Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Screens that Support Address Matching . . . . . . . . . . . . . . . . . . . . . .
Address Match Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Delivery Sequence Footnotes Screen. . . . . . . . . . . . . . . . . . . . . .
Miscellaneous Information/Base Address Screen . . . . . . . . . . .
Expanded Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Geographic Coding Information . . . . . . . . . . . . . . . . . . . . . . . . . .
Match Settings Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Elements Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parsed Elements Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Return Codes Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistics Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Address Stack Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Screens that Support Database Inquiry . . . . . . . . . . . . . . . . . . . . . . .
Apartments at a House Range . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cities in a State Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cities in a ZIP Code Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
City Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Firms in a House Range Screen . . . . . . . . . . . . . . . . . . . . . . . . . .
Houses on a Street Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Streets in a City or Streets in a ZIP Code Screen . . . . . . . . . . . .
Geographic Coding Plus Interface . . . . . . . . . . . . . . . . . . . . . . . .
Screens that Support Site Customization . . . . . . . . . . . . . . . . . . . . .
Administration Sign-on Screen. . . . . . . . . . . . . . . . . . . . . . . . . . .
Interactive Customization Screens . . . . . . . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
227
232
232
233
233
236
239
242
244
246
249
252
254
262
266
270
270
273
276
278
281
283
286
288
294
294
296
225
3
Interactive Screen Reference
Database Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customization File Administration . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Backup and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Repair, Re-Initialization, and Password Display . . . . . . . . .
Batch Uncoded Records Interface (G1CPBNC) . . . . . . . . . . . . . . . . .
How it Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UR COMMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UW COMMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description of Supplied Sample G1CPBNC . . . . . . . . . . . . . . . . .
226
304
305
305
305
307
307
308
309
310
311
Software Release 4.0.0/March 2015
The Command Field
3
The 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).
Table 1: Valid Entries in the Command Field (Part 1 of 6)
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.
Press F8
F8 with a number
between 1 and 9998 on
the command line will
scroll down that
number of lines.
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.
EXTEND
Allows you to override database expiration,
so you can match interactively with an
expired database.
None.
NOTE: You must use the “EXTEND”
command each time an expired database is
identified by the software initialization.
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.
Working With CODE-1 Plus
227
3
Interactive Screen Reference
Table 1: Valid Entries in the Command Field (Part 2 of 6)
Command
Description
Alternate Method
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.
UP
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.
Press F7
F7 with a number
between 1 and 9998 on
the command line will
scroll up that number of
lines.
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.
Customizing Interface Commands
228
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
Software Release 4.0.0/March 2015
The Command Field
3
Table 1: Valid Entries in the Command Field (Part 3 of 6)
Command
Description
Alternate Method
Database Inquiry Commands
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.
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 F4.
or
Position your cursor on
the desired line and
press F4.
Type the desired line
number in the
Command field and
press F2.
or
Position your cursor on
the desired line and
press F2.
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>
Move to the Cities in a ZIP Code screen for
the ZIP Code that is displayed on line <line
number>.
Type the desired line
number in the
Command field and
press F5.
or
CZ <ZIP Code>
or
Move to the Cities in a ZIP Code screen for
the ZIP Code entered as <ZIP Code>.
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.
This command is only valid from the Houses
on a Street, or Apartments at a House Range
screens.
Working With CODE-1 Plus
or
Position your cursor on
the desired line and
press F5.
229
3
Interactive Screen Reference
Table 1: Valid Entries in the Command Field (Part 4 of 6)
Command
HS <line number>
Description
Alternate Method
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.
LOCATE <string>
Generally positions the database inquiry to
the first entry that starts with <string>.
Type the desired line
number in the
Command field and
press F4.
or
Position your cursor on
the desired line and
press F4.
None.
NOTE: If there are multiple cities with the
same name, they will be listed by finance
number, highest to lowest.
MATCH
Go to the address match function. (The
match results screen that appears when you
access the database inquiry function reappears.)
Press F9.
SC <line number>
Move to the Streets in a City screen for the
city name that is displayed on line <line
number>.
Type the desired line
number in the
Command field and
press F4.
This command is only valid from the Cities in
the Database screen.
SL <line number>
Display all streets in the city locality
displayed on line <line number> on the
Streets in a City screen.
or
Position your cursor on
the desired line and
press F4.
Type the desired line
number in the
Command field and
press F4.
or
Position your cursor on
the desired line and
press F4.
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.
SZ <ZIP Code>
230
Type the desired line
number in the
Command field and
press F4.
or
Position your cursor on
the desired line and
press F4.
Move to the Streets in a ZIP Code screen for
the ZIP Code entered as <ZIP Code>
None.
Software Release 4.0.0/March 2015
The Command Field
3
Table 1: Valid Entries in the Command Field (Part 5 of 6)
Command
ZC <line number>
Description
Display all ZIP Codes for the city locality
displayed on line <line number> on the City
Information and Cities in a State screens.
Alternate Method
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.
None.
This command is only valid if you have
Geographic Coding Plus installed.
Working With CODE-1 Plus
231
3
Interactive Screen Reference
Table 1: Valid Entries in the Command Field (Part 6 of 6)
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.
Under VAX/VMS, the function keys are not available. You must enter commands in
the Command field, instead of pressing function keys.
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.
232
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
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.
Screens that Support Address Matching
The screens shown in this section of the chapter support the address matching
function. They are listed in alphabetical order.
NOTE: 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.
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.
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:
Output Case: U
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
Working With CODE-1 Plus
233
3
Interactive Screen Reference
This screen enables you to enter an input address that you want CODE-1 Plus to
match against the database. CODE-1 Plus will return the matched, standardized
address for you.
NOTE: 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:
DPV UNAVAILABLE - NO LICENSE FOUND
or
DPV UNAVAILABLE - LICENSE INVALID.
Fields
The following table presents a description of, and acceptable values for, each field on
the Address Match screen.
NOTE: Shaded fields are required.
Table 2: Fields on the Address Match Screen
Field Name
234
Description
Firm Name
The name of the firm for the record you want to match —
optional
Secondary Addr
The secondary address line for the record you want to match
— optional
Primary Addr
The primary address for the record you want to match.
City, ST
The city and state for the record you want to match. You can
enter the state name or abbreviation — optional if ZIP Code is
entered.
ZIP Code
The ZIP Code for the record you want to match — optional if
City, St is entered
USPS County Name or
Urb. Name
If the address matches to a Puerto Rican address which 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.
The matched standardized address, including apartment
number
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 2: Fields on the Address Match Screen
Field Name
Description
City, State ZIP
The matched standardized city/state/ZIP Code line
CRRT (Carrier Route)
The 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 “Z4 OUT” on page 216.
DPBC + Check
The matched delivery point barcode (DPBC) and check digit
Function Keys
The following table describes the action taken by each function key on the Address
Match screen.
Table 3: Function Keys on the Address Match Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F2
ZC
List ZIP Codes in City screen.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F4
SC
Go to the Streets in a City screen.
F5
CZ
Go to the Cities in a ZIP Code screen.
F8
DOWN
Go to the next screen of data.
F9
MAT
Go to the Return Codes screen.
F10
FLIP
Expand the database inquiry function to fill the
entire screen.
NOTE: 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.)
Working With CODE-1 Plus
235
3
Interactive Screen Reference
Delivery Sequence Footnotes Screen
The Delivery Sequence Footnotes screen shows you all of the Delivery Sequence
Footnotes (DSF2 codes) that were applicable to your match attempt. This screen is
accessed by entering DS in the Command field, or by pressing F8 from the Return
Codes screen or F7 from the Parsed Elements screen.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm name:
Firm: M D/Suf: M
Secondary Addr:
St: M
City: S
Primary Addr: 100 center st #1
Correct ZIP: Y
City, ST: chicopee ma
Output Case: U
ZIP Code: 01014
Urb Name:
Mult Secondary: Y
USPS County: HAMPDEN
Override City: C
Matched Addr: 100 CENTER ST # 1
CRRT: C770
City,State ZIP: CHICOPEE MA 01014-0819
DPBC: 081901 5
------------------------------------------------------------------------------Command: ________________________________________
Nav DPV
2 of 6
DS - Delivery Sequence Footnotes
AA :
Record matched the ZIP+4 database.
DPV Footnotes
AA :
BB :
PB :
1=Help
Record matched the ZIP+4 database.
Input address matched to DPV (all components)
Input address matched to PBSA.
3=Quit
4=MS
5=RE
6=Geo
7=Up
8=Down
9=Inq
10=Flip
Fields
The following table presents a description of, and acceptable values for, each field on
the Delivery Sequence Footnotes screen.
Table 4: Delivery Sequence Footnotes Screen (Part 1 of 2)
DSF2 Code
236
Description
AA
The record matched the ZIP+4 database (the CODE-1 Plus database).
A1
No match was found.
A2
The 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
The 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
The record matched the DSF2 file, but is missing secondary information.
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 4: Delivery Sequence Footnotes Screen (Part 2 of 2)
DSF2 Code
Description
C1
The 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
The 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.
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.
Working With CODE-1 Plus
237
3
Interactive Screen Reference
Function Keys
The following table describes the action taken by each function key on the Delivery
Sequence Footnotes screen.
Table 5: Function Keys on the Delivery Sequence Footnotes Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F4
MS
Go to the Match Settings screen.
F5
RE
Refresh (erase) all of the input and output data
from the screen.
F6
GEO
Go to the Geographic Coding Interface (you must
have purchased and installed Geographic Coding
Plus separately).
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
If the bottom of the list of DSF2 codes is displayed,
go to the next match results screen. If the bottom
of the list of DSF2 codes is not currently displayed,
page down the list of codes.
F9
INQ
Go to the database inquiry function.
F10
FLIP
Go to the database inquiry function and expand it to
fill the entire physical screen.
NOTE: 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).
238
Software Release 4.0.0/March 2015
3
Screens that Support Address Matching
Miscellaneous Information/Base Address Screen
The Miscellaneous Information/Base Address screen shows you the base address for the
street that was matched (if applicable) and additional information about the matched
address.
To access the screen, enter the DI command, or press F8 from the Statistics screen.
The following is a sample of the Miscellaneous Information/Base Address screen.
CODE-1 Plus Coding System
--------------------------------------------------------------------------Firm Name: Pitney Bowes
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: 4200 parliament pl #600
Correct ZIP: Y
City, ST: lanham md
Output Case: U
ZIP Code: 207061882 Urb Name:
Mult Secondary: Y
USPS County: Prince Georges
Override City: Z
Matched Addr: 4200 Parliament Pl Ste 600
CRRT: C059
City,State ZIP: Lanham MD 20706-1882
DPBC: 184400 8
--------------------------------------------------------------------------Command:
__ of __
DI - Misc Address Values
(6 of 6)
Base Address:
Preferred Alias: Y Abbrev Alias: Y Line of Travel Results: 0001A K0
Finance Number: 235076
Last Line Number: V23825
Standardized Firm Name: Pitney Bowes
County Name: Prince Georges
County Number: 033
Congressional District: 04
Season: YYYYYNNNNYYY
LACS:
Matching Primary Range Low:
4200 High:
4200
Parity: B
Matching Secondary Range Low:
600 High:
600
Parity: B
1=Help
3=Quit
4=MS
5=RE
6=Geo
7=Up
9=Inq
10=Flip
Fields
The following table presents a description of, and acceptable values for, each field on
the Miscellaneous Information/Base Address screen.
Table 6: Fields on Miscellaneous Information/Base Address Screen (Part 1 of 2)
Field Name
Description
Base Address
The 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
A 5-character sequence code plus 2-character alternate
sequence code
Finance Number
The USPS finance number
Last Line Number
The alphanumeric, cross-reference value between the
CODE-1 Plus City/State file and the ZIP Code file
Working With CODE-1 Plus
239
3
Interactive Screen Reference
Table 6: Fields on Miscellaneous Information/Base Address Screen (Part 2 of 2)
Field Name
Description
Standardized Firm Name
The firm name that was returned during the matching process
USPS County Name
The county where the address resides
USPS County Number
A USPS-assigned number for the county name
Congressional District
A USPS-assigned, 2-digit number representing the address’
congressional district
Season
A 12-byte code indicating when mail can be delivered to a specific
address
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
The low house range used for the matching process
Range High
The high house range used for the matching process
Parity
Even or odd numbers in range
Matching Secondary
(if it exists)
Range Low
The low unit range used for the matching process
Range High
The high unit range used for the matching process
Parity
Even or odd numbers in range
Function Keys
The following table describes the action taken by each function key on the
Miscellaneous Information/Base Address screen.
Table 7: Function Keys on the Miscellaneous Information/Base
Address Screen
Function Key
240
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 7: Function Keys on the Miscellaneous Information/Base
Address Screen
Function Key
Name
Description
F4
MS
Go to the Match Settings screen.
F5
RE
Refresh (erase) all of the input and output data
from the screen.
F6
GEO
Go to the Geographic Coding Interface (you must
have purchased and installed Geographic Coding
Plus separately).
F7
UP
Return to the previous match results screen.
F9
INQ
Go to the database inquiry function.
F10
FLIP
Go to the database inquiry function and expand it to
fill the entire physical screen.
NOTE: 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).
Working With CODE-1 Plus
241
3
Interactive Screen Reference
Expanded Return Codes
The Expanded Return Codes screen shows you textual descriptions of each of the return
codes that are displayed on the Return Codes screen. You can access this screen by
entering the ER command in the Command Field. The following is a sample of the
Expanded Return Codes screen.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm Name: LOCUS INC
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: 2560 HUNTington ave #302
Correct ZIP: Y
City, ST: alexandria va
Output Case: U
ZIP Code: 22303
Urb Name:
Mult Secondary: Y
USPS County: Fairfax
Override City: Z
Matched Addr: 2560 Huntington Ave Ste 302
CRRT: C009
City,State ZIP: Alexandria VA 22303-1493
DPBC: 149360 7
------------------------------------------------------------------------------Command:
Nav Off
1 of 1
ER - Expanded Return Codes
General RC:
Record Type:
Unit RC:
Firm RC:
Source of Adr:
ZIP Status:
Source of ZIP:
The address match was successful.
Firm
The input unit doesn’t match the units for house range.
There were no firms on the database for this address.
The output address was taken from the primary line.
The input ZIP was confirmed by an address match.
The original ZIP Code was retained.
1=Help
3=Quit
4=MS
5=RE
6=Geo
9=Inq
10=Flip
Fields
There are no fields to fill in the Expanded Return Codes screen.
Function Keys
The following table describes the action taken by each function key on the Expanded
Return Codes screen.
Table 8: Function Keys on the Expanded Return Codes Screen
Function Key
242
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F4
MS
Go to the Match Settings screen.
F5
RE
Refresh (erase) all of the input and output data from the
screen.
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 8: Function Keys on the Expanded Return Codes Screen
Function Key
Name
Description
F6
GEO
Go to the Geographic Coding Interface (you must have
purchased and installed Geographic Coding Plus
separately).
F9
INQ
Go to the database inquiry function.
F10
FLIP
Go to the database inquiry function and expand it to fill
the entire physical screen.
Working With CODE-1 Plus
243
3
Interactive Screen Reference
Geographic Coding Information
The Geographic Coding Information screen shows you the geographic coding data for
your matched address.
You can access this screen by entering the GC command in the Command Field. The
following is a sample of the Geographic Coding Information screen.
Settings Fields
1=Help
3=Quit
4=MS
5=RE
6=Geo
9=Inq
Information Only
MSA: 8840 WASHINGTON DC-MD-VA-WV
Setting Fields
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm Name: LOCUS INC
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: 2560 HUNTington ave #302
Correct ZIP: Y
City, ST: alexandria va
Output Case: U
ZIP Code: 22303
Urb Name:
Mult Secondary: Y
USPS County: Fairfax
Override City: Z
Matched Addr: 2560 Huntington Ave Ste 302
CRRT: C009
City,State ZIP: Alexandria VA 22303-1493
DPBC: 149360 7
------------------------------------------------------------------------------Command:
Nav Off
1 of 1
GC - Geographic Coding Information
Match Level: 9
Lat/Long Level: 4
State: 51
Latitude: 038.7968 N
County: 059 FAIRFAX
Longitude: 077.0765 W
Census Tract: 420400
Census Block Grp: 1
10=Flip
Fields
The following table presents a description of, and acceptable values for, each field on
the Geographic Coding Information screen.
Table 9: Fields on the Geographic Coding Information Screen
Field Name
Match Level
Description
The level of match obtained against the Geographic Coding
Master File. One of the following codes appears:
• 9 — Both the ZIP Code and ZIP +4 Code matched the
Master File
• 5 — The input ZIP Code matched, but the ZIP+4 Code did
not
• X — The Geographic Coding Master File data has
expired.
244
State
The FIPS state code of the matched address.
County
The FIPS county number and name of the matched address.
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 9: Fields on the Geographic Coding Information Screen
Field Name
Description
MSA
The Metropolitan Statistical Area that encompasses this
address.
Census Tract
The 6-digit number representing the census tract division
within the county.
Census Block Group
The single-digit numeric code indicating the block group
division of the census tract.
Lat/Long Level
The level of latitude and longitude determined for the
matched address. One of the following codes will be
displayed.
• 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
The latitude of the standardized address.
Longitude
The longitude of the standardized address.
Function Keys
The following table describes the action taken by each function key on the Geographic
Coding Information screen.
Table 10: Function Keys on the Geographic Coding Information Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F4
MS
Go to the Match Settings screen.
F5
RE
Refresh (erase) all of the input and output data
from the screen.
F6
GEO
Go to the Geographic Coding Interface (you must
have purchased and installed Geographic Coding
Plus separately).
F9
INQ
Go to the database inquiry function.
F10
FLIP
Go to the database inquiry function, and expand it
to fill the entire physical screen.
Working With CODE-1 Plus
245
3
Interactive Screen Reference
Match Settings Screen
The Match Settings screen enables you to tailor your processing requirements. You
can also specify whether or not 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.
You can access this screen by entering MS in the Command field, or by pressing the
function key F4 from any match results screen.
Note that the fields you can modify are actually on the top half of the physical screen,
along with the address matching fields. When the Match Settings screen is displayed,
the only fields in which you can enter data are the settings fields on the upper right
portion of the screen. To save your new settings and return to the previous screen,
just press ENTER. Once you have changed the settings, they stay changed for
subsequent matches until you change them again or exit. The following is a sample of
the Match Settings screen.
1=Help
-
Firm, Dir/Suf, St(reet) - T=Tight, M=Medium, L=Loose, E=Equal
X = Accept vanity city names, S = Do not accept
Y = Correct input ZIP Code if necessary, N = Do not correct
U = Uppercase, L= Lowercase, C = Mixed case
Y = Attempt to find ZIP+4 Match, N = Match to the default
Z = Return preferred ZIP+4 lastline, C = Return default USPS
3=Quit
Information Only
Algorithms
V(anity)city
Correct ZIP
Output Case
Mult 2ry Cmp
Override City
Settings Only
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:
Output Case: U
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
------------------------------------------------------------------------------Command:
Nav DPV
1 of 1
Specify Match Settings
10=Exit
NOTE: Although this screen enables 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.
246
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Fields
The following table presents a description of, and acceptable values for, each field on
the Match Settings screen.
Table 11: Fields on the Match Settings Screen
Field Name
Algorithms
Description
A 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
A 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).
Correct ZIP
A one-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
A 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
A 1-character code indicating whether to attempt multiple
secondary component processing:
• Y — Attempt secondary match.
• N — Assign default ZIP+4 Code.
Override City
A 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)
• Z — Store the ZIP+4 File Preferred Last Line City Name
(override city name).
Working With CODE-1 Plus
247
3
Interactive Screen Reference
Function Keys
The following table describes the action taken by each function key on the Match
Settings screen.
Table 12: Function Keys on the Match Settings Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F10
CANCEL
Return to the previous screen without modifying
the match settings.
NOTE: 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.)
248
Software Release 4.0.0/March 2015
3
Screens that Support Address Matching
Multiple Elements Screen
The Multiple Elements screen shows you whether multiple match elements were found
during the match attempt. This screen can be accessed by entering the ME command,
or by pressing F8 from the Parsed Elements screen or F7 from the Statistics screen. The
following sample is a of the Multiple Elements screen.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm Name: LOCUS INC
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: 2560 HUNTington ave #302
Correct ZIP: Y
City, ST: alexandria va
Output Case: U
ZIP Code: 22303
Urb Name:
Mult Secondary: Y
USPS County: Fairfax
Override City: Z
Matched Addr: 2560 Huntington Ave Ste 302
CRRT: C009
City,State ZIP: Alexandria VA 22303-1493
DPBC: 149360 7
------------------------------------------------------------------------------Command:
Nav Off
4 of 6
--ME - Multiple Elements
Was the city standardized?:
Was the state standardized?:
Was apartment detected in input?: Y
Was 'default record' matched?:
Were multiple input elements found?
Leading dir:
Street name:
LACSLINK ACTIVATED
1=Help
3=Quit
4=MS
5=RE
ASM/ESM Flag: A
SuiteLink RC:
SuiteLink MC:
SuiteLink FID:
Suffix:
6=Geo
7=Up
LACSLink RC: A
LACSLink Ind: Y
Trailing dir:
8=Down
9=Inq
10=Flip
Fields
The following table presents a description of, and acceptable values for, each field on
the Multiple Elements screen.
Table 13: Fields on the Multiple Elements Screen (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.
Working With CODE-1 Plus
249
3
Interactive Screen Reference
Table 13: Fields on the Multiple Elements Screen (Part 2 of 2)
Field Name
Was apartment detected
in input?
Description
A 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.
Was “default record”
matched?
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.
250
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Function Keys
The following table describes the action taken by each function key on the Multiple
Elements screen.
Table 14: Function Keys on the Multiple Elements Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F4
MS
Go to the Match Settings screen.
F5
RE
Refresh (erase) all of the input and output data
from the screen.
F6
GEO
Go to the Geographic Coding Interface (you must
have purchased and installed Geographic Coding
Plus separately).
F7
UP
Return to the previous match results screen.
F8
DOWN
Go to the next match results screen.
F9
INQ
Go to the database inquiry function.
F10
FLIP
Go to the database inquiry function and expand it to
fill the entire physical screen.
NOTE: 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.)
Working With CODE-1 Plus
251
3
Interactive Screen Reference
Parsed Elements Screen
The Parsed Elements screen shows you the individual elements that make up the
standardized address. If no address match was found, the fields on this screen are
blank. This screen is accessed by entering the PE command, or by pressing F8 from
the Delivery Sequence Footnotes screen or F7 from the Multiple Elements screen. The
following sample of the Parsed Elements screen.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm Name: LOCUS INC
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: 2560 HUNTington ave #302
Correct ZIP: Y
City, ST: alexandria va
Output Case: U
ZIP Code: 22303
Urb Name:
Mult Secondary: Y
USPS County: Fairfax
Override City: Z
Matched Addr: 2560 Huntington Ave Ste 302
CRRT: C009
City,State ZIP: Alexandria VA 22303-1493
DPBC: 149360 7
------------------------------------------------------------------------------Command:
Nav Off
3 of 6
PE - Parsed Elements
House: 2560
Street: Huntington
Lead Dir:
Suffix: Ave
RR/HC #:
PO Box:
Short City: Alexandria
ZIP Code: 22303 1493
1=Help
Trail Dir:
RR/HC Box:
Apt Info: Ste 302
Private Mail Box:
3=Quit
4=MS
5=RE
6=Geo
7=Up
8=Down
9=Inq
10=Flip
Fields
The following table presents a description of, and acceptable values for, each field on
the Parsed Elements screen.
Table 15: Fields on the Parsed Elements Screen (Part 1 of 2)
Field Name
252
Description
Lead Dir
The returned leading directional
House
The returned house number
Street
The returned street name
Suffix
The returned suffix
Trail Dir
The returned trailing directional
RR/HC #
The returned rural route or highway contract route number
RR/HC Box
The returned rural route or highway contract box number
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 15: Fields on the Parsed Elements Screen (Part 2 of 2)
Field Name
Description
PO Box
The returned post office box number
Apt. Information
The returned apartment designator (i.e., STE, APT) and
number
Short City
The returned short city name
ZIP Code
The returned 9-digit ZIP Code.
Private Mail Box
The returned Private Mailbox information.
Function Keys
The following table describes the action taken by each function key on the Parsed
Elements screen.
Table 16: Function Keys on the Parsed Elements Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F4
MS
Go to the Match Settings screen.
F5
RE
Refresh (erase) all of the input and output data from the
screen.
F6
GEO
Go to the Geographic Coding Interface (you must have
purchased and installed Geographic Coding Plus
separately).
F7
UP
Return to the previous match results screen.
F8
DOWN
Go to the next match results screen.
F9
INQ
Go to the database inquiry function.
F10
FLIP
Go to the database inquiry function and expand it to fill
the entire physical screen.
NOTE: 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.)
Working With CODE-1 Plus
253
3
Interactive Screen Reference
Return Codes Screen
The Return Codes screen shows you the return codes that correspond to your match
attempt. This screen is accessed by entering the RC command in the Command field,
or pressing the F7 function key from the Delivery Sequence Footnotes screen. The
following is a sample of the Return Codes screen.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm name:
Firm: M D/Suf: M
Secondary Addr:
St: M
City: S
Primary Addr: 1401 Peartree Ln
Correct ZIP: Y
City, ST:
Output Case: U
ZIP Code: 20721
Urb Name:
Mult Secondary: Y
USPS County: PRINCE GEORGES
Override City: C
Matched Addr: 1401 PEARTREE LN
CRRT: R002
City,State ZIP: BOWIE MD 20721-3004
DPBC: 300401 0
------------------------------------------------------------------------------Command: ________________________________________
Nav DPV
1 of 6
RC - Return Codes
General RC:
City RC: B
Firm RC:
Address Prob: 0
Overall Prob: 0
USPS Rec. Type: S
City Type:
Dir. RC:
Suffix RC:
Unit RC:
Firm Score:
Street Score: 0
Source of Addr: P
Alias RC:
ZIP Status: C
Source of ZIP: Z
POB ZIP Code: N
'best fit' ZIPs: 1
PBSA Ind:
Alt Addr Scheme:
Alias Type:
Line of Travel RC: 9
DPV Flag: Y
NoStat: N
Vacant: N CMRA: N
RDI Flag:
First four additional ZIPs:
Drop Info Type:
Data:
1=Help
3=Quit
4=MS
5=RE
6=Geo
8=Down
9=Inq
10=Flip
NOTE: If you hit a “seed record” during DPV processing, a note similar to the
following will appear on the bottom of this screen:
DPV KEY IS: S06430475462316207
In order for you to continue DPV processing, you will have to return to the Pitney
Bowes website and provide the code to get a new permanent key. See Chapter 6
for more information on DPV processing, “seed records,” and license keys. You will
also be required to extract and build a DPV Seed file and supply it on the Pitney
Bowes website in order to get a new permanent key.
254
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Fields
The following table presents a description of, and acceptable values for, each field on
the Return Codes screen.
Table 17: Fields on Return Codes Screen (Part 1 of 6)
Field Name
General RC
Description
A 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
A 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
A 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
A 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.
Working With CODE-1 Plus
255
3
Interactive Screen Reference
Table 17: Fields on Return Codes Screen (Part 2 of 6)
Field Name
Overall Prob
Description
A 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.
USPS Rec. Type
The 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
This is a 1-character code describing the input city type:
• P — Primary city
• S — Secondary city
• V — Vanity city.
Dir. RC
A 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
A 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.
256
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 17: Fields on Return Codes Screen (Part 3 of 6)
Field Name
Unit RC
Description
A 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
A 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
A 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.
Source of Addr.
A 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
A 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.
Working With CODE-1 Plus
257
3
Interactive Screen Reference
Table 17: Fields on Return Codes Screen (Part 4 of 6)
Field Name
ZIP Status
Description
A 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
A 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
A one-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
The number of “best fit” ZIP Codes that were found during the
match attempt.
PBSA Ind
A one-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.
258
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 17: Fields on Return Codes Screen (Part 5 of 6)
Field Name
Alt. Adr. Scheme
Description
A 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
A 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
A 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
A 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
A 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.
Working With CODE-1 Plus
259
3
Interactive Screen Reference
Table 17: Fields on Return Codes Screen (Part 6 of 6)
Field Name
Vacant Table Flag
Description
A 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.
CMRA Flag
This is a 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
This is a 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
A 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.
NOTE: The Dropped Info. 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 Info. Type that is
not blank, but a blank Data field.
260
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Function Keys
The following table describes the action taken by each function key on the Return
Codes screen.
Table 18: Fields on the Return Codes Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Return to the Main Menu.
F4
MS
Go to the Match Settings screen.
F5
RE
Refresh (erase) all of the input and output data
from the screen.
F6
GEO
Go to the Geographic Coding Interface (you must
have purchased and installed Geographic Coding
Plus separately).
F8
DOWN
Go to the next match results screen.
F9
INQ
Go to the database inquiry function.
F10
FLIP
Go to the database inquiry function and expand it to
fill the entire physical screen.
NOTE: 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.)
Working With CODE-1 Plus
261
3
Interactive Screen Reference
Statistics Screen
The Statistics screen shows execution statistics about the number of calls that were
made to the matcher while this address was being processed. This screen is
particularly useful if you are encountering some kind of problem with Interactive
CODE-1 Plus. If that is the case, these statistics can aid the Pitney Bowes Customer
Support Representatives in solving your problem.
This screen is accessed by entering the ST command, or by pressing F8 from the
Multiple Elements screen or F7 from the Dropped Information/Base Address screen. On
the following page is a sample of the Statistics screen.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm Name: LOCUS INC
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: 2560 HUNTington ave #302
Correct ZIP: Y
City, ST: alexandria va
Output Case: U
ZIP Code: 22303
Urb Name:
Mult Secondary: Y
USPS County: Fairfax
Override City: Z
Matched Addr: 2560 Huntington Ave Ste 302
CRRT: C009
City,State ZIP: Alexandria VA 22303-1493
DPBC: 149360 7
------------------------------------------------------------------------------Command:
Nav Off
5 of 6
ST - Statistics
City-based locality match results:
Finance number-based locality match results:
Original ZIP-Based match results:
Number of match attempts:
Master File Reads
ZIP Index
City Details
2
3
1=Help
262
3=Quit
4=MS
1
Locality
2
5=RE
6=Geo
Std.Address
ZIP
ZIP+4
CR-RT
RC:
RC:
RC:
RC:
Street Details
1
7=Up
8=Down
9=Inq
County
1
10=Flip
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Fields
The following table presents a description of, and acceptable values for, each field on
the Statistics screen.
Table 19: Fields on the Statistics Screen (Part 1 of 3)
Field Name
City-based locality match
results
Description
A 1-character code indicating the results of the match
attempt in the city-based locality:
• Blank — Not attempted
• I — Attempted, improved (a match was found).
• N — Attempted, no match found
Finance number-based
locality match results
A 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
A 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
A 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.
Working With CODE-1 Plus
263
3
Interactive Screen Reference
Table 19: Fields on the Statistics Screen (Part 2 of 3)
Field Name
ZIP RC
Description
A 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.
ZIP+4 RC
A 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
A 1-character return code indicating the success or reason
for failure of the Carrier Route coding attempt (i.e., was an
output carrier route 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.
264
ZIP Index
The number of database reads done on the ZIP Index file in
order to obtain the match.
City Details
The number of database reads performed on the City Details
file in order to obtain the match.
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 19: Fields on the Statistics Screen (Part 3 of 3)
Field Name
Description
Locality
The number of database reads performed on the Locality file
in order to obtain the match.
Street Details
The number of database reads performed on the Street
Details file in order to obtain the match.
County
The number of database reads performed on the County file
in order to obtain the match.
Function Keys
The following table describes the action taken by each function key on the Statistics
screen.
Table 20: Function Keys on the Statistics Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F4
MS
Go to the Match Settings screen.
F5
RE
Refresh (erase) all of the input and output data
from the screen.
F6
GEO
Go to the Geographic Coding Interface (you must
have purchased and installed Geographic Coding
Plus separately).
F7
UP
Return to the previous match results screen.
F8
DOWN
Go to the next match results screen.
F9
INQ
Go to the database inquiry function.
F10
FLIP
Go to the database inquiry function and expand it to
fill the entire physical screen.
NOTE: 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.)
Working With CODE-1 Plus
265
3
Interactive Screen Reference
Address Stack Screen
The Address Stack screen shows 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).
The following is a sample of the information available on the Address Stack screens.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm Name: Pitney Bowes
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: calle 1 a-15
Correct ZIP: Y
City, ST: bayamon pr
Output Case: U
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
------------------------------------------------------------------------------Command:
Nav On
1 of 2
AS - Address Stack
Address---- City---- St ZIP---ZIP4 DPC C-Rt RTP Cnty/CD Primary---- LL#--A15 CALLE 1 SAN JUAN PR 00921-4848 158 C043 S 1 127
A10 - A24 B V18250
A15 CALLE 1 SAN JUAN PR 00921-4504 159 C043 S 1 127
A12 - A22 B V19361
A15 CALLE 1 SAN JUAN PR 00924-5306 155 C058 S 1 127
A1 - A43 B V18276
A15 CALLE 1 SAN JUAN PR 00924-5314 156 C058 S 1 127
A1 - A15 B V18278
A15 CALLE 1 SAN JUAN PR 00926-5239 158 C084 S 1 127
A3 - A24 B V18355
A15 CALLE 1 SAN JUAN PR 00926-5950 158 C085 S 1 127
A1 - A24 B V18384
A15 CALLE 1 SAN JUAN PR 00956-2323 154 C014 S 1 021
A1 - A16 B V18476
A15 CALLE 1 SAN JUAN PR 00956-4416 159 C009 S 1 021
A15 - A19 B V19089
1=Help
266
3=Quit
4=MS
5=RE
6=Geo
8=Down
9=Inq
10=Flip
Software Release 4.0.0/March 2015
3
Screens that Support Address Matching
The picture below shows additional Address Stack screen information.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm Name: Pitney Bowes
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: calle 1 a-15
Correct ZIP: Y
City, ST: bayamon pr
Output Case: U
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
------------------------------------------------------------------------------Command:
Nav On
1 of 2
AS - Address Stack
Fin-Nr Urbanization------- Firm-----------428460 PARQ DE SAN IGNACIO Pitney Bowes
428460 PARQ DE SAN IGNACIO Pitney Bowes
428460 PARQ DE SAN IGNACIO Pitney Bowes
428460 PARQ DE SAN IGNACIO Pitney Bowes
428460 PARQ DE SAN IGNACIO Pitney Bowes
428460 PARQ DE SAN IGNACIO Pitney Bowes
428460 PARQ DE SAN IGNACIO Pitney Bowes
428460 PARQ DE SAN IGNACIO Pitney Bowes
1=Help
3=Quit
4=MS
5=RE
6=Geo
8=Down
9=Inq
10=Flip
Fields
The following table presents a description of, and acceptable values for, each field on
the Address Stack screens.
Table 21: Fields on the Address Stack Screen (Part 1 of 2)
Field Name
Working With CODE-1 Plus
Description
Address
Street name along with directorionals, 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)
267
3
Interactive Screen Reference
Table 21: Fields on the Address Stack Screen (Part 2 of 2)
Field Name
Description
RTP
A 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
Function Keys
The following table describes the action taken by each function key on the Address
Stack screen
Table 22: Function Keys on the Address Stack Screen(Part 1 of 2)
Function Key
268
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F4
MS
Go to the Match Settings screen.
Software Release 4.0.0/March 2015
Screens that Support Address Matching
3
Table 22: Function Keys on the Address Stack Screen(Part 2 of 2)
Function Key
Name
Description
F5
RE
Refresh (erase) all of the input and output data from the
screen.
F6
GEO
Go to the Geographic Coding Interface (you must have
purchased and installed Geographic Coding Plus
separately).
F7
UP
If the second of the Address Stack screens is displayed,
return to the previous screen. If the first of the Address
Stack screens is currently displayed, this area will be
blank.
F8
DOWN
If the first of the Address Stack screens is displayed, go
to the next screen. If the second of the Address Stack
screens is currently displayed, this area will be blank.
F9
INQ
Go to the database inquiry function.
F10
FLIP
Go to the database inquiry function and expand it to fill
the entire physical screen.
NOTE: 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).
NOTE: 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.
Working With CODE-1 Plus
269
3
Interactive Screen Reference
Screens that Support Database Inquiry
The screens shown in this section all support the database inquiry function. They are
listed in alphabetical order.
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.
This screen is accessed by entering the AH <line number> command (or pressing F4)
from the Houses on a Street screen. The following is a sample of the Apartments at a
House Range screen.
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:
Output Case: U
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
------------------------------------------------------------------------------Command:
Nav Off
__ of __
Apts in 350 5TH AVE, ZIP Code 10118
LN
Apt Range
ZIP
Z+4 Range Rte
Record Type
Apt Type Firms
1
Default
10118 0110
C020 H Highrise
2
10118 0199
C020 H Highrise
LOWR
3
1
10118 0199
C020 H Highrise
FRNT
4
1
10118 0199
C020 H Highrise
LBBY
5
1
10118 0109
C020 H Highrise
LOWR
2
6
2-14
10118 0199
C020 H Highrise
LBBY
7
3
10118 0167
C020 F Firm
LBBY
1
8
4
10118 0111
C020 F Firm
LBBY
1
1=Help
2=Alias
3=Quit
5=FM
6=Back
8=Down
9=Mat
10=Flip
NOTE: To view more lines of data at once, enter the FLIP command in the
Command field, or press F10.
270
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
Fields
The following table presents a description of, and acceptable values for, each field on
the Apartments at a House Range screen.
Table 23: Fields on the Apartments at a House Range Screen
Field Name
Description
LN
The line number assigned to this apartment range.
Apt Range
The apartment number range.
ZIP
The ZIP Code for the apartments in this range.
Z+4 Range
The range of ZIP+4 Codes that are valid for this apartment
range.
Rte
The carrier or rural route number for the apartments in this
range.
Record Type
The USPS record type for the ZIP+4 records in this apartment
range.
Apt Type
The unit designator for the apartments in this range (i.e., APT,
STE).
Firms
The number of firms in this apartment range.
Function Keys
The following table describes the action taken by each function key on the
Apartments at a House Range screen.
Table 24: Function Keys on the Apartments at a House Range Screen (Part 1 of 2)
Function Key
Name
Description
F1
HELP
Obtain online help.
F2
ALIAS
Show the base street name for the house range shown.
F3
QUIT
Return to the Main Menu.
F5
FM
Go to the Firms on a Street screen.
F6
BACK
Return to the previous screen.
F7
UP
Scroll the list so that the previous 8 house ranges are
displayed.
F8
DOWN
Scroll the list so that the next 8 house ranges are
displayed.
Working With CODE-1 Plus
271
3
Interactive Screen Reference
Table 24: Function Keys on the Apartments at a House Range Screen (Part 2 of 2)
Function Key
Name
Description
F9
MAT
Go to the address matching function.
F10
FLIP
Change the screen so that the data fills the entire physical
screen.
NOTE: 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.)
272
Software Release 4.0.0/March 2015
3
Screens that Support Database Inquiry
Cities in a State Screen
The City Information screen shows you an alphabetical listing of all of the city names
in a particular state. For each city, this screen also displays the state abbreviation and
the ZIP Code (or range of ZIP Codes) that is valid for the city.
This screen is displayed when you enter the CS <state abbr.> command. You can enter
this command from any screen in the system. The following is a sample of the Cities in
a State screen.
NOTE: 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
.
CODE-1 Plus Coding System
-------------------------------------------------------------------------Firm Name:
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: 4200 PARLIAMENT ST
Correct ZIP: Y
City, ST: LANHAM MD
Output Case: U
ZIP Code: 20706
Mult Secondary: Y
USPS County: PRINCE GEORGES
Override City: Z
Matched Addr: 4200 PARLIAMENT PL
CRRT: C005
City,State ZIP: LANHAM MD 20706-1882
DPBC: 185200 9
-------------------------------------------------------------------------Command:
__ of __
Cities in Maryland
LN City
State
ZIP Range
Type Urb Unique-ZIP
1 ABELL
MD
20606
P
2 ABER PROV GRD
MD
21005-21010
p
3 ABERDEEN
MD
21001
P
4 ABERDEEN PROVING GROUND
MD
210014-21010
P
5 ABINGDON
MD
21009
P
6 ACCIDENT
MD
21520
P
7 ACCOKEEK
MD
20607
P
8 ADAMSTOWN
MD
21710
P
1=Help
2=ZC
3=Quit
4=SC
5=CZ
6=Back
8=Down
9=Mat
10=Flip
NOTE: To view more lines of data at once, enter the FLIP command in the
Command field, or press F10.
Working With CODE-1 Plus
273
3
Interactive Screen Reference
Fields
The following table presents a description of, and acceptable values for, each field on
the Cities in a State screen.
Table 25: Fields on the Cities in a State Screen
Field Name
Description
LN
The line number of the city.
City
The city name.
State
The abbreviations for the state in which the city is located.
ZIP Range
The 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
A 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.
Function Keys
The following table describes the action taken by each function key on the Cities in a
State screen.
Table 26: Function Keys on the Cities in a State Screen (Part 1 of 2)
Function Key
274
Name
Description
F1
HELP
Obtain online help.
F2
ZC
Go to the ZIP Codes in a City screen.
F3
QUIT
Return to the Main Menu.
F4
SC
Go to the Streets in a City screen.
F5
CZ
Go to the other Cities in a ZIP Code screen.
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
Table 26: Function Keys on the Cities in a State Screen (Part 2 of 2)
Function Key
Name
Description
F6
BACK
Return to the previous screen.
F7
UP
Scroll the list so that the previous 8 cities are
displayed.
F8
DOWN
Scroll the list so that the next 8 cities are
displayed.
F9
MAT
Go to the address matching function.
F10
FLIP
Change the screen so that the data fills the entire
physical screen.
NOTE: 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.)
Working With CODE-1 Plus
275
3
Interactive Screen Reference
Cities in a ZIP Code Screen
The Cities in a ZIP Code screen shows you all of the cities in a given ZIP Code. For each
city, CODE-1 Plus displays the long city names, short city names, and city type.
This screen is accessed by entering the CZ <line number> or the CZ <ZIP Code>
command, or by pressing F5 from the Cities in the Database screen or Cities in a State
screen. The following is a sample of the Cities in a ZIP Code screen.
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:
Output Case: U
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
------------------------------------------------------------------------------Command:
Nav Off
__ of __
Cities in ZIP Code 00730
LN
Long City Name
State
Short City Name
City Type
1
ALT DEL MADRIGAL
PR
Vanity
2
ALTS DE JACARANDA
PR
Vanity
3
BDA BORINQUEN
PR
Vanity
4
BDA CLAUSELLS
PR
Vanity
5
BDA FERRAN
PR
Vanity
6
BDA TAMARINDO
PR
Vanity
7
BO LA PONDEROSA
PR
Vanity
8
BO MAGUEYES
PR
Vanity
1=Help
3=Quit
4=SZ
6=Back
8=Down
9=Mat
10=Flip
NOTE: To view more lines of data at once, enter the FLIP command in the
Command field, or press F10.
The USPS enables 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 has three city names associated with it: Abbeville, Cow
Island, and Meaux. Since Abbeville is preferred, it has a city type of primary; all other
city names have a city type of secondary.
276
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
Fields
A description of each field on the Cities in a ZIP Code screen follows.
Table 27: Fields on the Cities in a ZIP Code Screen
Field Name
Description
LN
The line number for this city name.
Long City Name
The full name for the city.
State
The 2-character state abbreviation for the city.
Short City Name
The USPS shortened city name.
City Type
The USPS designated city type. One of the following city types
appears: Primary, Secondary, Vanity.
Function Keys
The action performed by each function key on the Cities in a ZIP Code screen follows.
Table 28: Fields on the Cities in a ZIP Code Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Return to the Main Menu.
F4
SZ
Go to the Streets in a ZIP Code screen.
F6
BACK
Return to the previous screen.
F7
UP
Scroll the list so that the previous 8 cities are
displayed.
F8
DOWN
Scroll the list so that the next 8 cities are
displayed.
F9
MAT
Go to the address matching function.
F10
FLIP
Change the screen so that the data fills the entire
physical screen.
NOTE: 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.)
Working With CODE-1 Plus
277
3
Interactive Screen Reference
City Information Screen
The City Information screen shows you an alphabetical listing of all of the 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 that applies to the city.
The screen on the following page is displayed when you first access the Interactive
CODE-1 Plus 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.
NOTE: 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.
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:
Output Case: U
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
To view more lines of data, enter the FLIP command in the Command field, or press
F10.
278
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
Fields
The following table presents a description of, and acceptable values for, each field on
the City Information screen.
Table 29: Fields on the City Information Screen
Field Name
Description
LN
The line number of the city
City
The city name
State
The abbreviations for the state in which the city is located
ZIP Range
The 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
A 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.
Function Keys
The following table describes the action taken by each function key on the City
Information screen.
Table 30: Function Keys on the City Information Screen (Part 1 of 2)
Function Key
Name
Description
F1
HELP
Obtain online help.
F2
ZC
Go to the ZIP Codes in a City screen.
F3
QUIT
Return to the Main Menu.
F4
SC
Go to the Streets in a City screen.
F5
CZ
Go to the other Cities in a ZIP Code screen.
Working With CODE-1 Plus
279
3
Interactive Screen Reference
Table 30: Function Keys on the City Information Screen (Part 2 of 2)
Function Key
Name
Description
F8
DOWN
Scroll the list so that the next 8 cities are
displayed.
F9
MAT
Go to the address matching function.
F10
FLIP
Change the screen so that the data fills the entire
physical screen.
NOTE: 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.)
280
Software Release 4.0.0/March 2015
3
Screens that Support Database Inquiry
Firms in a House Range Screen
The Firms in a House Range screen shows you all of the 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.
This screen is accessed by entering 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. The following is a sample of the Firms in a House Range screen.
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:
Output Case: U
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
------------------------------------------------------------------------------Command:
Nav Off
__ of __
Firms in 350 5TH AVE, NEW YORK, NY
LN
House Range
Apt Range
Firm Name
ZIP Code
C-Rt
1
350
1
NY COFFEE STATION
10118-0119 C020
2
350
1
SHOW BRAN PHOTO
10118-0145 C020
3
350
3
BIG APPLE RESTAURANT
10118-0167 C020
4
350
4
DAIKICHI SUSHI
10118-0111 C020
5
350
5
AU BON PAIN
10118-0112 C020
6
350
6
FINESSE CASSINI JEWLERY
10118-0149 C020
7
350
7
FEDERAL EXPRESS
10118-0129 C020
8
350
8
DUANE READE
10118-0138 C020
1=Help
2=Alias
3=Quit
6=Back
8=Down
9=Mat
10=Flip
NOTE: To view more lines of data at a time, in the Command field type FLIP
command and press ENTER, or press F10.
Fields
A description of each field on the Firms on a House Range screen follows.
Table 31: Fields on a Firms on a House Range Screen (Part 1 of 2)
Field Name
Description
LN
The line number for this firm.
House Range
The house number ranges that are valid for this firm.
Working With CODE-1 Plus
281
3
Interactive Screen Reference
Table 31: Fields on a Firms on a House Range Screen (Part 2 of 2)
Field Name
Description
Apt Range
The apartment number ranges that are valid for this firm.
Firm Name
The firm name.
ZIP Code
The 9-digit ZIP Code assigned to this firm.
C-Rt
The carrier route number for this firm.
Function Keys
The action performed by each function key on the Firms on a House Range screen
follows.
Table 32: Function Keys on the Firms on a House Range Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F2
ALIAS
Show the base street name for the line on which
the cursor is currently placed.
F3
QUIT
Return to the Main Menu.
F6
BACK
Return to the City Information screen.
F7
UP
Scroll the list so that the previous 8 firms are
displayed.
F8
DOWN
Scroll the list so that the next 8 firms are
displayed.
F9
MAT
Go to the address matching function.
F10
FLIP
Change the screen so that the data fills the entire
physical screen.
NOTE: 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.)
282
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
Houses on a Street Screen
The Houses on a Street screen shows you a listing of all of the house number ranges on
a particular street. In addition to even/odd house number ranges, CODE-1 Plus
shows you ZIP and ZIP+4 Code ranges, carrier routes, and firm/alias name.
This screen is accessed by entering the command HS <line number> (or pressing
F4) from the Streets in a City or Streets in a ZIP Code screens. The following is a sample
of the Houses on a Street screen.
NOTE: 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.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Firm Name:
Firm: M D/Suf: M
Secondary Addr:
St: M Vcity: S
Primary Addr: 163 conover rd
Correct ZIP: Y
City, ST: trenton nj
Output Case: U
ZIP Code: 08691
Urb Name:
Mult Secondary: Y
GEO County: MERCER
Override City: Z
Matched Addr: 163 CONOVER RD
CRRT: R003
City,State ZIP: PRINCETON JUNCTION NJ 08550-3233
DPBC: 323363 2
------------------------------------------------------------------------------Command:
Nav Off
__ of __
Houses on CONOVER RD, ZIP Code 08691
LN
House Range
E/O ZIP Z+4 Range Rte Typ
Firm/Alias Name
1 Z
1-99
O 08691 3228
R004 S
2 Z
2-98
E 08691 3229
R004 S
3 Z
100-120
E 08691 3230
R004 S
4 Z
101-161
O 08691 3231
R004 S
5 Z
122-170
E 08691 3232
R004 S
6 Z
163-199
O 08691 3233
R004 S
7 Z
172-198
E 08691 3234
R004 S
8 Z
200-298
E 08691 3235
R004 S
1=Help
3=Quit
4=AH
5=FM
6=Back
8=Down
9=Mat
10=Flip
NOTE: To view more lines of data, in the Command field, type FLIP and press
ENTER, or press F10.
Working With CODE-1 Plus
283
3
Interactive Screen Reference
NOTE: 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.
Fields
The following table presents a description of, and acceptable values for, each field on
the Houses on a Street screen.
Table 33: Fields on the Houses on a Street Screen
Field Name
284
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 evennumbered 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.
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.
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
Function Keys
The following table describes the action taken by each function key on the Houses on
a Street screen.
Table 34: Function Keys on the Houses on a Street Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Return to the Main Menu.
F4
AH
Go to the Apartments on a Street screen.
F5
FM
Go to the Firms on a Street screen.
F6
BACK
Return to the City Information screen.
F7
UP
Scroll the list so that the previous eight house
ranges are displayed.
F8
DOWN
Scroll the list so that the next eight house ranges
are displayed.
F9
MAT
Go to the address matching function.
F10
FLIP
Change the screen so that the data fills the entire
physical screen.
NOTE: 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.)
Working With CODE-1 Plus
285
3
Interactive Screen Reference
Streets in a City or Streets in a ZIP Code Screen
The Streets in a City or Streets in a ZIP Code screen shows an alphabetical listing of all
of the 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 STand BLVD.
This screen is accessed by entering the SC or SL command (or pressing F4) from the
Cities in the Database screen, or Cities in a State screen, or pressing F4 from the Cities
in a ZIP Code screen. You can enter the SZ command from any database inquiry
screen. On the following page is a sample of the Streets in a City screen.
NOTE: 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.
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:
Output Case: U
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
------------------------------------------------------------------------------Command:
Nav Off
__ of __
Streets in NEW YORK, NY
LN
Dir StreetName
Sfx
Dir
ZIP Codes
1
ABINGDON
SQ
10014
2
ABP FULTON J SHEEN
PL
10017
3
ACADEMY
ST
10034
4
ADAM CLAYTON POWELL JR
BLVD
10026-10039
5
ALBANY
ST
10006-10280
6
ALEX ROSE
PL
10033
7
ALLEN
ST
10002
8
ALPHONSO B DEAL
ST
10031
1=Help
3=Quit
4=HS
6=Back
8=Down
9=Mat
10=Flip
NOTE: To view more lines of data, enter the FLIP command in the Command
field, or press F10.
286
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
Fields
A description of each field on the Streets in a City or Streets in a ZIP Code screen follows.
Table 35: Fields on the Streets in a City or Streets in a ZIP Code Screen
Field Name
Description
LN
The line number of the street.
Dir
The leading directional for the street.
Street Name
The names of the street.
Sfx
The suffix for the street.
Dir
The trailing directional for the street.
ZIP Codes
The ZIP Code(s) that are valid for this street. This field will
only appear if you accessed this screen from the Cities in the
Database screen, not the Cities in a ZIP Code screen.
Function Keys
The action performed by each function key follows.
Table 36: Fields on the Streets in a City or Streets in a ZIP Code Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Return to the Main Menu.
F4
HS
Go to the Houses on a Street screen.
F6
BACK
Return to the City Information screen.
F7
UP
Scroll the list so that the previous eight streets are
displayed.
F8
DOWN
Scroll the list so that the next eight streets are
displayed.
F9
MAT
Go to the address matching function.
F10
FLIP
Change the screen so that the data fills the entire
physical screen.
NOTE: 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.)
Working With CODE-1 Plus
287
3
Interactive Screen Reference
Geographic Coding Plus Interface
If you have purchased Geographic Coding Plus from Pitney Bowes, you can access
that product directly from CODE-1 Plus. To do so, type the command GEO in the
Command field on any CODE-1 Plus screen. The Geographic Coding Interface
screen will appear. 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 the User's Guide that came with Geographic Coding
Plus for further reference on the fields and function keys on this screen.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Command:
Top
Geographic Coding Interface
ZIP: 20902 ZIP+4: 1104
DPBC: 18
House#: 12018
Match Level:
State Code:
County Code:
Census Tract:
Block Group:
MSA Code:
MSA Name:
ZIP: 20706 ZIP+4: 1882
DPBC: 99
House#: 4200
9
24
031 MONTGOMERY
703404
2
8840
WASHINGTON DC-MD-VA-WV
Lat/Long Level: 4
Latitude: 039.053630 N
Longitude: 077.069344 W
Software: 04.0
1=Help
9
24
033 PRINCE GEORGES
803510
1
8840
WASHINGTON DC-MD-VA-WV
4
038.950609 N
076.834870 W
File: February 2003
8=Down
Distance in miles:
14.459
10=Exit
NOTE: 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.
288
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
Fields
The following table presents a description of, and acceptable values for, each field on
the first Geographic Coding Interface screen.
Table 37: Fields on the First Geographic Coding Interface Screen (Part 1 of 2)
Field Name
Description
ZIP Code
The 5-digit ZIP Code for the entered address.
ZIP+4 Code
The 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
A 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
The 2-character FIPS state code of the matched address.
FIPS County Code
The 2-character FIPS county number and 20-character
county name of the matched address.
Census Tract
The 6-digit number representing the census tract division
within the county.
Block Group
The 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
A code indicating the level of latitude and longitude
determined for the matched address. One of the following
codes appears.
• 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.
Working With CODE-1 Plus
289
3
Interactive Screen Reference
Table 37: Fields on the First Geographic Coding Interface Screen (Part 2 of 2)
Field Name
Description
Latitude
A 9-digit number (with six decimal places implied) followed
by a 1-character directional (N or S) that occupy the first
eight bytes of this area.
Longitude
A 9-digit number (with six decimal places implied) followed
by a 1-character directional (E or W) that occupy the last
eight bytes of this area.
Software Vintage
Indicates the version of Geographic Coding you are using.
File
Indicates the expiration date of the Geographic Coding File
that you are using.
Distance in Miles
The number of miles between the two specified addresses,
if necessary.
Function Keys
The following table describes the action on the first Geographic Coding Interface
screen.
Table 38: Function Keys on the First Geographic Coding
Interface Screen
Function Key
290
Name
Description
F1
HELP
Obtain online help.
F8
DOWN
Go to the last screen of the Geographic Coding
Interface.
F10
CANCEL
Exit from the Geographic Coding Interface.
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
This is the second and last screen of geographic coding data for your matched
address.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Command: ________________________________________
Bot
Geographic Coding Interface Additional Information
ZIP: 20902 ZIP+4: 1104
DPBC: 18
House#: 1201
MCD/CCD Code:
Confidence:
PRIZM Cluster:
Cluster Group:
ZIP: 20706 ZIP+4: 1882
DPBC: 99
House#: 4200
91160
1
21 THE AFFLUENTIALS
S2 SUBURBAN SPRAWL
Place Code: 83837
Class Code: U2 Incorporated:
Place Name: WHEATON-GLENMONT
GeoTAX Key: 21031
Date Annexed
01/1990
Updated
1=Help
No
RC: N
91164
1
52975
U1 No
MITCHELLVILLE
21033
Verified
Annexed
01/1990
N
Updated
Verified
7=Up
10=Exit
Fields
The following table presents a description of, and acceptable values for, each field on
the second and last Geographic Coding Interface screen.
Table 39: Fields on the Second Geographic Coding Interface Screen (Part 1 of 3)
Field Name
Description
ZIP Code
The 5-digit ZIP Code for the entered address.
ZIP+4 Code
The 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.
Working With CODE-1 Plus
291
3
Interactive Screen Reference
Table 39: Fields on the Second Geographic Coding Interface Screen (Part 2 of 3)
Field Name
Confidence
Description
A 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
A 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
A 2-character PRIZM cluster social group code and a 20character group name.
Place Code
A 5-character FIPS place code.
Incorporated
A 1-character code indicating whether the entered address
is in an incorporated area.
• Y — Incorporated
• N — Not incorporated
Class Code
A 2-character class code.
Place Name
A 30-character place name.
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
A 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
292
Place last annexed date.
Software Release 4.0.0/March 2015
Screens that Support Database Inquiry
3
Table 39: Fields on the Second Geographic Coding Interface Screen (Part 3 of 3)
Field Name
Description
Updated
Place last updated date.
Verified
Place last verified date.
Function Keys
The following table describes the resulting action for each function key on the
second and last Geographic Coding Interface screen.
Table 40: Function Keys on the Second Geographic Coding
Interface Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F7
UP
Go to the first screen of the Geographic Coding
Interface.
F10
CANCEL
Exit from the Geographic Coding Interface.
Working With CODE-1 Plus
293
3
Interactive Screen Reference
Screens that Support Site Customization
The screens shown in this section all support the interactive site customization
function.
Administration Sign-on Screen
The Administration Sign-on screen allows you to type in, and optionally update, the
password required to access the site default update screens. This screen is accessed
by typing “ADMIN” from any match or database inquiry screen. If a new password is
typed in, the screen will return with an area to “Confirm New Password.”
If you do not have your initial password, contact Pitney Bowes support at 800-3676950.
The password change process can be stopped by pressing the space bar through both
new password fields, or by selecting Quit or Cancel. The Administration Sign-on screen
is shown below.
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
294
10=Cancel
Software Release 4.0.0/March 2015
Screens that Support Site Customization
3
Fields
The following table presents a description of each field on the Administration Sign-on
screen.
Table 41: 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.
Function Keys
The following table describes the action initiated by each function key on the
Administration Sign-on screen.
Table 42: Function Keys on the Administration Sign-On Screen
Function Key
Name
Description
F1
HELP
Obtain online help.
F3
QUIT
Exit from the Interactive CODE-1 Plus System.
F10
CANCEL
Return to screen from which “ADMIN” was
invoked.
Working With CODE-1 Plus
295
3
Interactive Screen Reference
Interactive Customization Screens
The Interactive Customization screens allow you to view, and optionally update, the
site-specific values you choose for your system. These screens are accessed 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.
The first Interactive Customization screen is shown below.
CODE-1 Plus Coding System
--------------------------------------------------------------------------Command: ________________________________________
Interactive Customization Screen
Page 1 of 3
Display Options
Address Match Settings
Initial Screen: S (S, F)
Expiration Warning: D (D, S)
Initial Command:
Firm: M (T, M, L, E)
Dir/Suffix: M (T, M, L, E)
Street: M (T, M, L, E)
Vanity City Name: X (X, S)
Correct Input ZIP: Y (Y, N)
Use Output Case: U (U, L, C)
Multiple Secondary: Y (Y, N)
Preferred City Name: C (C, Z)
Perform DPV Process:
(Blank, X)
Perform LTO Process:
(Blank, X)
Perform RDI Process:
(Blank, X)
G1M06I Change current Site Default Settings as desired
1=Help
Enter=Verify
3=Quit
5=Save
8=Down
9=Reset
10=Exit
Fields
The following table describes the fields available for update on the first Interactive
Customization Screen.
Table 43: Fields on the First Interactive Customization Screen (Part 1 of 3)
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
296
Software Release 4.0.0/March 2015
Screens that Support Site Customization
3
Table 43: Fields on the First Interactive Customization Screen (Part 2 of 3)
Field Name
Firm
Description
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.
Working With CODE-1 Plus
297
3
Interactive Screen Reference
Table 43: Fields on the First Interactive Customization Screen (Part 3 of 3)
Field Name
Multiple Secondary
Description
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.
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
298
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’.
Software Release 4.0.0/March 2015
Screens that Support Site Customization
3
Function Keys
The following table describes the resulting action for each key on the first Interactive
Customization screen.
Table 44: Function Keys on the First Interactive Customization Screen
Function Key
Name
Description
F1
Help
Obtain online help.
Enter
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.
F3
Quit
Exit the system as defined on the customization
database.
F5
Save
Save current entries after validation. Remain on
screen after save.
F8
Down
Go to the second customization screen.
F9
Reset
Restore screen values to current database entries
(at last update to customization file).
F10
Exit
Return to the screen from which “ADMIN” was
entered.
This is the second Interactive Customization screen.
CODE-1 Plus Coding System
------------------------------------------------------------------------------Command: ________________________________________
Interactive Customization Screen
Page 2 of 3
Processing Options
Geographic Coding Available:
Geo Lat/Long Data Source:
Use Geo County:
ZIP Match Centroid:
Return Alias Base on Match:
N
N
C
N
(N, Y)
(B = Base, A = Advanced, F = Finest)
(N, Y)
(Z = ZIP, C = Census Tract)
(N, Y)
Custom Page Title: C1P 3.6 Cycle N Interactive
Use Navigation: Y
(N, Y)
Enhanced/All Street Matching:
(E = ESM, A = ASM)
Preferred Alias Processing:
(N, Y)
Abbreviated Alias Processing:
(N, Y)
1=Help
Working With CODE-1 Plus
Enter=Verify
3=Quit
5=Save
7=Up
8=Down
9=Reset
10=Exit
299
3
Interactive Screen Reference
Second Interactive Customization Screen With Seed Violation Bypass Option
CODE-1 Plus Coding System
------------------------------------------------------------------------------Command:
Interactive Customization Screen
Page 2 of 3
Processing Options
Geographic Coding Available: N
(N, Y)
Geo Lat/Long Data Source:
(B = Base, A = Advanced, F = Finest)
Use Geo County: N
(N, Y)
ZIP Match Centroid: C
(Z = ZIP, C = Census Tract)
Return Alias Base on Match: N
(N, Y)
*** SEED STOP BYPASS IS ON ***
Custom Page Title: CODE-1 Plus for Windows
Use Navigation: N
(N, Y)
Enhanced/All Street Matching:
(E = ESM, A = ASM)
Preferred Alias Processing:
(N, Y)
Abbreviated Alias Processing:
(N, Y)
G1M07I Change current Processing Options as desired
1=Help
Enter=Verify
3=Quit
5=Save
7=Up
8=Down
9=Reset
10=Exit
CICS
C1P 3.3 CYCLE M CICS
------------------------------------------------------------------------------Command:
Interactive Customization Screen
Page 2 of 3
Processing Options
Geographic Coding Available: N
(N, Y)
Geo Lat/Long Data Source:
(B = Base, A = Advanced, F = Finest)
Use Geo County: N
(N, Y)
ZIP Match Centroid: C
(Z = ZIP, C = Census Tract)
Return Alias Base on Match: N
(N, Y)
*** SEED STOP BYPASS IS ON ***
Custom Page Title: CODE-1 Plus for Windows
Use Navigation: N
(N, Y)
Enhanced/All Street Matching:
(E = ESM, A = ASM)
Preferred Alias Processing:
(N, Y)
Abbreviated Alias Processing:
(N, Y)
CICS Processing Options
Return Transid: CQIT (blank = return to CICS, **** = Issue Disconnect)
TS Queue Utilization: A (A = Auxiliary, M = Main)
G1M07I Change current Processing Options as desired
1=Help
Enter=Verify
3=Quit
5=Save
7=Up
8=Down
300
9=Reset
10=Exit
Software Release 4.0.0/March 2015
Screens that Support Site Customization
3
Fields
The following table describes the fields available for update on the second Interactive
Customization screen.
Table 45: Fields on the Second Interactive Customization Screen (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.
ZIP Match Centroid
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
Working With CODE-1 Plus
The interactive system page title (for all screens) can be
customized using this option.
301
3
Interactive Screen Reference
Table 45: Fields on the Second Interactive Customization Screen (Part 2 of 2)
Field Name
Description
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.
Function Keys
The following table describes the resulting action for each function key on the
second Interactive Customization screen.
Table 46: Function Keys on the Second Interactive
Customization Screen
Function Key
302
Name
Description
F1
Help
Obtain online help.
F3
Quit
Exit the system as defined on the customization
database.
F5
Save
Save current entries after validation. Remain on
screen after save.
F7
Up
Go to the first Interactive Customization screen.
F9
Reset
Restore screen values to current database entries
(at last update to customization file).
F10
Cancel
Return to the screen from which “ADMIN” was
entered.
Software Release 4.0.0/March 2015
Screens that Support Site Customization
3
Definition of PFKEYS
The third and last customization screen allows you to define your program function
keys (PFKEYS). This will enable you 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, looking at the
screen capture below, you can tab down to PFKEY 01 and change the text from “Help”
to “Info.”
CODE-1 Plus Coding System
----------------------------------------------------------------------------Command:
Interactive Customization Screen
Page 3 of 3
PFKEY Assignments
Pfkey
Help: 01
Quit: 03
Down/Next: 08
Back:
06
Save, Reset:
ZC, SC, CZ:
MS, Refresh, GEO:
Alias, AH, FM:
Text
Help
Quit
Down
Up/Previous:
Match, Inquiry:
Flip, Exit/Cancel:
Back
HS:
SZ:
Pfkey
05
02
04
02
Text
Save
ZC
MS
Alias
Pfkey
09
04
05
04
Pfkey
07
09
10
04
04
Text
Reset
SC
RE
AH
Text
Up
Mat
Flip
Text
Inq
Exit
HS
SZ
Pfkey
05
06
05
Text
CZ
Geo
FM
G1M06I Change current Site Default Settings as desired
1=Help
Enter=Verify
3=Quit
5=Save
7=Up
9=Reset
10=Exit
NOTE: You CANNOT assign one PFKEY to have several functions. If you do so, the
screen will state that “Key designation conflicts with a Multi-Screen Key.” Any
errors in defining PFKEYS will appear in red when you hit the ENTER key after
making your changes.
Working With CODE-1 Plus
303
3
Interactive Screen Reference
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 following is a sample of the
information available on the Database Information screen.
NOTE: The DPV database vintage date will appear only if you have performed a
match with DPV turned on.
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:
Output Case: U
ZIP Code:
Urb Name:
Mult Secondary: Y
Override City: Z
Matched Addr:
CRRT:
City,State ZIP:
DPBC:
------------------------------------------------------------------------------Command:
Nav Off
__ of __
DB - Database Information
(1 of 1)
CODE-1 Plus software release 03.3 mod 00 for the current CASS cycle expires
beginning .
CODE-1 Plus January 2009 database expires after 12/30/2008.
There are 103 days remaining until this database expires.
DPV database vintage is 01/2005.
Programs and Design (C) Copyright Pitney Bowes Software, Inc. 2008.
1=Help
304
3=Quit
4=MS
5=RE
6=Geo
9=Inq
10=Flip
Software Release 4.0.0/March 2015
Customization File Administration
3
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.
NOTE: 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, a
number of options exist using program G1CPDFL. For mainframe users there are two
options.
The first option is to physically delete the file and re-run the initialization job,
DEFCUSTM.
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:
1. If an error is detected on the open to the customization file, the program will
attempt to create the file.
2. If the attempt is not successful, the program will issue an appropriate error
message and terminate.
3. If the file is opened successfully, a read will be attempted for the control record.
Working With CODE-1 Plus
305
3
Interactive Screen Reference
4. If the read for the control record fails, the customization utility will add the
control record to the file.
5. If the read for the control record is successful, the customization utility will
search for the admin (password) record.
6. If the admin (password) record is found, the customization utility will display the
encrypted password stored on the record.
If the admin record is not found, the initial install password will be written to the
file.
If required, a decrypting of the password can be obtained by calling Pitney Bowes
Technical Support at (800) 367-6950. Given the 16-character hexadecimal
representation of the password, the Technical Support Representative can provide
you with the current text value of the password.
306
Software Release 4.0.0/March 2015
Batch Uncoded Records Interface (G1CPBNC)
3
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.
NOTE: 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, follow the instructions in the
previous chapter, “Understanding the Interactive Functions,” to use the UR and UW
commands from the CODE-1 Plus Interactive screen.
1. 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:
•
The message that appears
•
The clearing of the Command field to blanks
•
The sounding of an audible alarm
•
The clearing of the address area to blanks
•
The cursor position upon the completion of the UR and UW commands.
Working With CODE-1 Plus
307
3
Interactive Screen Reference
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.
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.
NOTE: 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:
308
•
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-CURSOR-CMD-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.
Software Release 4.0.0/March 2015
Batch Uncoded Records Interface (G1CPBNC)
•
3
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 UXIT-SAVE-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.
•
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.
•
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 UXITADDRESS 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 UXITSAVE-AREA.
Working With CODE-1 Plus
309
3
Interactive Screen Reference
Program Parameters
Eleven logical parameters are passed in a single 01 level. These eleven parameters are
as follows:
Table 47: The G1CPBNC Option Call Areas (Part 1 of 2)
Position
1-2
Name
EXITFUNCTION
Length
in Bytes
2
Contents
The 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
The command line from the Interactive CODE-1 Plus
Command field.
43-121
UXITPROMPTMESSAGE
79
The 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
UXITADDRESS
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.
125
UXIT-CURSOR
1
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.
310
Software Release 4.0.0/March 2015
Batch Uncoded Records Interface (G1CPBNC)
3
Table 47: The G1CPBNC Option Call Areas (Part 2 of 2)
Position
Name
Length
in Bytes
Contents
126-221
UXITRESERVED
96
These bytes are 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.
Working With CODE-1 Plus
311
3
Interactive Screen Reference
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.
NOTE: 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.
312
Software Release 4.0.0/March 2015
CHAPTER 4
Using the Z4CHANGE Option
This chapter describes the CODE-1 Plus Z4CHANGE Option. Instructions are
included for running a Z4CHANGE job and calling the Z4CHANGE program,
C1P430, from your own driver.
What is the Z4CHANGE Option? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Z4CHANGE Option Database . . . . . . . . . . . . . . . . . . . . . . . . .
Rules for Using the Z4CHANGE Option . . . . . . . . . . . . . . . . . . . .
Activating the Z4CHANGE Option, C1P430 . . . . . . . . . . . . . . . . . .
Using Z4CHANGE Option Processing . . . . . . . . . . . . . . . . . . . . . . . . .
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Your Entire List Through CODE-1 Plus . . . . . . . . . .
Each Month, Process Your File Again . . . . . . . . . . . . . . . . . .
Calling C1P430 From Your Own Driver. . . . . . . . . . . . . . . . . . . . . . . .
Generating Reports for Z4CHANGE Processing . . . . . . . . . . . . . . . .
Unix Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
314
314
314
315
315
315
315
316
317
318
319
319
313
4
Using 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-and-address 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.
NOTE: 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.)
NOTE: If the USPS determines that significant changes were made to the CASS
requirements, you must reprocess your entire list using recently-certified
software.
314
Software Release 4.0.0/March 2015
Using Z4CHANGE Option Processing
4
Activating the Z4CHANGE Option, C1P430
To activate and use Z4CHANGE, 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.
The call areas and the procedures for filling in the parameters are described later in
this chapter.
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
If you want to have CODE-1 Plus write the database vintage date in the output
records, do the following:
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)
Working With CODE-1 Plus
315
4
Using the Z4CHANGE Option
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.
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:
316
•
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.
Software Release 4.0.0/March 2015
Calling C1P430 From Your Own Driver
4
Calling C1P430 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.
NOTE: 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:
Table 1: The Z4CHANGE Option Call Areas (Part 1 of 2)
Position
1
Name
PARM-FUNCTION
Length
1
Contents
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. CODE1 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.
Working With CODE-1 Plus
317
4
Using the Z4CHANGE Option
Table 1: The Z4CHANGE Option Call Areas (Part 2 of 2)
Position
40
Name
PARM-RETURNCODE
Length
1
Contents
This 1-character field is filled by C1P430 after the
ZIP Code is checked. One of the following codes
will be placed in 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
9-digit 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 your Getting Started With CODE-1 Plus Guide.
NOTE: The mainframe environment generates the Z4CHANGE reports
automatically when you specify Z4CHANGE options in your batch job. If you work
in a Unix or Windows environment, refer to the sections following the sample
reports for instructions on generating the Z4CHANGE reports.
318
Software Release 4.0.0/March 2015
Generating Reports for Z4CHANGE Processing
4
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
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:
•
Copy the SAMZ4C.BAT file
•
Modify the file to meet your needs
•
Run it.
Pitney Bowes provides the SAMZ4C.BAT file in your CMDS directory. To edit this file:
•
Double-click on the Edit Job File icon
•
Specify SAMZ4C as the job to edit.
Working With CODE-1 Plus
319
4
320
Using the Z4CHANGE Option
Software Release 4.0.0/March 2015
CHAPTER 5
Line of Travel (LTO10)
This chapter describes the Line of Travel (LOT) option. Although LOT is
incorporated in CODE-1 Plus, you may call the Line of Travel matcher from other
applications by calling the Line of Travel subroutine (program LTO10). This chapter
describes the LOT subroutine and lists the associated parameters. This chapter also
describes how to use the LTO60 exit routine to access LOT information from other
Pitney Bowes applications.
What is Line of Travel? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Why Use Line of Travel?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Started with Line of Travel . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Started with Line of Travel . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sorting Your LOT Coded Records . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling the LTO10 Subroutine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input Area — Parameter 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output Area — Parameter 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COBOL Calling Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Calling Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Line of Travel Exit Routine (LTO60) . . . . . . . . . . . . . . . . . . . . . . .
EXITOP Parameter for the LTO60 Exit Routine . . . . . . . . . . . . . . . . .
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line of Travel Exit Routine for Unix . . . . . . . . . . . . . . . . . . . . . . . . . .
Line of Travel Exit Routine for Windows. . . . . . . . . . . . . . . . . . . . . . .
Control Totals Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
322
322
323
323
324
325
326
327
328
329
329
330
332
333
333
334
321
5
Line of Travel (LTO10)
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 1-character 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
NOTE: 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 walksequence. Line of Travel simulates walk-sequence, but only for ten or more pieces per
carrier route.
322
Software Release 4.0.0/March 2015
Accessing Line of Travel
5
Accessing Line of Travel
There are four ways to invoke Line of Travel:
•
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.
•
Exit Routine (LTO60)—The LTO60 exit routine posts Line of Travel
information onto your name-and-address record when passed from any Pitney
Bowes EXEC- level program. Batch driver processing requirements are passed via
the EXITOP parameter.
NOTE: 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.
NOTE: 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
Working With CODE-1 Plus
323
5
Line of Travel (LTO10)
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
NOTE: 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.
NOTE: 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.
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 addon and the LOT sequence code. Refer to Chapter 8 of the CODE-1 Plus Reference Guide
for a table of these codes.
324
Software Release 4.0.0/March 2015
Calling the LTO10 Subroutine
5
NOTE: 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. Refer to Chapter 8 of the CODE-1 Plus Reference Guide for a
table of these codes.
Working With CODE-1 Plus
325
5
Line of Travel (LTO10)
Input Area — Parameter 1
The following table maps the positions in input area Parameter 1.
Table 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.
326
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.
Software Release 4.0.0/March 2015
Calling the LTO10 Subroutine
5
Output Area — Parameter 2
The following table maps the positions in output area Parameter 2.
Table 2: Parameter 2 Output Area Positions (Part 1 of 2)
Position
1
Name
MATCH LEVEL
Length
1
Description
Indicates the level of match obtained against the
Line of Travel Master File.
• 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 nonnumeric DPC or invalid Carrier Route Code.
• 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.
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.
• Blank — No LOT number could be determined,
due to invalid input.
• A — Ascending
• D — Descending
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.
Working With CODE-1 Plus
327
5
Line of Travel (LTO10)
Table 2: Parameter 2 Output Area Positions (Part 2 of 2)
Position
Name
Length
Description
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 add-on 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.
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.
328
Software Release 4.0.0/March 2015
Windows Calling Example
5
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
*/
}
/*
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);
The 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.
Working With CODE-1 Plus
329
5
Line of Travel (LTO10)
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.
Table 3: Fields on the EXITOP Parameter (Part 1 of 2)
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.
Required.
19-22
Location of
ZIP CODE
Location of the input record ZIP Code.
Required.
23
Format of
ZIP CODE
Code indicating the format of your input
record ZIP Code. Enter one of the following:
Required.
LTO60 is dynamically loaded when you
enter this parameter.
• C — 5-digit ZIP Code in character format
• 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.
330
Software Release 4.0.0/March 2015
EXITOP Parameter for the LTO60 Exit Routine
5
Table 3: Fields on the EXITOP Parameter (Part 2 of 2)
Position
Field Name
Description
Comments
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:
Required.
• C — Character format
• 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.
Required.
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.
37-40
Location for
ALTERNATE
SEQUENCE CODE
Location for the 2-character Alternate
Sequence code on the output record.
Optional.
41-44
Location for
HEXADECIMAL
SEQUENCE CODE
Location for the 1-character Hexadecimal
Sequence code on the output record.
45-48
Location for
CARRIER ROUTE
CODE
Location for the input record Carrier Route
Code on the output record.
Required.
50
REPORT
SUPPRESSION
CODE
Determines whether the Control Totals
Report will be printed. Enter one of the
following codes:
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.
• Blank — The report will be printed
(default).
• X — The report will not be printed.
51-66
Working With CODE-1 Plus
RESERVED
These fields are reserved for future use.
331
5
Line of Travel (LTO10)
NOTE: To allow non-COBOL II driver programs to interface with Line of Travel,
see the section titled “Calling C1PRPT” in Chapter 10 for instructions on using
the COB2INIT and/or COB2INI programs provided.
NOTE: 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......................
332
•
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.
Software Release 4.0.0/March 2015
Line of Travel Exit Routine for Unix
5
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)
NOTE: /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.
Working With CODE-1 Plus
333
5
Line of Travel (LTO10)
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:
334
•
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.
•
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 9-digit 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 2-digit 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 4-digit 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 non-numeric 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.
Software Release 4.0.0/March 2015
Control Totals Report
5
•
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.
An example Control Totals Report follows.
Line of Travel Option
LTO60: Control Totals
Line of Travel Option Master File Version:
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
February 2013
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
5,022
LOT Numbers with Ascending Sequence Codes 3,308
LOT Numbers with Descending Sequence Codes 4,703
Alternate DPC Sequence Codes Determined
Line of Travel Option
Working With CODE-1 Plus
2/13/2013
5,022
LTO60: Control Totals
100.00%
100.00%
10.11%
84.99%
15.01%
84.99%
14.74%
85.26%
of
of
of
of
of
of
of
of
Total Records
Records Processed
Records Processed
Records Processed
Records Processed
Records Processed
Records Processed
Records Processed
868
319
4,703
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/2013
335
5
336
Line of Travel (LTO10)
Software Release 4.0.0/March 2015
CHAPTER 6
Using Delivery Point Validation
This chapter introduces Delivery Point Validation (DPV).
NOTE: 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
export rules regulating postal databases go to http://ribbs.usps.gov/.
What is Delivery Point Validation?. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Matches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is a Multiple Match? . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Started with Delivery Point Validation . . . . . . . . . . . . . . . . . .
Installing the DPV Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
z/OS/IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating Delivery Point Validation . . . . . . . . . . . . . . . . . . . . . . .
Delivery Point Validation and Seed Records . . . . . . . . . . . . . . . .
Reporting a Seed Record Match . . . . . . . . . . . . . . . . . . . . . . .
Obtaining a DPV License . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Residential Delivery File Processing . . . . . . . . . . . . . . . . . . . . . . . . .
What is Residential Delivery File Processing? . . . . . . . . . . . . . .
Building the Residential Delivery File in CODE-1 Plus . . . . . . . .
C1DBRDI Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Building Your RDI File in z/OS/IMS. . . . . . . . . . . . . . . . . . . . .
Building Your RDI File in Windows . . . . . . . . . . . . . . . . . . . . .
Building Your RDI File in Unix . . . . . . . . . . . . . . . . . . . . . . . . .
Building Your RDI File in VMS . . . . . . . . . . . . . . . . . . . . . . . . .
FILEDT Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating the RDI Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RDI Large Memory Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DPV Parameters and Return Codes . . . . . . . . . . . . . . . . . . . . . .
DPVIN Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DPVOUT Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
339
339
340
341
341
342
343
346
345
346
348
348
353
355
355
355
356
356
356
357
358
358
359
359
359
359
360
360
361
337
6
Using Delivery Point Validation
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Expiration of DPV Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open/Read Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
“Seed Records” and Stop DPV Processing . . . . . . . . . . . . . . . . .
Software Incompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DPV by List Code Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DPV Processing Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . .
Residential Delivery File Build Report . . . . . . . . . . . . . . . . . . . . . . . .
Residential Delivery File Build Execution Log . . . . . . . . . . . . . . . . . .
338
361
361
361
362
362
363
363
364
364
Software Release 4.0.0/March 2015
What is Delivery Point Validation?
6
What is Delivery Point Validation?
Delivery Point Validation (DPV) was introduced by the USPS to help you validate the
accuracy of your address data to the physical delivery point. This product is available
to you only through a CASS-certified vendor, such as Pitney Bowes.
NOTE: 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; it only
confirms whether an address falls within the low-to-high address range encoded for
the named street. By incorporating the DPV option, CODE-1 Plus can determine
whether the actual address exists, all the way down to the apartment or suite
information. Using the DPV option will reduce your undeliverable-as-addressed
(UAA) mail volume that results from inaccurate addresses, reducing postage costs and
other business costs associated with the handling of inaccurate address information.
DPV will not only confirm the delivery address, it will confirm whether the address is
a commercial mail receiving agency (CMRA) which 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.
DPV can also resolve multiple matches from the ZIP+4 database. This optional
process has the potential for increasing the number of ZIP+4 coded records in your
address list.
Multiple Matches
With the DPV option, every record ZIP+4 coded is automatically processed against
the DPV files. DPV can resolve multiple matches to the ZIP+4 database. Attempting
to resolve ZIP+4 multiple responses will increase your ZIP+4 match rate, but will also
increase processing time. For this reason, you may wish to turn off some of these
options.
The DPVIN parameter sets up the options for multiple match conditions. When
verifying proper candidates for DPV processing, the multiple condition is first
checked at the ZIP Code level, Carrier Route, Directional, and then Suffix (or left to
right on the parameter). There are times when the multiple condition occurs in
multiple categories.
Working With CODE-1 Plus
339
6
Using Delivery Point Validation
Two other options are available on the DPVIN parameter pertaining the Unique ZIP
and Small Town default assignments and multiple secondary components. The figure
on the following page shows examples of the different types of multiple matches that
can be Delivery Point Validated. Please refer to the section “The DPV Parameters and
Return Codes” for details on how you tell DPV to solve these multiple matches.
What is a Multiple Match?
Figure 1: Examples of Multiple Matches in CODE-1 Plus
340
Software Release 4.0.0/March 2015
Getting Started with Delivery Point Validation
6
Getting Started with Delivery Point Validation
Delivery Point Validation consists of a separate database that you must load on to
your system, just like the CODE-1 Plus database. After the initial installation of the
DPV database, Pitney Bowes will provide you with an updated DPV database
approximately every 120 days.
Before you can run Delivery Point Validation, 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.
Installing the DPV Database
In this section, we provide platform-specific instructions for installing your DPV
database. Please note that the DPV database has a 120-day expiration cycle.
Databases expire on the following schedule:
Table 1: DPV Database Expiry Cycle
Database Month
Working With CODE-1 Plus
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
341
6
Using Delivery Point Validation
Windows
After product installation and the appropriate variables have been defined, you are
ready to load the database files. You must have a DPV Database CD-ROM or DVD.
Follow these steps to load the DPV Database:
NOTE: 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. Load the database from the database media. If loading from CD-ROM or DVD,
place the database disk into your CD-ROM drive.
2. 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.
3. 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.
342
Software Release 4.0.0/March 2015
Getting Started with Delivery Point Validation
6
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.
4. If the load completed without errors, you may proceed and run your CODE-1 Plus
jobs. If there were errors, please contact Technical Support.
Unix
Perform the following steps to install your DPV database from the DVD.
NOTE: Our DVDs are formatted as UDF with Rockridge extension.
1. Place the DVD in the drive and close the drive door. If your system auto-mounts,
go to Step 4 now.
2. 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.
3. 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.
NOTE: Your system must allow DVDs created under the ISO 9660 format to be
mounted as a file system.
4. Issue the appropriate source command to setup the environment:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)
Working With CODE-1 Plus
343
6
Using Delivery Point Validation
5. Execute the script for installing the database by typing the following command:
$G1DIR/g1bin/installdb
or
cd to $G1DIR/g1bin and type installdb
6. Select CODE-1 Plus from the menu options, and a sub-menu will appear listing
your file install options.
7. At the prompt on the bottom of the screen, select the Delivery Point Validation
file you want to install; Split, Flat, or Full.
8. 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)
344
Software Release 4.0.0/March 2015
Getting Started with Delivery Point Validation
6
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:
1. Change directory (cd) to the $G1C1P/bin subdirectory.
2. Source the setup script:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)
3. Run the DPV build script, dpvbuild.
The dpvbuild script creates a dpvrts for your system. This executable will be
located in $G1C1P/pgms.
NOTE: 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.
Once the dpvrts runtime environment has been built, you can proceed to the
next step in DPV processing.
VMS
To load the DPV database on VMS, follow these steps:
1. Change directory (set default) to the c1p batch subdirectory, i.e.
device:[directory.BATCH]
2. Run the Database Install script, c1p_master_build.com.
> @c1p_master_build
3. Select Delivery Point Validation (DPV) database you want to install on the List of
Database Build options.
Working With CODE-1 Plus
345
6
Using Delivery Point Validation
4. The load program will create the appropriate sequential files in the database area
(destination directory). The DPV load report and execution log will also be
created on the same directory.
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
DPFALOCF.JCM
Database
Flat DPV Database
DPFDBIND.JCM
DPFDBINS.JCM
DPHALOCF.JCM
Full DPV Database
DPHDBIND.JCM
DPHDBINS.JCM
DPVALOCF.JCM
Split DPV Database
DPVDBIND.JCM
DPVDBINS.JCM
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.
Activating Delivery Point Validation
Follow the steps below to activate DPV processing.
NOTE: CODE-1 Plus customers should be aware that batch jobs running with
DPV Split, LACSLink, and SuiteLink may require up to 377M of GETVIS.
346
Software Release 4.0.0/March 2015
Getting Started with Delivery Point Validation
6
Using Batch Processing to Activate DPV
To activate DPV in batch mode, you must define:
•
DPVIN parameter
•
DPVOUT parameter
•
Five MAILER parameters
NOTE: To process DPV on mainframe, the JCL must have DD statements for the
DPV DB you intend to use.
To retain output information for DPV processing, you must complete the DPVOUT
parameter card.
Using the CODE-1 Plus GUI to Activate DPV
To activate DPV using the CODE-1 Plus GUI, go to the Primary Window and expand
the DPV options. This area will allow you to determine how you want DPV processing
performed.
Please see Delivery Point Validation Field Selections in Chapter 1 for more
information on these options.
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.
Working With CODE-1 Plus
347
6
Using Delivery Point Validation
Delivery Point Validation and Seed Records
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.
NOTE: If you wish to test your file using seed records, go to the Rapid Information
Bulletin Board System (RIBBS) Web site at http://ribbs.usps.gov/, click DPV, click
Delivery Point Validation (DPV) Information, and click the
LACSLINK_PUBLICSEED.txt file to see a list of seed records for LACSLink.
When you encounter a seed record during processing (i.e., a false-positive match
(seed violation)), you are required to do two things:
1. Report the seed record match to Pitney Bowes.
2. Get a new license key to turn DPV back on.
You can accomplish both tasks by going to the Pitney Bowes Web site. Details of how
to do so are provided in the remainder of this chapter.
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
GROUP 1 WEBSITE TO OBTAIN YOUR NEW DPV LICENSE KEY.
S0000000000000000
The alphanumeric in bold above is the code you need to report to Pitney Bowes.
348
Software Release 4.0.0/March 2015
Getting Started with Delivery Point Validation
6
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
CODE-1 Plus 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 false-positive (seed violation) record
information.
Table 2: DPVSEED Header Record (Part 1 of 2)
Position
Working With CODE-1 Plus
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
349
6
Using Delivery Point Validation
Table 2: DPVSEED Header Record (Part 2 of 2)
Position
Length
Description
Format
174-178
5
Number of ZIP codes on file
numeric
179-180
2
Number of false positives
numeric
Table 3: 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
CODE-1 Plus 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.
350
Software Release 4.0.0/March 2015
Getting Started with Delivery Point Validation
6
CODE-1 Plus 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.
Table 4: DPVSEED/P9OUT Map
DPVSEED
Position
DPVSEED
Description
P9OUT
Position
P9OUT
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
CODE-1 Plus API Series
CODE-1 Plus API Series DPV customers must capture the information listed above in
their application interfacing with the DPV-called API and write this information to a
file.
Working With CODE-1 Plus
351
6
Using Delivery Point Validation
DPV customers who call the CODE-1 Plus APIs 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 4 indicates which
fields on the output 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 cDPVFalPos (C and Java API) or DPVFalPos (Visual Basic API). If the
value in this field is a ‘Y’, a DPV Seed Record has been encountered and the DPVSEED
file must be generated.
Table 5: DPVSEED/API Map
DPVSEED
Position
352
DPVSEED
Description
C Output
Field Name
Visual Basic Output
Field Name
Java Output Field
Name
1-2
Street pre-directional
szSALeadDir
SALeadDir
sSALeadDir
3-30
Street name
szSAStrNam
SAStrNam
sSAStrNam
31-34
Street suffix abbreviation
szSAStrSfx
SAStrSfx
sSAStrSfx
35-36
Street post-directional
szSATrailDir
SATrailDir
sTrailDir
37-46
Address primary number
szSAHouseNum
SAHouseNum
sSAHouseNum
47-50
Address secondary
abbreviation
szSAAptType
SAAptType
sSAAptType
51-58
Address secondary number
szSAAptNum
SAAptNum
sSAAptNum
59-63
Matched ZIP code
szFinalZIP
FinalZIP
sFinalZIP
64-67
Matched ZIP+4
szDPBC
(first four bytes)
DPBC
(first four bytes)
sDPBC
(first four bytes)
68-180
Filler
N/A
N/A
N/A
Software Release 4.0.0/March 2015
Getting Started with Delivery Point Validation
6
DPV Seed Record Reporting
For all forms of processing with CODE-1 Plus, if you encounter a seed, it must be
reported to the USPS. We have made available via the Pitney Bowes Support site,
http://www.g1.com/Support, a method in which to report all seeds to the USPS.
When you go through our Support site to report the seed violation, you will also be
given a reactivation license or key to be applied to restart the function in which the
violation occurred. To access the Seed Reporting/License area of our Support site:
1. Login to the Pitney Bowes Support site, http://www.g1.com/Support.
NOTE: If you do not know your User ID and password for the Support website,
please go to the Login screen (http://www.g1.com/support/login.asp) and select
the option to have it e-mailed to you. When you enter your e-mail address as
instructed, it must be an exact match to our customer database. If a successful
match is found, your User ID and password will be e-mailed to the address entered.
2. Go to My Products.
3. Select CODE-1 Plus.
4. Select the appropriate platform with which you are running CODE-1 Plus.
5. Under the Database section, you will see listings for: Delivery Point Validation
(DPV) and LACSLink. For each, there will be a View Available Downloads link under
the LICENSE column of the Database table. Click this View Available Downloads
link for the database of the function that the violation was incurred.
You have now reported your seed record violation and you must obtain a new key to
continue using DPV processing.
Obtaining a DPV License
To obtain a DPV License, you will need to select, via the license form, one of the
following:
1. New License. If you have never installed your DPV license, you can select this
option to be given your CODE-1 Plus DPV first time activation license. To install
this license, execute your license management installation process. This process
is the same the one executed to install your CODE-1 Plus product license.
Working With CODE-1 Plus
353
6
Using Delivery Point Validation
2. Batch. If you encounter a DPV Seed Violation with your CODE-1 Plus batch job,
you must enter the Seed Code and attach the Seed File to be issued a reactivation license. The Seed Code is written out to the PRNTXLG log. You will also
be required to attach the Seed File that is generated by CODE-1 Plus. The Seed
File is defined to CODE-1 Plus using the DPVSEED DD statement that exists in
the JCL, Job Script or Batch file that is used to submit the batch job. Once the
Seed Code and the Seed File have been entered, you can select the Download
License button to acquire your DPV reactivation license. To install the
reactivation license, perform the following:
a.
For Windows, the installation is done using Database Load. Select the
License Management option.
b.
For Unix, execute the INSTALLDB script and select the License
Management option.
c.
For Mainframe, execute the LMDBIND JCL.
3. Interactive. If you encounter a DPV Seed Violation using the Matcher-Inquiry/
G1CP Transaction, please report the address causing the seed violation to
Technical Support. A seed file will be created for you to report via our Support
site. You will not be required to enter a Seed Code if you select the Interactive
Seed Violation option. Once the Seed File has been attached, you can select the
Download License button to acquire your DPV reactivation license. To install the
reactivation license, you can follow the same process as documented under the
New License section for your particular platform.
354
a.
For Windows, the installation is done using Database Load. Select the
License Management option.
b.
For Unix, execute the INSTALLDB script and select the License
Management option.
c.
For Mainframe, execute the LMDBIND JCL.
Software Release 4.0.0/March 2015
Residential Delivery File Processing
6
Residential Delivery File Processing
This section describes Residential Delivery Indicator (RDI) File Processing within
CODE-1 Plus including a description of the C1DBRDI program and instructions for
using the Residential Delivery Indicator to include RDI processing in a CODE-1 Plus
job. You can find a list of supporting reports starting on page 364.
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.
NOTE: 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 on a CD-ROM from the USPS.
Working With CODE-1 Plus
355
6
Using Delivery Point Validation
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 (CD-ROM format).
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.
NOTE: 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.
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.
356
Software Release 4.0.0/March 2015
Residential Delivery File Processing
6
3. Click on [Next] to load your RDI file.
NOTE: 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.
NOTE: 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.
Working With CODE-1 Plus
357
6
Using Delivery Point Validation
Building Your RDI File in VMS
To build your RDI file on VMS, follow these steps:
1. Copy the RDI raw data file obtained from the USPS into the CODE-1 Plus data
subdirectory, i.e. device:[directory.DATA].
2. Change directory (set default) to the CODE-1 Plus batch subdirectory, i.e.
device[directory.BATCH].
3. Run the C1DBRDI script, RDIBUILD.com.
>@RDIBUILD
4. Enter the file name of the RDI file that was placed in the CODE-1 Plus [data]
subdirectory.
5. Enter the file date in YYYYMM format.
6. The load program creates an RDI file in the output area specified in step 4. This
file is a relative record file with the name of RDIMSTR.
7. Ensure that the C1DBRDI file definition variable has been defined and
referenced on the CODE-1 Plus jobs. (Refer to the SMPLXXXX jobs in the BATCH
subdirectory.)
8. CODE-1 Plus can now use the RDI file during processing.
FILEDT Parameter
The following table is an overview of each field on the FILEDT parameter.
Table 6: Fields on the DPVIN Parameter (Part 1 of 3)
Position
358
Field Name
Description
Comments
1-6
KEYWORD
FILEDT is the only acceptable entry.
Required.
8-13
FILE DATE
Date of RDI file being created in YYYYMM
format.
Optional.
Default is to
use the system
date.
Software Release 4.0.0/March 2015
The DPV Parameters and Return Codes
6
Activating the RDI Option
Once you have built the RDI file, you can use RDI in your CODE-1 Plus processing.
You turn on the Residential Delivery Indicator system by placing a Y in column 52 of
the DPVIN parameter. The results for your RDI processing will be printed on the
Delivery Point Validation Processing Summary Report.
You can also produce an RDI Build Report by placing a Y in column 42 of the
REPORT parameter. Or, you can produce the RDI Counts by List Code Report by
placing a Y in column 44 of the REPORT parameter.
The Qualitative Statistical Summary (QSS) section of the PS Form 3553 includes the
RDI counts.
RDI Large Memory Module
We offer the RDI Large Memory Module (DPV040L) to improve speed during RDI
processing. Please refer to Chapter 2 and the PGMNAM parameter for more
information on using DPV040L.
The DPV Parameters and Return Codes
The DPVIN and DPVOUT parameters accommodate all processing requirements for
Delivery Point Validation certification:
•
Delivery Point Validation Processing (presence of DPV in parameter)
•
Delivery Point Validation Options
•
Delivery Point Validation Return Codes
•
Delivery Point Validation Footnote Codes.
DPVIN Parameter
The DPVIN parameter activates DPV processing and provides processing options
based on matches to the ZIP+4 database. This parameter includes the following:
•
Multiple match options for ZIP Code and PO Box or RR/HC address type
•
Multiple match options for ZIP Code and street address type
•
Multiple match options for Carrier Route
•
Multiple match options for Directionals
•
Multiple match options for Suffix
•
Multiple match options for Suffix/Directional correction
Working With CODE-1 Plus
359
6
Using Delivery Point Validation
•
Multiple input secondary components with no designator
•
Option to DPV confirm a unique ZIP/small town default ZIP+4 assigned by
CODE-1 Plus
•
Option to bypass DPV secondary address validation and CMRA lookup
•
Option to attempt PBSA Table lookup
•
Option to attempt Residential Delivery File (RDI) processing
•
Option to determine whether to match against a split file or a flat file
Field-by-Field
For a field-by-field description of the DPVIN parameter, refer to “DPVIN” on
page 146.
DPVOUT Parameter
The optional DPVOUT parameter posts all answers from DPV processing and is
required for DPV processing:
•
Delivery Point Validation Return Codes
•
Delivery Point Validation Footnote Codes.
This parameter comprises the following:
•
Location for DPV return code on the output record
•
Location for DPV Commercial Mail Receiving Agency (CMRA) flag on the output
record
•
Location for DPV false/positive flag on the output record
•
Location for DPV Footnote Codes on the output record
•
Location for a PBSA Flag
•
Location for a Residential Flag
•
Location for a Business Flag
•
Option to produce different types of Business Flags.
DPV Footnote Codes are 2-character, USPS-defined codes that represent the changes
that were made to the input address during the matching process. Up to 10 of these
codes can be stored by CODE-1 Plus for each record. Even if your address is not
presented for DPV processing, those footnote codes that pertain to the match to the
ZIP+4 database will be returned.
360
Software Release 4.0.0/March 2015
Error Messages
6
Field-by-Field
For a field-by-field description of the DPVOUT parameter, refer to “DPVOUT” on
page 152.
Error Messages
This section describes possible error messages that you may receive during DPV
processing.
NOTE: 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 will stop working 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*
****************************************************************************
Another example is:
****************************************************************************
*Database error on DHFDPV -> EXPIRED
*
****************************************************************************
Open/Read Failure
If you have an open/read failure on the DPV database, this message will appear:
****************************************************************************
*OPEN/READ FAILURE ON DPV DATABASE
*
****************************************************************************
Working With CODE-1 Plus
361
6
Using Delivery Point Validation
“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 will stop DPV processing with the error message on the
following page:
**********************************************************************************
*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 GROUP 1 SOFTWARE, 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 GROUP 1 SOFTWARE AND
*
*ANY CUSTOMER OF GROUP 1 SOFTWARE 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 GROUP 1 SOFTWARE. *
*DPV LICENSE UPDATE URL:HTTP://WWW.G1.COM/SUPPORT/LICENSE/DPV.ASP THE FOLLOWING *
*CODE IS NEEDED WHEN ACCESSING THE ABOVE-NOTED GROUP 1WEBSITE TO OBTAIN YOUR NEW *
*DPV LICENSE KEY.S9999999999999999
*
**********************************************************************************
NOTE: 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.
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.*
************************************************************************
362
Software Release 4.0.0/March 2015
DPV by List Code Report
6
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
*************************************************************************************
DPV by List Code Report
The DPV by List Code Report shows you the results of your DPV processing by list
code. This report is printed automatically when your job is run, unless you have an N
in column 40 of the REPORT 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. You will find the following information on this report:
•
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 is printed automatically when your job is run,
unless you have an N in column 38 of the REPORT 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:
•
Delivery Point Validation attempts with percentages
•
Multiple attempts confirmed
•
Unique/Small Town Default ZIP+4 confirmed
Working With CODE-1 Plus
363
6
Using Delivery Point Validation
•
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
NOTE: 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.
Residential Delivery File Build Report
You will find the following information on this report:
•
The 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:
364
•
The date and time of the RDI File build
•
The number of 9-digit input records
•
The number of 11-digit input records.
Software Release 4.0.0/March 2015
CHAPTER 7
Auxiliary File Processing
This chapter discusses the Auxiliary File Processing within CODE-1 Plus. A
description of the C1AUXBLD program, instructions for using the Early Warning
System (EWS) to run the Auxiliary File Option in a CODE-1 Plus job, and supporting
reports are included.
What is the Early Warning System? . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Processing and EWS . . . . . . . . . . . . . . . . . . . . . . . .
Building the Auxiliary File with the Early Warning System . . . . . . .
C1AUXBLD Utility Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Building Your Auxiliary File in z/OS/IMS . . . . . . . . . . . . . . . .
Building Your Auxiliary File in NT . . . . . . . . . . . . . . . . . . . . . .
Building Your Auxiliary File in Unix . . . . . . . . . . . . . . . . . . . .
Building Your Auxiliary File in VMS . . . . . . . . . . . . . . . . . . . .
AUXIL Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Field-by-Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating the Auxiliary File/Early Warning System File. . . . . . . . . .
Auxiliary File Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Build (C1AUXBLD) Reports. . . . . . . . . . . . . . . . . . .
Auxiliary File Build Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Build Execution Log . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auxiliary File Reporting in the CODE-1 Plus Matcher. . . . . . . . . . . .
Working With CODE-1 Plus
366
366
367
367
368
368
368
369
369
370
371
372
372
372
372
373
365
7
Auxiliary File Processing
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.
For more on the
Control Totals
Report, please refer
to the Getting
Started With
CODE-1 Plus.
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.”
NOTE: You must build the Auxiliary File using the C1AUXBLD program, supplied
with your CODE-1 Plus software.
NOTE: 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.
366
Software Release 4.0.0/March 2015
Building the Auxiliary File with the Early Warning System
7
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.
NOTE: 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.
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/.
NOTE: 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.
NOTE: 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.
Working With CODE-1 Plus
367
7
Auxiliary File Processing
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.
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.
368
Software Release 4.0.0/March 2015
AUXIL Parameter
7
Building Your Auxiliary File in VMS
To build your Auxiliary File on VMS, follow these steps:
1. Copy the EWS raw data file obtained from the USPS web site into the
CODE-1 Plus data subdirectory, i.e. device:[directory.DATA].
2. Change directory (set default) to the CODE-1 Plus batch subdirectory, i.e.
device:[directory.BATCH].
3. Run the C1AUXBLD script, C1AUXBLD.com.
> @C1AUXBLD
4. Enter the file name of the Auxiliary File that was placed in the CODE-1 Plus data
subdirectory.
The load program creates an Auxiliary File in the output area specified in step 4. This
file is an indexed sequential file with the name of G1C1AUX.IDX.
Ensure that the G1C1AUX file definition variable has been defined and referenced
on the CODE-1 Plus jobs. (Refer to the SMPLXXXX jobs in the BATCH subdirectory).
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. This parameter comprises the following:
•
Input file number and format
•
5-Digit ZIP location
•
Street name/address line length and location
•
Street suffix, pre-directional, post-directional, house range, secondary range, and
secondary designator locations.
Working With CODE-1 Plus
369
7
Auxiliary File Processing
Field-by-Field
The following table is an overview of each field on the AUXIL parameter.
Table 1: 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:
Required.
• A — Street, Suffix, and Directionals in
a single address line.
• 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
PRE-DIRECTIONAL
Location on the input record of the predirectional information.
Optional.
29-31
Location of
POST-DIRECTIONAL
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
follows: 10-character low range
followed by 10-character high range.
Optional.
NOTE: If there is no house range
information in the input record, populate
this field with leading zeros.
370
Software Release 4.0.0/March 2015
Activating the Auxiliary File/Early Warning System File
7
Table 1: Fields on the AUXIL Parameter (Part 2 of 2)
Position
37-39
Field Name
Location of
SECONDARY RANGE
Description
Location on the input record of
16-character secondary range
formatted as follows: 8-character low
range followed by 8-character high
range.
Comments
Optiona.l
NOTE: If there is no secondary range
information in the input record, populate
this field with leading zeros.
41-43
Location of
SECONDARY
DESIGNATOR
Location on the input record of the
secondary designator.
Optional.
Activating the Auxiliary File/Early Warning System File
For more
information on the
Input Call Area, see
Chapter 9.
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)
NOTE: The Auxiliary matcher is not available as a stand-alone program or as a
callable routine.
See Chapter 2 for
more information
on the AUXIL1
parameter.
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.
Working With CODE-1 Plus
371
7
Auxiliary File Processing
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.
NOTE: 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.
Auxiliary File Build Report
You will find the following information on this report:
•
The 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:
372
•
The date and time of the Auxiliary File build
•
The number of records read
•
The number of virtual records written
•
The number of physical records written.
Software Release 4.0.0/March 2015
Auxiliary File Reporting in the CODE-1 Plus Matcher
7
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:
For more
information on the
Control Totals
Report and the PS
Form 3553, please
refer to the Getting
Started With
CODE-1 Plus.
•
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.
Working With CODE-1 Plus
373
7
374
Auxiliary File Processing
Software Release 4.0.0/March 2015
CHAPTER 8
Using G1G001
This chapter discusses the executable routine G1G001, which enables you to print
detailed reports using your coded records output file. The module is explained, along
with each of the parameters used to execute the module. Additionally, sample
control language is included.
What is G1G001? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using G1G001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input File and Header/Footer Parameters. . . . . . . . . . . . . . . . . . . . .
FILEDF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HEADER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HEADxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UFTxx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UHDxx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Report Layout and Content Parameters. . . . . . . . . . . . . . . . . . . . . . .
CONTRL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONSTANT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MOVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGESZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TESTIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNPK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record Selection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Control Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OpenVMS Control Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IMS JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
z/OS JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unix Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Windows Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
376
376
377
377
379
380
381
382
383
383
385
386
388
389
390
391
392
392
393
394
394
394
394
394
395
396
375
8
Using G1G001
What is G1G001?
G1G001 is a program that you can use to print customized reports of records from
the CODE-1 Plus output files (the CODE-1 Plus output file becomes the G1G001
input file). You can:
•
Define which record elements to print on the report
•
Format those input elements with constant data
•
Print multiple 132-character print lines per input record
•
Print a main header and a date on your reports
•
Print up to three lines of additional header
•
Select or reject records to print based on a list code or a mismatch reason code.
If you use a mismatch reason code, you also have the option of printing a 20character reason (derived from the reason code)
•
Select records by comparing pairs of fields in a single record: if the value of the
first field is different from the value of the second field, the record will print
•
Include or exclude a specific number of records
•
Limit the report to a specific number of pages.
Using G1G001
To use G1G001, define parameters to perform the following functions:
•
Identify your input file.
•
Print Header information on your report.
•
Identify the content and layout of your print lines.
•
Select or reject records for processing.
When printing multiple print lines for each input record, the order of the parameters
makes a difference. Parameters that affect a print line should be grouped together.
Once you have defined your parameters, you will write control language and submit
the job.
376
Software Release 4.0.0/March 2015
Input File and Header/Footer Parameters
8
Input File and Header/Footer Parameters
The following parameters are used to define your input file and the header and footer
lines that are to print on your reports:
•
FILEDF
•
HEADER
•
HEADxx
•
UFTxx
•
UHDxx.
FILEDF
The required FILEDF parameter enables you to define the input file for the G1G001
program.
Field-by-Field
The following table is an overview of each field on the FILEDF parameter.
Table 1: FILEDF Parameter Fields (Part 1 of 2)
Position
Field Name
Description
Comments
1-6
KEYWORD
FILEDF is the only acceptable entry.
Required.
8-15
FILE NAME
Name of the input or output file. Enter
the following name:
Required.
No default.
G1GNAM Input file
17
RECORD FORMAT
Code indicating whether the records in
the file are fixed-length.
Required.
Default is F.
• F — Records are fixed-length.
19-22
RECORD LENGTH
The length, in bytes, of the records in the
file.
Required.
No default.
24-28
BLOCK SIZE
The size, in bytes, of the blocks in the file.
Required.
No default.
Working With CODE-1 Plus
377
8
Using G1G001
Table 1: FILEDF Parameter Fields (Part 2 of 2)
Position
30-33
Field Name
DEVICE TYPE
Description
Comments
The type of device on which this file
resides. Enter one of the following
codes:
TAPE
2311
2314
3310
3330
3340
3350
3370
3375
3380
FBA
35
LABEL TYPE
Code indicating whether the records on
the file have standard or omitted labels.
Enter one of the following codes:
Not used for
z/OS, Unix, or
VAX.
Default is
TAPE.
Default is S.
• N — No labels
• S — Standard labels.
378
39-46
EXIT ROUTINE NAME
Name of the input exit routine that
should be called when G1G001 is ready
to read a record from this file, or the
name of the output exit routine that
should be called when G1G001 is ready
to write a record to the file.
Optional.
No default.
Name must be
entered leftjustified.
50-56
NUMBER OF
RECORDS TO SKIP
Number of records G1G001 should skip
before selecting the first record.
Optional.
No default.
58-64
CROSS-SECTIONAL
SAMPLING
Number indicating the portion of the
records in the file that should be
processed. G1G001 assumes a decimal
point before the first digit.
Optional.
No default.
66-72
MAXIMUM NUMBER
OF RECORDS
Maximum number of records G1G001
should read from or write to this file.
Optional.
No default.
Software Release 4.0.0/March 2015
Input File and Header/Footer Parameters
8
HEADER
The required HEADER parameter enables you to define a date and header text that
identifies the report.
Field-by-Field
The following table is an overview of each field on the HEADER parameter.
Table 2: HEADER Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
HEADER is the only acceptable entry.
Required.
8-17
DATE
The date that G1G001 was executed. 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.
Working With CODE-1 Plus
379
8
Using G1G001
HEADxx
The optional HEADxx parameter enables you to define up to three additional header
lines to print at the top of the report. You can define up to six HEADxx parameters
(two for each line).
Field-by-Field
The following table is an overview of each field on the HEADxx parameter.
Table 3: HEADxx Parameter Fields
Position
Field Name
Description
Comments
1-4
KEYWORD
HEAD is the only acceptable entry.
Required.
5-6
HEADING LINE
DESIGNATOR
One of the following codes to determine the line
number and line side on which this header text
should be printed:
Required.
No default.
• 1A — Left side, line 1
• 1B — Right side, line 1
• 2A — Left side, line 2
• 2B — Right side, line 2
• 3A — Left side, line 3
• 3B — Right side, line 3
The left side refers to positions 1-66, the right side
refers to positions 67-132.
7
SPACE BEFORE
HEADER (for
this heading
print line)
Enter one of the following codes to tell G1G001 how
many blank lines should be printed before this
header line:
Optional.
Default is S.
• S — Single space (no blank lines)
• D — Double space (one blank line)
• T — Triple space (two blank lines).
8-73
380
HEADER TEXT
Any text that you want printed on the top of your
report. If you include the string “MM/DD/YY” or
“MM/DD/YYYY” in this field, G1G001 will print the
date specified in columns 8-17 of the HEADER
parameter in your header text. If columns 8-17 on
the HEADER record are blank, the current system
date will be used. For example, if MM/DD/YY is
specified, then columns 8-15 will be “05/19/09”. If
MM/DD/YYYY is specified, then columns 8-17 will
be “05/19/2009”.
Optional.
No default.
Software Release 4.0.0/March 2015
Input File and Header/Footer Parameters
8
UFTxx
The optional UFTxx parameter enables you to specify any text to print at the bottom
of every page of each report. You can specify up to four footer lines.
Field-by-Field
The following table is an overview of each field on the UFTxx parameter.
Table 4: 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:
Required.
No default.
• A — Left side of the line
• B — Right side of the line.
7-72
Working With CODE-1 Plus
FOOTER TEXT
The text that you want to appear at the
bottom of every page of each report.
Required.
No Default.
381
8
Using G1G001
UHDxx
The optional UHDxx parameter enables you to specify any additional text to print at
the top of each page of each report. You can specify up to four additional header
lines.
Field-by-Field
The following table is an overview of each field on the UHDxx parameter.
Table 5: 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:
Required.
No default.
• A — Left side of the line
• B — Right side of the line.
7-72
382
HEADER TEXT
The text that you want to appear at the
top of each page of every report.
Required.
No Default.
Software Release 4.0.0/March 2015
Report Layout and Content Parameters
8
Report Layout and Content Parameters
The following parameters define how the report lines look and what data prints on
the report lines.
•
CONTRL
•
CONSTANT
•
FORMAT
•
MOVE
•
PAGESZ
•
TESTIT
•
UNPK.
NOTE: G1G001 does not generate the Execution Log.
CONTRL
The required CONTRL parameter enables you to define the following information:
•
Location and length of the key code in the input records (this key code will be
compared to the value entered on the SELECT parameter, explained later in this
chapter, to determine if the record is to be printed).
•
Number of pages that are to be printed.
•
Whether or not page numbers are to be printed on the report.
•
Location of the mismatch reason code in the input record, and the location on
the print line for the mismatch reason.
•
Whether to print the report in mixed case or upper case.
The following table lists the mismatch reason codes for G1G001. These are codes
that CODE-1 Plus stores as General Return Codes. You can identify the mismatch
reason code location in your input record as the location where CODE-1 Plus stored
the General Return Code.
Table 6: General Return Codes (Part 1 of 2)
Working With CODE-1 Plus
A
Apartment match
required
M
Multiple matches
B
Insufficient address
P
Unmatched post-code
C
Unmatched city name
R
Rte Srvc not found
383
8
Using G1G001
Table 6: General Return Codes (Part 2 of 2)
D
Out of sequence
S
Unmatched street
E
External File Match
U
Not attempted
F
Unmatched FSA
V
Non-deliverable ZIP+4
H
Unmatched house/box
X
Out of sequence
I
Unmatched initial
Z
Unmatched ZIP Code
L
Locality failure
Field-by-Field
The following table is an overview of each field on the CONTRL parameter.
NOTE: All input record position fields can be extended one column to the left to
accommodate 4-byte positions, if necessary.
Table 7: CONTRL Parameter Fields (Part 1 of 2)
Position
384
Field Name
Description
Comments
1-6
KEYWORD
CONTRL is the only acceptable entry.
Required.
8-10
KEY CODE
LOCATION
The starting position in the input record
of the key code.
Required.
No default.
12
LENGTH OF KEY
CODE
The length of the key code in the input
record.
Required.
No default.
14-16
NUMBER OF PAGES
The maximum number of pages of the
report that are to be printed.
Optional.
Default is to
print the entire
file.
18
PAGE NUMBERS
Enter a “P” in this column if you want
page numbers printed on your report.
These page numbers will be printed in
positions 125-132 of the first header line.
Optional.
No default.
20-22
MISMATCH REASON
CODE LOCATION
The position in the input record of the
1-character mismatch reason code. Only
records with a non-blank character in
this position will be eligible for printing.
If you do not enter a location, all records
will be eligible for printing.
Optional.
No default.
Software Release 4.0.0/March 2015
Report Layout and Content Parameters
8
Table 7: CONTRL Parameter Fields (Part 2 of 2)
Position
Field Name
Description
Comments
24-26
MISMATCH REASON
PRINT POSITION
The position on the print line for the
20-character mismatch reason (derived
from the mismatch reason code).
Optional.
No default.
28
PRINT UPPER/
LOWER CASE
Enter one of the following codes to
specify whether your report is to be
printed in all upper case or in mixed
case.
Optional.
Default is Y.
• N — Print in mixed case.
• Y — Print in all upper case.
CONSTANT
The optional CONSTANT parameter enables you to define constants to print on the
reports. With the CONSTANT parameter, you can define the data that is the constant,
but not where on the report line that constant is to be printed. You can use MOVE
and FORMAT parameters to specify where to print the constants on the report line.
There are up to eight CONSTANT parameters available, each specifying a single
constant.
Field-by-Field
The following table is an overview of each field on the CONSTANT parameter.
Table 8: CONSTANT Parameter Fields
Position
Field Name
Description
Comments
1-8
KEYWORD
CONSTANT is the only acceptable entry.
Required.
9-10
CONSTANT ID
NUMBER
The number that identifies this constant:
01 - 08. The constant will later be
referenced by C01-C08.
Required.
No default.
12-21
CONSTANT DATA
The data string that is to be associated
with this CONSTANT ID NUMBER. You
can use leading and trailing blanks.
However, depending on the length you
specify for printing the constant on the
MOVE or FORMAT parameters, trailing
blanks can be truncated.
Required.
No default.
Working With CODE-1 Plus
385
8
Using G1G001
FORMAT
The optional FORMAT parameter specifies print line locations for several elements
of your input file and/or constants. G1G001 will concatenate these fields and
constants according to the following rules:
•
FORMAT parameters are executed in the order in which they are defined.
•
The first field to be formatted must not be a constant.
•
There must be at least two fields to be formatted.
•
Two consecutive non-constant fields (i.e., input record elements) automatically
have a space between them.
•
All leading blanks of non-constant fields (i.e., input record elements) are
suppressed and are not printed on the print line.
•
No spaces print between constants and input record elements unless enabled for
in the length of the constant. (In other words, if there is a 2-byte constant, and
you want to print a space between the constant and the input record element that
follows it, define a length of 3 for the constant.)
Field-by-Field
The following table is an overview of each field on the FORMAT parameter.
NOTE: All input record position fields can be extended one column to the left to
accommodate 4-byte positions, if necessary.
Table 9: FORMAT Parameter Fields (Part 1 of 2)
Position
386
Field Name
Description
Comments
1-6
KEYWORD
FORMAT is the only acceptable entry.
Required.
7-8
COMMENT
You can enter any value you wish here to
identify this format operation; G1G001
will ignore this field.
Optional.
No default.
10-12
PRINT LOCATION
The location on the print line to which
you want the input record elements or
constants moved.
Required.
No default.
14-15
TOTAL LENGTH
The length the data concatenated with
this format is to occupy on the print line.
You can enter a number between 1 and
99.
Required.
No default.
Software Release 4.0.0/March 2015
Report Layout and Content Parameters
8
Table 9: FORMAT Parameter Fields (Part 2 of 2)
Position
Field Name
Description
Comments
17-19
25-27
33-35
41-43
49-51
57-59
65-67
73-75
LOCATION OF
FIELDS TO BE
FORMATTED
The starting position in the input record
for the data that is to be printed on the
print line, or the constant ID number. You
can enter an input position or C01-C08
for each of these LOCATION fields. You
must enter at least 2 fields, and no more
than 8. The first blank field will
terminate the processing of this line.
Required.
No default.
20
28
36
44
52
60
68
76
CONSTANT
TREATMENT
A code controlling the formatting of the
constant (this is only valid if the
corresponding LOCATION field is a
constant):
Required.
No default.
21-22
29-30
37-38
45-46
53-54
61-62
69-70
77-78
LENGTH OF FIELDS
TO BE FORMATTED
The length of each of the input record
elements or constants defined in the
LOCATION fields.
Required.
No default.
23
31
39
47
55
63
71
79
ZERO SUPPRESSION
A code indicating whether or not leading
zeros should be suppressed from the
corresponding input record element or
constant. Enter a Z if leading zeros
should be suppressed.
Optional.
Default is to
not print
leading zeros.
80
FORCE PRINT OF
CURRENT LINE
Enter one of the following codes to
indicate whether or not you want to force
the current line to be printed:
Optional.
Default is to
not print the
current line.
• * — Do not print this constant if the
preceding field contains only blanks.
• Blank — Do not print this constant if
the succeeding field contains only
blanks.
• P — Print the current line.
• Blank — Do not print the current line
Working With CODE-1 Plus
387
8
Using G1G001
MOVE
The optional MOVE parameter enables you to specify locations on the print line for
input file elements or constants defined with the CONSTANT parameter. You can
define up to 100 MOVE parameters.
Field-by-Field
The following table is an overview of each field on the MOVE parameter.
NOTE: All input record position fields can be extended one column to the left to
accommodate 4-byte positions, if necessary.
Table 10: MOVE Parameter Fields
Position
Field Name
Description
Comments
1-4
KEYWORD
MOVE is the only acceptable entry.
Required.
5-6
COMMENT
You can enter any value you wish here to
identify this move operation; G1G001 will
ignore this field.
Optional.
No default.
8-10
DESTINATION
The location on the print line to which
you want the input record element or
constant moved.
Required.
No default.
12-13
LENGTH
The length this data is to occupy on the
print line. You can enter a number
between 1 and 99.
Required.
No default.
15-17
SOURCE
The starting position in the input record
for the data that is to be printed on the
print line, or the constant ID number. You
can enter an input position or C01-C08.
Required.
No default.
19
FORCE PRINT OF
CURRENT LINE
Enter one of the following codes to
indicate whether or not you want to force
the current line to be printed:
Optional.
Default is to
not print the
current line.
• Blank — Do not print the current line
• P — Print the current line.
388
Software Release 4.0.0/March 2015
Report Layout and Content Parameters
8
PAGESZ
The optional PAGESZ parameter enables you to specify how many lines to print on
each page of the report.
Field-by-Field
The following table is an overview of each field on the PAGESZ parameter.
Table 11: 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.
Required.
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:
Required.
Default is RPT.
• RPT — G1G001 report.
Working With CODE-1 Plus
389
8
Using G1G001
TESTIT
The optional TESTIT parameter enables you to check the syntax of the parameters
before running the entire job. This parameter has no fields.
If you have this parameter in your job, CODE-1 Plus will check the syntax of your
parameters, and print a parameter report so that you can check that the information
stored on the parameters is really what you intended to store. Then, if all looks good
and there are no errors, you can remove this parameter and submit the job to run.
Field-by-Field
As shown in the table below, the keyword is the only field on the TESTIT parameter.
Table 12: TESTIT Parameter Field
Position
1-6
390
Field Name
KEYWORD
Description
Comments
TESTIT is the only acceptable entry.
Required.
Software Release 4.0.0/March 2015
Report Layout and Content Parameters
8
UNPK
The optional UNPK parameter enables you to print, in an unpacked format, data that
is in the input record in packed format. You can enter up to 100 UNPK parameters.
Field-by-Field
The following table is an overview of each field on the UNPK parameter.
NOTE: All input record position fields can be extended one column to the left to
accommodate 4-byte positions, if necessary.
Table 13: UNPK Parameter Fields
Position
Field Name
Description
Comments
1-4
KEYWORD
UNPK is the only acceptable entry.
Required.
5-6
COMMENT
You can enter any value you wish here to
identify this unpack operation; G1G001
will ignore this field.
Optional.
No default.
8-10
DESTINATION
The location on the print line to which
you want the input record element
printed in unpacked format.
Required.
No default.
12-13
DESTINATION
LENGTH
The length this unpacked data is to
occupy on the print line. This number can
not exceed 18.
Required.
No default.
15-17
SOURCE
The starting position in the input record
of the packed data that is to be unpacked
and printed.
Required.
No default.
19-20
SOURCE LENGTH
The length this packed data occupies in
the input record. This length must not
exceed 10.
Required.
No default.
Working With CODE-1 Plus
391
8
Using G1G001
Record Selection Parameters
The following parameters are used to select or reject records to be printed, or limit
the number of records that are to be printed:
•
SELECT
•
CHANGE.
This section describes these parameters in detail.
SELECT
The required SELECT parameter enables you to specify a value in the input record
key code field that is to be used to select records for printing. If the value in the input
record matches the value you specify on the SELECT parameter, the record will be
selected for printing. If the value in the record is different than the value on the
SELECT parameter, the record will not be selected. You can also choose to select all
records, regardless of the value in the key code field, or you can choose to select all
records that do not contain blanks in the key code field. You can define up to 200
SELECT parameters. The key code location and length are specified on the CONTRL
parameter.
Field-by-Field
The following table is an overview of each field on the SELECT parameter.
Table 14: SELECT Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
SELECT is the only acceptable entry.
Required.
8-16
KEY CODE
COMPARISON
VALUE
The value that should be compared to
the key code in the input record. Or, you
can enter one of the following special
values:
Required.
No default.
ALLKEYS—Every record will be selected,
regardless of the data that is in the input
record key code.
NON BLANK—Only records with nonblank key codes will be selected.
NOTE: If you enter one of these special
values, you can only define one SELECT
parameter.
392
Software Release 4.0.0/March 2015
Record Selection Parameters
8
CHANGE
The optional CHANGE parameter enables you to specify a pair of fields that should
be used to determine if a record is to be selected for printing. For each record, the
data in the first field will be compared to the data in the second field. If the data in
the two fields is different, the record will be selected for printing. If the data is
identical, the record will not be selected for printing. You can enter up to 10
CHANGE parameters.
Field-by-Field
The following table is an overview of each field on the CHANGE parameter.
NOTE: All input record position fields can be extended one column to the left to
accommodate 4-byte positions, if necessary.
Table 15: CHANGE Parameter Fields
Position
Field Name
Description
Comments
1-6
KEYWORD
CHANGE is the only acceptable entry.
Required.
8-10
FIRST COMPARISON
FIELD
The location in the input record of the
first field that is to be used for
comparison.
Required.
No default.
12-13
LENGTH
The length of the two fields that are to be
used for comparison.
Required.
No default.
15-17
SECOND
COMPARISON FIELD
The location in the input record for the
second field that is to be used for
comparison.
Required.
No default.
Working With CODE-1 Plus
393
8
Using G1G001
Sample Control Language
This section lists the file names used in your platform control language to run
G1G001. Each platform section lists the file(s) (JCL, BAT, CMD, and so on) in your
product directories that you should modify according to your site and any
procedures to follow to run G1G001. To minimize maintenance, the files are not
listed.
File Names
Regardless of the environment in which you are running CODE-1 Plus, the following
file assignments are used for executing the G1G001 program:
Table 16: File Names Used for Executing Program G1G001
File Name
Description
G1GPRM
The input parameter file
PRNTRPT
The output printer file
G1GNAM
The input file
OpenVMS Control Language
To run G1G001 in an OpenVMS environment, modify G1G001.COM in the
[xxx.BATCH] directory according to your site’s needs (where xxx is the name of the
directory where you installed the batch product).
IMS JCL
To run G1G001 in an IMS environment, modify the EXG1G001 member in the
SAMPJCL library according to your site’s needs.
z/OS JCL
To run G1G001 in an z/OS environment, modify the EXG1G001 member in the
SAMPLIB library according to your site’s needs.
394
Software Release 4.0.0/March 2015
Sample Control Language
8
Unix Environment
To run G1G001 under Unix, you must complete three steps:
1. Edit the /data/samprt.g1prm file.
2. Source the setup script to setup the CODE-1 Plus environment variables.
3. Source the job (samprt) script to setup the G1G001 job variables.
4. Execute the rung1g001 script to execute the G1G001 batch driver.
Step 1. Edit the /data/samprt.g1prm File
The /data/samprt.g1prm file contains parameters that you can edit for your G1G001
job.
Step 2. Source the setup Script
The setup script sets all the CODE-1 Plus environment variables. The setup script is
in your product $g1c1p\bin directory.
Step 3. Source the samprt Script
The samprt job script assigns file names to all the G1G001 file variables. You will
need to modify the paths, file names, and record lengths for your site. The setup script
is in your product $g1c1p\bin.
Step 4. Execute the rung1g001 Script
The rung1g001 script executes the G1G001 batch driver. The rung1g001 script is
in your product $g1c1p\bin.
Working With CODE-1 Plus
395
8
Using G1G001
Windows Environment
To run the G1G001 program in the Windows environment, you will perform the
following steps:
1. Edit the SAMGRW.BAT file to create your own job file.
2. Edit the SAMGRW.PRM parameter file.
3. Run the Generalized Report Writer job.
Step 1. Edit the SAMGRW.BAT file to Create Your Job
Pitney Bowes provides the SAMGRW.BAT file in your bin directory. Copy and modify
this file to meet your needs. To edit this file, click on the Edit Job File icon and specify
SAMGRW as the job to edit.
Step 2. Edit the SAMGReW.PRM Parameter File
Pitney Bowes provides the SAMGRW.PRM file in your data directory. Copy and
modify this file to meet your needs. To edit this file, click on the Edit Parm File icon
and specify SAMGRW as the file to edit.
Step 3. Run the Job
To run your job, click on the Generalized Report Writer icon. When prompted for the
name of the job to run, enter SAMGRW, (or the name under which you saved your job
file.) 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.
396
Software Release 4.0.0/March 2015
CHAPTER 9
Calling CODE-1 Plus Matching, Analyzer,
and Callable Batch Driver Modules
This chapter describes how to call program modules that match input addresses and
add ZIP + 4 and carrier route codes or analyze the input lines.
CODE-1 Plus Matching Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is C1MATCHx?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is C1ANZADR?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is C1BMCBD? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is EXTADDR2? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Casing Your Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Format of Cased Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Casing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Call Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling CODE-1 Plus on z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using COBxSTUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using COBxINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling C1MATCHx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COBOL Call to Batch Version of C1MATCHx . . . . . . . . . . . . . . . .
The Input Call Area (P9IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Output Results Call Area (P9OUT) . . . . . . . . . . . . . . . . . . . . .
Output Audit Call Area (P9AUDIT). . . . . . . . . . . . . . . . . . . . . . . . .
Unmatched Data Call Area (P9INTRF) . . . . . . . . . . . . . . . . . . . . .
CICS Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COBOL Call to CICS Version of C1MATCHI . . . . . . . . . . . . . .
IMS Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COBOL Call to IMS Version of C1MATCHx . . . . . . . . . . . . . . .
COBOL Call to IMS Version of C1MATCHI . . . . . . . . . . . . . . .
Calling CODE-1 Plus from Unix, Windows, or VMS . . . . . . . . . . .
Calling C1ANZADR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANALYSIS-PARAMETERS Call Area . . . . . . . . . . . . . . . . . . . . . . .
ANALYSIS-NORMALIZATION Call Area . . . . . . . . . . . . . . . . . . . .
Calling C1BMCBD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling C1BMCBD in IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling the Address Line Extraction Module (EXTADDR2) . . . . . . . .
Calling EXTADDR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supplied Copybooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
398
398
399
399
399
403
403
404
399
400
400
402
403
404
405
414
443
444
444
446
446
449
453
454
455
455
456
459
461
462
462
463
397
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
CODE-1 Plus Matching Modules
What is C1MATCHx?
Callable matching modules are programs that CODE-1 Plus uses to analyze your
input addresses and attempt to match those addresses to the CODE-1 Plus database.
These modules, designed to be called from your own applications, enable you to tailor
CODE-1 Plus to meet very specific processing needs.
The following callable modules match your input addresses against the CODE-1 Plus
database.
Table 1: Callable Matching Modules
Module
Description
Memory Used
C1MATCHI
Matcher for interactive processing
C1MATCHB
Default matcher for batch processing
3 MB
C1MATCHS
Matcher for batch processing
1 MB (small
memory model)
C1MATCHM
Matcher for batch processing
6 MB (medium
memory model)
C1MATCHL
Matcher for batch processing
12 MB (large
memory model)
C1MATCHH
Matcher for batch processing
28 MB (huge
memory
model).
NOTE: To call an optional C1MATCHx memory model, refer to the PGMNAM
parameter described in Chapter 2. “Above the Line” mainframe users should
assign a region size of 1 MB. The 12 and 28 MB memory models are not available
for “Below the Line” and “Static Linked” Mainframe users.
These modules:
398
•
Process instructions you specify
•
Match the input record against the CODE-1 Plus database
•
Store the match results (standardized addresses and return codes) and
processing statistics
Software Release 4.0.0/March 2015
Call Areas
9
NOTE: SMPLDRVR2, a sample COBOL batch program that demonstrates the
techniques used to call C1MATCHx, the address line extraction module
EXTADDR2, and the callable print program C1PRPT, have been provided for your
convenience. You can find the source code for this program with the other sample
files that you received with CODE-1 Plus.
What is C1ANZADR?
C1ANZADR is the callable module that analyzes an input address. C1ANZADR
analyzes the elements of an address for use by the C1MATCHx modules during the
matching process. The specialized nature of the analyzer implies that it can not be
used for standardizing mailing addresses. The analyzer performs various
transformations on the input address to facilitate the matching process. These
transformations make the output unusable for label printing, etc.
You can use the analyzer to normalize input addresses to USPS standards.
C1ANZADR formats the address elements into a human-readable string that you can
use on mailing labels, envelopes, etc.
What is C1BMCBD?
C1BMCBD allows a user-supplied program to submit one address at a time to
CODE-1 Plus for matching.
What is EXTADDR2?
EXTADDR2 uses up to six address lines to return two lines to be passed to the
CODE-1 Plus matcher.
Call Areas
TIP: Do NOT alter
the copybooks in
any way.
When you call a CODE-1 Plus module, you must pass, as parameters (addresses), the
names of the pre-defined call areas. These call areas are blocks of memory containing
data that is used by both your program and the CODE-1 Plus Matcher. Each call area
has a specific copybook with which it is associated. These copybooks describe the
data that is stored in each byte of the call area. The copybooks are very specific, so
that the driver and called module “know” where each piece of data is stored in the call
area. Therefore, the copybooks must not be altered in any way.
Working With CODE-1 Plus
399
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Copybooks of the call areas are supplied to call the Batch Matchers (C1MATCHx) as
COBOL (P9IN, P9OUT, P9AUDIT, and P9INTRF), Assembler (ASMPARMI and
ASMPARMO), and PL/I (PLIP9I and PLIP9O).
NOTE: Note: Assembler and PL/I versions of P9INTRF are not provided.
If you are calling the CODE-1 Plus matcher from a CICS application, you must use
the C1MATCHI matcher and pass a single 01-level call area. The copybook P9COMM
is supplied with the software and it combines the call areas previously described.
Calling CODE-1 Plus on z/OS
When you call CODE-1 Plus from your own application in a z/OS environment, there
are a few considerations.
LE conforming
languages, such as
High-Level
Assembler, RPG,
and C are included
for LE. You will not
need to initialize the
LE Runtime
Environment for
these languages.
If you are using non LE-programming languages, the Language Environment (LE)
runtime environment must be initialized prior to the first call to CODE-1 Plus. You
can do this by using either the COBxSTUB, or the COBxINI programs as described on
the following page. Or you may write your own routines to perform this task. The
sections on the following pages explain how to initialize the runtime environment
from programs written in other languages using COBxSTUB and COBxINI.
NOTE: When you call CODE-1 Plus from your own application in an z/OS
environment, you must initialize the P9AUDIT and P9IN areas to SPACES before
the first call to C1MATCHx. C1MATCHx then initializes all the numeric fields to
the proper values. You should not initialize these structures after the initial call
(including the last call which terminates the process).
Using COBxSTUB
If the non-COBOL user-written program that calls CODE-1 Plus is a batch program,
you can use the appropriate COBxSTUB program, which is shipped with
CODE-1 Plus, to initialize the runtime environment. Use COBMSTUB for initializing
the LE (z/OS) Runtime.
This method is easier to use than the COBxINI method described later. Using the
COBxSTUB method, the name of the user-written program is passed as a parameter
through JCL and that program is dynamically called. The COBxSTUB program is
written in the appropriate COBOL language. In this fashion, COBxSTUB becomes the
top program in the calling heap/stack and causes the LE runtime environment to be
initialized before the user- written program is executed. We recommend that the
user-written program perform a dynamic call to the CODE-1 Plus matcher.
400
Software Release 4.0.0/March 2015
Call Areas
9
Sample z/OS JCL
//yourjobcard
//yourstep EXEC PGM=COBxSTUB,PARM='your_program_name',REGION=0M
//STEPLIB DD DSN=yourhlq.CODE1P.LOADLIB,DISP=SHR
//
DD DSN=yourRTlib,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSOUT
DD SYSOUT=*
//**********************************************************************
//* CODE-1 Plus DATABASE FILE DEFINITIONS
//**********************************************************************
//CITYDB
DD DSN=yourhlq.CODE1P.CITYDB,DISP=SHR
//COUNTY
DD DSN=yourhlq.CODE1P.COUNTY,DISP=SHR
//DTLDB
DD DSN=yourhlq.CODE1P.DTLDB,DISP=SHR
//G1C1AUX DD DSN=yourhlq.CODE1P.G1C1AUX,DISP=SHR
//LCLDB
DD DSN=yourhlq.CODE1P.LCLDB,DISP=SHR
//LTMASTR DD DSN=yourhlq.CODE1P.LOTDB,DISP=SHR
//ZIPIDX
DD DSN=yourhlq.CODE1P.ZIPIDX,DISP=SHR
//*****************************************************************
//* DPV FILES
//*****************************************************************
//DPVDB
DD DSN=yourhlq.GROUP1.DPVE,DISP=OLD
for Flat DPV DB
//DPVHDB
DD DSN=yourhlq.GROUP1.DPVHE,DISP=OLD for Full DPV DB
//DPVSDE
DD DSN=yourhlq.GROUP1.DPVSE,DISP=OLD for Split DPV DB
//
*****************************************************************
//* GROUP 1 LICENSE FILE
//*****************************************************************
//G1LICEN DD DSN=yourhlq.GROUP1.G1LICEN,DISP=OLD
//*****************************************************************
//* STATISTICAL FILE
//*****************************************************************
//G1STAT
DD
DSN=yourhlq.CODE1P.G1STAT,DISP=(,CATLG,DELETE),
//
UNIT=SYSDA,
//
DCB=(RECFM=U,RECL=1024,BLKSIZE=8192),
//
SPACE=(CYL,(1,1))
//*****************************************************************
//* INPUT, OUTPUT, AND PRINT REPORT DEFINITIONS
//*****************************************************************
//C1BMNAM DD DSN=yourhlq.CODE1P.IVP.NAMEADDR,DISP=SHR
//C1BMCOK DD DSN=NULLFILE,
//
DCB=(RECFM=FBA,LRECL=133,BLKSIZE=133)
//PRNTRPT DD SYSOUT=*,DCB=(RECFM=F,LRECL=133,BLKSIZE=133)
//PRNTXLG DD SYSOUT=*,DCB=(RECFM=F,LRECL=133,BLKSIZE=133)
//PRNTCAS DD SYSOUT=*,DCB=(RECFM=F,LRECL=133,BLKSIZE=133)
//*****************************************************************
//* CODE-1 Plus IVP FILE PARAMETER RECORDS
//*****************************************************************
//C1BMPRM DD DSN=yourhlq.CODE1P.PARFILE,DISP=SHR
/*
//
Working With CODE-1 Plus
401
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Using COBxINI
In this section we give you all the necessary information for using the COBxINI
program.
Initializing the LE Runtime
If you are using non-LE-conforming languages, follow the steps below to initialize the
LE runtime environment:
1. Add the following to the WORKING STORAGE SECTION:
NOTE: Replace the x in the examples below with M for z/OS.
10 COBx-RETURN-CODE PIC S9(9) COMP
88 COBxINI-OK VALUE ZERO.
88 COBxINI-ALREADY VALUE +4,
VALUE ZERO.
2. Add the following to the PROCEDURE DIVISION to execute once before the first
call to C1MATCHx or C1ANZADR:
CALL 'COBxINI' USING COBx-RETURN-CODE.
IF COBxINI-OK
NEXT SENTENCE
ELSE
IF COBxINI-ALREADY
(display a message “LE already initialized” continue the run)
ELSE
(handle error-condition and terminate the run).
3. Compile/Assemble your program and link with the library/sublibrary that
contains the COBxINI object. If you use another language other than COBOL,
you can apply the same techniques described above, simply convert the COBOL
language syntax into the syntax of the programming language that you use.
402
Software Release 4.0.0/March 2015
Calling C1MATCHx
9
Calling C1MATCHx
The C1MATCHx modules (C1MATCHB, C1MATCHS, C1MATCHM, C1MATCHL,
C1MATCHH) take, as parameters, the names of the following call areas:
•
A 600-character input call area called P9IN, which contains the input address
information and the processing requirements
•
A 5,000-character output call area called P9OUT, which contains the match
results and return codes
•
An 800-character output call area called P9AUDIT, which contains audit
statistics.
•
An optional 2048-character output call area called P9INTRF, which contains
unmatched data.
NOTE: COBOL copy members of the call areas are provided on your installation
tape (in the sample library). These copy books are named P9IN, P9OUT, P9AUDIT,
and P9INTRF.
You must initialize the call areas to SPACES before the first call to C1MATCHx.
C1MATCHx then initializes all the numeric fields in P9AUDIT.
Casing Your Output
You can choose to output your CODE-1 Plus results in upper, lower or mixed case.
This option is part of the input parameter to program C1MATCHx. Position 10,
P9ICASE, may contain either a C, an L, or a blank to specify whether or not to case
the output results from calling program C1MATCHx. A value of C specifies that mixed
casing is to be performed, a value of L specifies that lower casing is to be performed,
and a blank specifies that upper casing is to be performed
Format of Cased Output
All fields that are returned in mixed case have the exception of known USPS
addressing recommendations, including the following:
•
All pre-and post-directionals are uppercase.
•
All box numbers containing alphabetic characters are returned all uppercase.
•
All state abbreviations remain all uppercase.
•
PO, HC, and RR literals remain all uppercase.
Working With CODE-1 Plus
403
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
There are no exceptions for fields returned in lower case.
Special Casing Requirements
Keep in mind the following special casing requirements for mixed-case output:
•
All words with a length greater than three characters and starting with “MC” are
returned with the letter following “MC” uppercased. For example, MCKEE
becomes McKee.
•
An alphabetic character following a non-space, non-alphabetic character is
returned uppercase. For example, F2F remains F2F. This rule has two exceptions:
–
All ordinal numbers are recognized and cased properly. Both consonants
following digits are lowercase. For example, 2ND becomes 2nd.
–
All words ending with “‘S” are cased properly. For example, ALEXANDER’S
becomes Alexander’s.
There are no special casing requirements for output returned in lower case.
COBOL Call to Batch Version of C1MATCHx
The following is a sample COBOL call to C1MATCHx (including C1MATCHI).
CALL WS-C1MATCHx USING P9IN
P9OUT
P9AUDT
P9INTRF
NOTE: You must set P9I-PRM4 to “Y” to indicate the presence of P9INTRF
(P9INTRF is not supported in C1MATCHI).
The remainder of this section presents the maps for each call area.
404
Software Release 4.0.0/March 2015
The Input Call Area (P9IN)
9
The Input Call Area (P9IN)
The following table is a map of the positions in the 600-byte P9IN input call area.
Table 2: Input Call Area (P9IN) (Part 1 of 9)
Position
1
Name
P9IFNC
Length
1
Contents
A 1-character code indicating what you want C1MATCHx
to do with the information in this call area. Type one of the
following values:
• 5 — C1MATCHx will perform an address match,
including ZIP Code correction, if necessary.
• 9 — C1MATCHx will perform an address match, but will
not attempt any ZIP Code correction (that is, the match
will be restricted to those addresses in the original
input ZIP Code, if there are any).
• E — End-of-job indicator; C1MATCHx will not perform
an address match, but will close its files and
subprograms.
NOTE: With this option, no standardized city and state
will be returned.
• Any other value is interpreted the same as 5, above.
2
P9ILLO
1
A 1-character code indicating if you want to conduct a
limited address match based on ZIP Code locality.
• Blank — Standard Processing (default)
• X — Limit Address Match to ZIP locality
NOTE: Setting this option will to “X” will produce a nonCASS certified configuration. No PS Form 3553 will be
generated.
3
P9ISTM
1
A 1-character code indicating the strictness of the street
name match. Type one of the following codes:
• E — The input street name must match the database
exactly.
• T — The matching algorithm is to be “tight.”
• M — The matching algorithm is to be “medium”
(default).
• L — The matching algorithm is to be “loose.”
Any other value is treated as M. (To generate Form 3553,
a value must be typed.)
Working With CODE-1 Plus
405
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 2: Input Call Area (P9IN) (Part 2 of 9)
Position
4
Name
P9IFMM
Length
1
Contents
A 1-character code indicating the strictness of the firm
name match. Type one of the following codes:
• E — The input firm name must match the database
exactly.
• T — The matching algorithm is to be “tight.”
• M — The matching algorithm is to be “medium”
(default).
• L — The matching algorithm is to be “loose.”
Any other value is treated as M. (To generate Form 3553,
a value must be typed.)
5
P9IDSM
1
A 1-character code indicating the strictness of the
directional/suffix match. Type one of the following codes:
• E — The input directional and suffix must match the
database exactly.
• T — The matching algorithm is to be “tight.”
• M — The matching algorithm is to be “medium”
(default).
• L — The matching algorithm is to be “loose.”
Any other value is treated as M. (To generate Form 3553,
a value must be typed.)
6
P9INAD
1
A 1-character code indicating whether the match should
return normalized address information. You can obtain
normalized address elements simultaneously with the
regular address match call—a single call can provide both
standardized and normalized address elements.
Additionally, if normalized address information is
requested, DSF2 footnotes are also returned.
• N — Provide normalized address elements for input
address lines.
Any other value does not return normalized address
elements.
7
P9ITEST
1
A 1-character code indicating whether to invoke a special
database mode function.
• V — Override database expiration.
Any other value invokes the normal matching operations.
8
P9IFC9
1
A 1-character code indicating whether or not the matcher
should return a vanity city name if it is the best match for
the input city name. Type one of the following codes:
• Blank — Never return a vanity city (default).
• X — Return a vanity city if it is the best match.
Any other value is treated as blank.
NOTE: Setting this indicator to X (when calling the
matcher directly from your own driver) produces a nonCASS-certified configuration. No USPS Form 3553 is
generated.
406
Software Release 4.0.0/March 2015
The Input Call Area (P9IN)
9
Table 2: Input Call Area (P9IN) (Part 3 of 9)
Position
9
Name
P9IDUAL
Length
1
Contents
A one-character code indicating how CODE-1 Plus should
return a match if multiple non-blank address lines are
present or multiple address types are on the same
address line.
• Blank — Normal match scoring for street address
elements, input ZIP Code, matching address line, and
so on (default).
• S — Return a street match, regardless of the address
line.
• P — Return a PO Box match, regardless of the address
line.
NOTE: Under normal conditions, a PO Box cannot match if
the city name and input ZIP Code are both changed.
DMM 708 states to match to a PO Box first when on the
same address line or the PO Box address is the primary
address line.
10
P9ICASE
1
A one-character code indicating whether or not to case
the output results from calling program C1MATCHx.
• C — Results will be output in mixed case where
appropriate
• L — All output will be returned in lower case.
• Blank — All output will be returned in upper case
(default).
11
P9ILOT
1
A one-character code indicating whether to attempt Line
of Travel matching.
• Blank — Do not attempt to perform Line of Travel
matching (default).
• X — Perform Line of Travel matching
12
P9IEALT
1
A one-character code indicating the matching preference
when a match is made to an alternate highrise record and
the input address contains secondary address data.
• Y — Attempt to match to the base address (default).
• N — Return the match to the alternate highrise record.
NOTE: Setting this indicator to N will produce a nonCASS-certified configuration. No USPS Form 3553 will be
generated.
13
P9ISCM
1
A one-character code indicating the matching preference
when multiple secondary components are found on the
input address.
• Y — Attempt to find an exact ZIP+4 match to each
secondary component (default).
• N — Match to the default.
NOTE: Setting this indicator to N will produce a nonCASS-certified configuration. No USPS Form 3553 will be
generated.
Working With CODE-1 Plus
407
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 2: Input Call Area (P9IN) (Part 4 of 9)
Position
14
Name
P9IZCT
Length
1
Contents
A one-character code indicating the preferred city name.
• Z — Return ZIP+4 File Preferred Last Line City Name
(override city name).
• C — Return city name from USPS City/State File
(default city name)
• P — Return the Primary City
NOTE: The default for this field is Z when calling
C1MATCHx. The default for C1BM00 is Z.
15
P9IDPV
1
• Blank — Do not attempt to perform DPV processing
(default).
• X — Perform DPV processing
16
P9IDPV-ZCP
1
• Blank — Perform DPV (default).
• N — Do not attempt to DPV when multiple condition is
due to ZIP Code - PO Box/Rural/HC
17
P9IDPV-ZCA
1
• Blank — Perform DPV (default).
• N — Do not attempt to DPV when multiple condition is
due to ZIP CODE – Street Address
18
P9IDPV-CR
1
• Blank — Perform DPV (default).
• N — Do not attempt to DPV when multiple condition is
due to Carrier Route
19
P9IDPV-DR
1
• Blank — Perform DPV (default).
• N — Do not attempt to DPV when multiple condition is
due to Directional (non-Cardinal rule)
20
P9IDPV-SFX
1
• Blank — Perform DPV (default).
• N — Do not attempt to DPV when multiple condition is
due to Suffix (none on input)
21
P9IDPV-SDC
1
• Blank — Perform DPV (default).
• N — Do not attempt to DPV when multiple condition is
due to Suffix or Directional Correction
22
P9IDPV-SC
1
• Blank — Perform DPV (default).
• N — Do not attempt to DPV when Multiple Input
Secondary Components with no Designator
23
P9IDPV-USD
1
• Blank — Perform DPV (default).
• N — Do not attempt to DPV confirm when Small Town
Default ZIP+4 assigned or Unique ZIP Default ZIP+4
assigned.
408
Software Release 4.0.0/March 2015
The Input Call Area (P9IN)
9
Table 2: Input Call Area (P9IN) (Part 5 of 9)
Position
24
Name
P9IDPV-10L
Length
1
Contents
This field allows you to process the DPV large memory
module to increase processing speed. Please note this
will require 18MB of memory.
• Blank — Use DPV010 for DPV processing (default).
• X — Use DPV Large memory Module DPV010L for DPV
processing.
25
P9IDPV-CMRA
1
Controls the CMRA lookup bypass
• Blank — Perform CMRA lookup (default).
• N — Do not perform CMRA lookup.
26
P9IDPV-BYS
1
Controls bypass of DPV validation on secondary
addresses.
• Blank — Perform DPV validation on secondary
addresses (default).
• N — Do not perform DPV validation on secondary
addresses.
27
P9IRDI
1
Controls whether or not to perform RDI processing.
• Blank — Do not attempt RDI processing (default).
• X — Attempt RDI processing.
28
P9IDPV-40L
1
This field allows you to process the RDI large memory
module to increase processing speed. Please not this will
require 16 MB of memory.
• Blank — Use DPV040 for RDI processing (default).
• X — Use Large Memory Module DPV010L and
DPV0130L for processing.
29
P9ISTE
1
This field allows you to specify how SuiteLink errors will be
treated.
• 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”.
• 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
1
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).
• Y — Bypass SuiteLink database expiration processing.
Working With CODE-1 Plus
409
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 2: Input Call Area (P9IN) (Part 6 of 9)
Position
31
Name
P9ISTE-SMM
Length
1
Contents
Controls the SuiteLink memory module size to use for
processing.
• Blank — DPV process will be using Medium memory
model (default).
• 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).
32-34
Reserved
3
35
P9ICMRAPMB
1
Controls whether to convert secondary information to
PMB.
• Blank — Do not convert secondary information to PMB.
• Y — Yes, convert secondary information to PMB where
appropriate.
• N — No, do not convert secondary information to PMB.
36
P9IR777-ZP4
1
Controls whether to suppress ZIP + 4 for addresses
assigned a phantom Carrier Route R777 (not eligible for
street delivery).
• Y — Yes, if Carrier Route R777 is found, add to the
ZIP + 4 Suppressed Count on the USPS Form 3553.
R777 addresses are not deliverable. Do not store the
ZIP + 4 (DPBC).
• Blank — If Carrier Route R777 is found, do not add to
the ZIP + 4 Suppressed Count on the USPS Form 3553.
R777 addresses are deliverable. Store the ZIP + 4
(DPBC).
37
P9IDPV-PBSA
1
Controls P. O. Box Street Address (PBSA) Table lookup.
• Blank — Do not perform PBSA Table lookup.
• Y — Yes, perform PBSA Table lookup.
• N — No, do not perform PBSA Table lookup.
38
P9IDPV-NOST
1
Controls DPV No Stat Lookup Bypass.
• Y — Perform DPV No Stat Lookup
• N — Do not perform DPV No Stat lookup (Default)
39
P9IDPV-VACT
1
Controls DPV Vacant Lookup Bypass.
• Y — Perform DPV Vacant Lookup
• N — Do not perform DPV Vacant lookup (Default)
410
Software Release 4.0.0/March 2015
The Input Call Area (P9IN)
9
Table 2: Input Call Area (P9IN) (Part 7 of 9)
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.
41
P9I-PRM4
1
Code indicating whether the fourth parameter, P9INTRF,
is present and to be processed.
• Blank — The fourth parameter, P9INTRF, is not present
and should not be processed.
• Y — The fourth parameter, P9INTRF, is present and
should be processed.
42
P9ISIN
1
Code indicating whether to perform Split Indicia
processing:
• Blank — Do not perform split indicia processing
(default).
• Y — Perform split indicia processing
43
P9ICZO
1
Controls the population of the CITY/STATE P9OUT areas
for the input ZIP Code when there is no match to the US
Postal Database. P9OUT areas are: P9OCL9, P9OCS9,
P9OCTL, P9OCTS, and P9OSTA.
• Blank — Do not return city/state for input ZIP Code
(default).
• Z — Return city/state for input ZIP Code.
44
P9ISSM
1
Controls whether to do enhanced street matching (ESM)
or All Street Matching (ASM).
• Blank — Do not use enhanced street matching
(default).
• A — Attempt match to all streets in locality (matches to
misspelled first letter in street name)
• S — Use enhanced street matching.
45
Reserved
1
46-50
P9IZIP
5
The 5-digit ZIP Code for the address to be matched.
51-54
P9IZIP4
4
The 4-digit ZIP+4 Code for the address to be matched.
55-154
P9IAD1
100
The primary address line.
155-254
P9IAD2
100
The secondary address line.
255-354
P9IFRM
100
The firm name, left-justified, in human-readable format.
If no firm name is available, or if you do not wish firm-level
ZIP+4 matching to be performed, leave this field blank.
Working With CODE-1 Plus
411
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 2: Input Call Area (P9IN) (Part 8 of 9)
Position
355-454
Name
P9ICST
Length
100
Contents
The city/state information. (Each component must be
separated by at least one blank.) You can use the first 99
bytes of this field, but do not use byte 100. It is reserved for
internal processing.
455-489
P9IURB
35
Urbanization name (without state name).
490
P9IENV
1
A one-character code indicating the environment in which
the C1MATCHx program is executing:
• B — C1MATCHx is being called in a batch environment
(default).
• I — C1MATCHx is being called in an interactive
environment.
Any other value is treated as B.
491-500
P9IDBL
10
These bytes are reserved for the AS/400 platform.
501
P9IAUX
1
A one-character code indicating Auxiliary File processing:
• Blank — Not performed (default).
• X — Perform Auxiliary File processing.
502-525
Reserved
24
526
P9I-PREFER
1
A one-character code indicating Preferred Alias
Processing.
• Y — Use Preferred Alias Processing.
• N — Do Not Use Preferred Alias Processing (default).
NOTE: A “Y” in this position is required to generate a
CASS report.
527
P9I-ABBREV
1
A one-character code indicating Abbreviated Alias
Processing.
• Y — Use Abbreviated Alias Processing.
• N — Do Not Use Abbreviated Alias Processing (default).
528
P9IDPV-FTI
1
A one-character code that allows you to specify the DPV
file to match against:
• Blank — Process the DPV split file.
• S — Process the DPV split file.
• F — Process the DPV flat file.
• H — Process the DPV full (hash) file.
529-530
P9IDPB2
2
Two characters for the DPBC input add on.
531
P9I-CASSOK
1
A one-character code that indicates whether a valid CASS
configuration is intended.
• N — Force non-CASS configuration
• Y — CASS configuration (default).
412
Software Release 4.0.0/March 2015
The Input Call Area (P9IN)
9
Table 2: Input Call Area (P9IN) (Part 9 of 9)
Position
532
Name
P9IDPV-MMS
Length
1
Contents
Controls the DPV memory module size to use for
processing.
• Blank — DPV process will be using Medium memory
model (default).
• 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).
533
P9ILACS-MMS
1
Controls the LACS memory module size to use for
processing.
• Blank — LACS process will be using Medium memory
model (default).
• 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).
534
P9ISEASONAL
1
Code indicating if CODE-1 Plus should retrieve and return
seasonal delivery flags:
• Y — Retrieve and return seasonal delivery flags.
NOTE: Any value other than Y will not retrieve seasonal
flags.
535-600
Reserved
Working With CODE-1 Plus
66
413
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
The Output Results Call Area (P9OUT)
The following table is a map of the 5,000-byte P9OUT output call area. You should
initialize this area to blank spaces before your first call to C1MATCHx.
When C1MATCHx processing does not find a valid match for an address:
1. The address is sent for LACSLink processing.
2. If LACSLink finds that the address is convertible, the LACSLink converted address
is written back to the P9IAD1 field.
3. The P9IAD2 field is filled with blank spaces.
4. The LACSLink converted address in the P9IAD1 field is sent back through
C1MATCHx processing for another matching attempt.
NOTE: The output parsed A1 elements will not be blank when an address has been
LACSLink converted.
414
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 1 of 28)
Position
1
Name
P9OGRC
Length
1
Contents
A one-character code indicating the success or reason
for failure of the address-match attempt:
• Blank — The address-match attempt was
successful.
• A — Apartment number missing or not found in
database, and an apartment-level match was
required.
• B — Insufficient (or blank) address information for
a match.
• C — Critical error (CICS and IMS only).
• E — External match—auxiliary file processing.
• H — House/Box number not found on street.
• M — Multiple address matches were found.
• S — Street name not found in ZIP Code.
• X — Database access issue. One example of a
database access issue would be that the database
has expired. This value may also indicate a license
issue.
• Z — ZIP Code not found in database.
2
P9OPRB
1
A one-character code indicating the (relative)
probable correctness of the overall match that was
found:
• Blank — No match was found.
• 0 — The match is most likely correct.
• 1-8 — These values represent intermediate values
on a sliding scale.
• 9 — The match is least likely to be correct.
NOTE: These values reflect the program's estimate of
“relative probable correctness” only; it is possible that
some matches given a score of 0 are not correct, and
probable that matches given a score of 9 are
nevertheless correct.
3
P9OSSC
Working With CODE-1 Plus
1
A 1-digit score, on a scale of 0 - 9, reflecting the
closeness of the street-name match (after
transformations by the analyzer, if any), where 0
indicates an exact match and 9 indicates the least
likely match. If no match was found, this field is blank.
415
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 2 of 28)
Position
4
Name
P9ODRC
Length
1
Contents
A 1-character code indicating the result of the
directional match, as follows:
• Blank — No address match, or directional (or lack
thereof) matches the database.
• D — The directional does not match the database at
all.
• F — The complete directional does not match the
database, but its first character does (for example,
N versus NW).
• N — No directional was found on the input address,
but a directional was present on the database.
5
P9OSRC
1
A 1-character code indicating the result of the suffix
match:
• Blank — No address match or suffix (or lack
thereof) matches the database.
• N — No suffix was found on the input address, but a
suffix was present on the database.
• S — The suffix does not match the database.
6
P9OARC
1
A 1-character code indicating the result of the
apartment match:
• Blank — No address match or apartment (or lack
thereof) matches the database.
• A — The apartment does not match the database.
• F — Apartment appended because of firm name
match.
• N — No apartment was found on the input address,
but an apartment was present on the database at
the street address.
7-10
P9O-LB-AM
4
The number of attempts required to match the
address. The number will be right-justified, with
leading blanks.
11
P9OAPR
1
A 1-character code indicating whether an apartment
number was detected in the input address:
• Y — An apartment number was detected in the
input address.
• N — No apartment number was detected in the
input address.
416
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 3 of 28)
Position
12
Name
P9OPRA
Length
1
Contents
A 1-character code indicating the (relative) probable
correctness of the address match (only):
• 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.
NOTE: These values reflect the program's estimate of
“relative probable correctness” only; it is possible that
some matches given a score of 0 are not correct, and
probable that most matches given a score of 9 are
nevertheless correct.
13
P9OFRC
1
A 1-character code indicating the result of the firm
name match:
• Blank — No address match or firm name matches,
or no firm name is present on the input.
• F — The input firm name does not match the
database.
• M — An input firm name was present, but there
were no firm names on the database for the
matched address.
14
P9OFSC
1
A 1-digit score, on a scale of 0 - 9, reflecting the
closeness of the firm-name match, where 0 indicates
an exact match and 9 indicates the least likely match.
If no (firm) match was obtained, this field will be blank.
15
P9OSMA
1
A 1-character code reflecting the source of the
matched address:
• Blank — No match was found.
• M — The matched address was synthesized from
information in both the primary and secondary
address lines.
• P — The matched address was taken from the
primary address line.
• S — The matched address was taken from the
secondary address line.
Working With CODE-1 Plus
417
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 4 of 28)
Position
16
Name
P9ODIT
Length
1
Contents
A 1-character code indicating which type of
information, if any, was dropped in order to get
the match:
• 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 — RR/HC or PO Box information was dropped in
order to obtain a street address match.
• W — One or more characters were dropped during
the address parsing process. These characters are
placed in positions 201-300 and/or 401-500
described below.
17
P9ODFR
1
A 1-character code indicating whether or not a default
record was matched:
• Blank — Record matched was not default record, or
no match was obtained.
• H — Highrise default.
• M — Military default.
• R — Rural Route default.
• S — Street default.
18
P9OALT-ADDR
1
A 1-character code indicating the alternate
addressing scheme:
• Blank — No alternate address scheme used.
• D — Delivery point alternate logic used.
• E — Enhanced Highrise Alternate Match logic used.
• S — Small town default logic used.
• U — Unique ZIP Code logic used.
19
P9OSCM
1
A 1-character return code indicating multiple
secondary component matching:
• Blank — Multiple secondary component logic not
used.
• E — Exact match to secondary component.
• S — Multiple secondary component logic used.
20
P9OALT
1
A 1-character code indicating whether the input
record was matched to a base ZIP+4 record or an
alternate ZIP+4 record.
• A — An alternate ZIP+4 record was matched.
• B — A base ZIP+4 record was matched.
418
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 5 of 28)
Position
21
Name
P9O9RC
Length
1
Contents
A 1-character code reflecting the success or reason
for failure of the ZIP+4 coding attempt:
• Blank — The address-match attempt was
successful.
• 7 — ZIP + 4 matched to a Carrier Route R777
(phantom) and was suppressed.
• A — An apartment number was missing or not
found in the database, and an apartment-level
match was required.
• B — Insufficient (or blank) address information for
a match.
• H — House/Box number not found on street.
• M — Multiple matches of equal quality were found.
• S — Street name was not found in the ZIP Code.
• U — Unavailable—auxiliary file processing.
• V — Record matched a non-deliverable 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 was not found in the database.
22
P9OCRC
1
A 1-character code reflecting the success or reason
for failure of the carrier route coding attempt:
• Blank — The address-match attempt was
successful.
• A — An apartment number was missing or not
found in the database, and an apartment-level
match was required.
• B — Insufficient (or blank) address information for
a match.
• H — House/Box number not found on street.
• M — Multiple matches of equal quality were found.
• N — Carrier Route coding not attempted - auxiliary
processing.
• S — Street name was not found in the ZIP Code.
• U — Unavailable—auxiliary file processing.
• Z — ZIP Code was not found in the database.
23
P9OOGER-N
Working With CODE-1 Plus
1
For internal use only.
419
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 6 of 28)
Position
24
Name
P9OCIT
Length
1
Contents
A 1-character code indicating whether or not the input
city name was standardized:
• Blank — No match, or the input city name was the
same as either the long or short city name returned
in fields P9OCTL and P9OCTS.
• C — The input city name was standardized to the
long or short city name returned in fields P9OCTL
and P9OCTS.
• I — Input city name was identical to short city name.
25
P9OSAB
1
A 1-character code indicating whether or not the input
state was standardized:
• Blank — No match, or the input state name was the
same as the state name returned in the P9OSTA
field.
• S — The state abbreviation was standardized to the
value returned in the P9OSTA field.
26
P9OURC
1
A 1-character code reflecting the urbanization name
match attempt:
• Blank — No urbanization name match, or
urbanization name matches, or no urbanization is
present on the input.
• M — Multiple matches were found.
27
P9ONTP
1
A 1-character code indicating the matched alias street
name type.
• Blank — Street record matched was not an alias
street.
• A — Street record was abbreviated.
• 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.
420
28
P9ODPC
1
The check-digit for the 11-digit delivery point barcode
(DPBC).
29-34
P9ODPBC
6
The delivery point barcode (DPBC) determined for the
input address, or blanks if none could be determined.
The ZIP+4 Code can be taken from the first four
characters of this field.
35-38
P9OCRT
4
The carrier route code, in Cnnn format, determined
for the input address; this field is blank if no match
could be obtained.
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 7 of 28)
Position
39
Name
P9ORTP
Length
1
Contents
The USPS Record Type of the ZIP+4 record that was
matched. If no match could be obtained, this field is
blank. Otherwise, the field will contain one of the
following record types:
• Blank — No match found.
• F — Firm record
• G — General delivery record
• H — High Rise (apartment complex) record
• P — Post office box record
• R — Rural Route or Highway Contract record
• S — Normal street address record
NOTE: Electing to store the record type will produce a
non-CASS-certified configuration. No USPS Form
3553 will be generated.
40
P9OSNA
1
The alias return code. The field will contain one of the
following codes:
• Blank — The record matched a base street name.
• A — The record matched an alias street name.
41
P9OLACS
1
The matched address Locatable Address Correction
Service (LACS) indicator. The field will contain one of
the following codes:
• L — The record was LACS converted and moved to
an urban address.
• Blank — The record was not LACS converted and
did not move to an urban address.
42
P9OAUX-M
1
A 1-character code indicating the auxiliary file match:
• Blank — Non-match.
• 1 — Early Warning System (EWS) File.
43
P9ODPV-RC
1
A 1-character code indicating the type of match to the
Delivery Point Validation file:
• Blank — not attempted or processing successful.
• E — Expired database.
• F — Open/Read failure on DPV database.
• V — Software not compatible with ZIP + 4 software.
• S — Seed record encountered.
• X — DPV software/database incompatible.
Working With CODE-1 Plus
421
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 8 of 28)
Position
44
Name
P9ODPV
Length
1
Contents
DPV Confirmation Indicator:
• Blank — Not presented.
• D — Valid primary; input missing secondary
(primary rural route).
• M — Unable to DPV confirm multiple condition.
• N — No Delivery Point Validation.
• S — Valid primary; however, secondary (primary for
rural route) and/or single trailing alpha present
and is not confirmed.
• Y — Delivery Point Validated. Primary valid and
secondary number (when present) valid.
45
P9ODPVC
1
DPV CMRA (Commercial Mail Receiving Agency)
Indicator:
• Blank — Not presented.
• Y — Yes CMRA.
• N — Not CMRA.
46
P9ODPVF
1
DPV False/Positive Indicator:
• Blank — Not presented.
• Y — False.
• N — Not false.
422
47-48
P9OSWM
2
Indicates the modification level of the matching
program C1MATCHx.
49-52
P9OSWV
4
Indicates the release number of the matching
program C1MATCHx.
53-62
P9OSWD
10
Indicates the date on which the matching program
was installed.
63-82
P9ODBV
20
Identifies the version of the CODE-1 Plus database
used to obtain matches.
83-102
P9OCSV
20
Identifies the software used to create the CODE-1 Plus
database.
103-302
Reserved
200
Filler
303-402
P9OCO1
100
The 100-byte output area returned by C1ANZADR
containing “care of” data dropped from the primary
address line. This field will be cased if there is a value
of “C” in P9ICASE.
403-602
Reserved
200
Filler
603-702
P9OCO2
100
The 100-byte output area returned by C1ANZADR
containing “care of” data dropped from the secondary
address line. This field will be cased if there is a value
of “C” in P9ICASE.
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 9 of 28)
Position
Name
Length
Contents
703-704
P9OSAL
2
The length of the standardized address string in the
P9OSAD field.
705-802
P9OSAD
98
Contains the complete standardized address,
including apartment information. This field will be
cased if there is a value of “C” in P9ICASE.
The following fields contain isolated elements of the standardized address, as noted.
803-812
P9OHS-LB
10
The house number.
813-814
P9ODI1
2
The leading directional.
815-842
P9OSTR
28
The street name. This field will be cased if there is a
value of “C” in P9ICASE.
843-846
P9OSFX
4
The street suffix. This field will be cased if there is a
value of “C” in P9ICASE.
847-848
P9ODI2
2
The trailing directional.
849-887
P9OSTN
39
The complete street name (a combination of fields
P9ODI1-P9ODI2, above). This field will be cased if
there is a value of “C” in P9ICASE.
888-937
P9OSTH
50
The street address, without apartment information.
This field will be cased if there is a value of “C” in
P9ICASE.
938-941
P9OATP
4
The apartment designator. This field will be cased if
there is a value of “C” in P9ICASE.
942-949
P9OAP-LB
8
The apartment number.
950-962
P9OAT-LB
13
The apartment number, preceded by the apartment
designator, if required. This field will be cased if there
is a value of “C” in P9ICASE.
963-968
P9ORR-LB
6
The rural route or highway contract number extracted
from the matched address, in the standard USPS form
(RR1, for example).
969-978
P9ORB-LB
10
The box number associated with the RR or HC route in
field P9ORR-LB.
979-988
P9OBX-LB
10
The post office box number.
989-990
P9OSAL-BASE
2
The number of bytes used for the base address
information.
9911088
P9OSAD-BASE
98
The base address information. This field will be cased
if there is a value of “C” in P9ICASE.
10891090
P9ODI1-BASE
2
The base leading directional.
Working With CODE-1 Plus
423
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 10 of 28)
Position
Name
Length
Contents
10911118
P9OSTR-BASE
28
The base street name. This field will be cased if there
is a value of “C” in P9ICASE.
11191122
P9OSFX-BASE
4
The base street suffix. This field will be cased if there
is a value of “C” in P9ICASE.
11231124
P9ODI2-BASE
2
The base trailing directional.
11251163
P9OSTN-BASE
39
The base complete street. This field will be cased if
there is a value of “C” in P9ICASE.
11641213
P9OSTH-BASE
50
The base address without apartment information. This
field will be cased if there is a value of “C” in P9ICASE.
1214
P9OCITY-TYPE-IN
1
A 1-character code indicating the input city type:
• P — Primary city name
• S — Secondary city name
• V — Vanity city name.
1215
P9OLACSLINK-IND
1
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.
12161217
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.
424
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 11 of 28)
Position
12181226
Name
P9OLACSLINK-DBINFO
Length
9
Contents
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.
12271239
P9OLACSLINKVERSION
13
Version number of the LACSLink database.
12401244
P9ODPV-DB-TY
5
A 5-character code indicating the DPV database type.
• FLAT — Indicates a DPV flat file.
• SPLIT — Indicates a DPV split file.
• FULL — Indicates a DPV full file.
1245
P9OVALID-ZIP
1
A 1-character code indicating the ZIP Code status.
• Y — Valid ZIP Code.
• N — Invalid ZIP Code.
1246
P9ODPV-PBSA
1
A 1-character code indicating whether a P. O. Box
Street Address (PBSA) was found.
• Y — PBSA found.
• N — No PBSA found.
1247
P9OPOBZIP
1
A 1-character code indicating whether this is a P. O.
Box only ZIP Code.
• Y — P. O. Box only ZIP Code.
• Blank — Not P. O. Box only ZIP Code.
12481259
P9OSEASONAL
12
A 12-byte code indicating when mail can be delivered
to a specific address.
1260
P9ODPV-VACT
1
A 1-character code indicating the presence of a DPV
vacant address.
• Blank — Not presented.
• Y — Vacant address.
• N — Not vacant address.
Working With CODE-1 Plus
425
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 12 of 28)
Position
1261
Name
P9ODPV-NOST
Length
1
Contents
A 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.
1262
P9ORDI
1
A 1-character code indicating the type of match to the
Residential Delivery Indicator (RDI) file:
• Blank — Not presented
• M — MIxed Residential/Business
• B — Business only
• R — Residential
1263
P9ORDI-RC
1
A 1-character code identifying the success or failure
of RDI processing:
• Blank — Not attempted or processing successful
• E — Expired database
• F — Open/Read failure
• V — Software not compatible with ZIP+4 software
• S — Executing DPV040 — Table(s) > 8 MB
1264
P9OSAR
1
A 1-character code indicating the success or reason
for failure of the standardized address match attempt:
• Blank — The address match attempt was
successful.
• A — Apartment number missing or not found in
database, and an apartment-level match was
required.
• B — Insufficient (or blank) address information for
a match.
• H — House/Box number not found on street.
• M — Multiple matches were found of equal quality.
• S — Street name not found in ZIP Code.
• U — Unavailable—auxiliary file processing.
• Z — ZIP Code not found in database.
1265
P9OD1R
1
A 1-character code indicating whether multiple values
were found for the leading directional segment of the
standardized address:
• Blank — Only one value was found.
• M — Multiple values were found.
426
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 13 of 28)
Position
1266
Name
P9OSNR
Length
1
Contents
A 1-character field indicating whether multiple values
were found for the root street name:
• Blank — Only one value was found.
• M — Multiple values were found.
1267
P9OSFR
1
A 1-character field indicating whether multiple values
were found for the street suffix:
• Blank — Only one value was found.
• M — Multiple values were found.
1268
P9OD2R
1
A 1-character field indicating whether multiple values
were found for the trailing directional:
• Blank — Only one value was found.
• M — Multiple values were found.
12691270
P9OFRM-LN
2
The length of the standardized firm name.
12711310
P9OFRM
40
The standardized firm name. This field will be cased if
there is a value of “C” in P9ICASE.
The following A1 elements pertain to the input primary address.
NOTE: The output parsed A1 elements will not be blank for addresses that have been LACSLinkconverted.
13111320
HOUSE-NR
10
The left-justified, primary normalized house number.
13211322
P9O-A1-PRE-DIR
2
The normalized pre-directional indicator.
13231367
P9O-A1-STREET-NAME
45
The normalized street name, which is any information
that remains after the address is matched. This field
will be cased if there is a value of “C” in P9ICASE.
13681371
P9O-A1-SUFFIX
4
The normalized street suffix. This field will be cased if
there is a value of “C” in P9ICASE.
13721373
P9O-A1-POST-DIR
2
The normalized post directional indicator.
13741377
P9O-A1-APT-TYPE
4
The normalized apartment type (designator). This field
will be cased if there is a value of “C” in P9ICASE.
13781385
P9O-A1-APT-NR
8
The left-justified, normalized apartment string.
Working With CODE-1 Plus
427
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 14 of 28)
Position
13861387
Name
P9O-A1-RR-TYPE
Length
2
Contents
A 2- character code indicating the normalized rural
route/highway contract type. One of the following
codes is stored:
• Blank — No type was stored.
• HC — The address contains a highway contact
number.
• RR — The address contains a rural route number.
13881390
P9O-A1-RRT-NR
3
The normalized rural route number, rural route/
highway contract number.
13911400
P9O-A1-BOX-NR
10
The left-justified, normalized box number.
14011404
P9O-A1-PMB-D
4
The left-justified Private Mailbox (PMB) Designator.
14051420
P9O-A1-PMB-NR
16
The left-justified Private Mailbox (PMB) Number.
14211422
P9O-A1-STREET-LEN
2
The normalized length of the street name.
14231443
Reserved
21
1444
P9O-A1-STD-PRE-DIR
1
A 1-character pre-directional standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1445
P9O-A1-STD-SUFFIX
1
A 1-character suffix standard format indicator. One of
the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1446
P9O-A1-STD-POST-DIR
1
A 1-character post-directional standard format
indicator. One of the following codes is stored:
• Blank —
element was not present in the input.
The
• N — The input was in a non-standard format.
• S — The input is in a standard format.
428
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 15 of 28)
Position
1447
Name
P9O-A1-STD-RR-TYPE
Length
1
Contents
A 1-character rural route/highway contract type
standard format indicator. One of the following codes
is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1448
P9O-A1-STD-GD
1
A 1-character general delivery standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1449
P9OP9O-A1-STD-APTTYPE
1
A 1-character apartment type standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1450
P9O-A1-STD-PMB
1
A 1-character PMB type standard format indicator.
One of the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1451
P9O-A1-STD-BOX
1
A 1-character box number type standard format
indicator. One of the following codes is stored:
• Blank — There was no box number.
• B — Input was a box number.
• N — Input was present, but was neither a box or
Post Office Box.
• P — Input was a Post Office Box.
14521460
Reserved
9
The following A2 elements pertain to the input secondary address:
14611470
P9O-A2-HOUSE-NR
10
The left-justified, normalized house number.
14711472
P9O-A2-PRE-DIR
2
The normalized pre-directional indicator.
14731517
P9O-A2-STREET-NAME
45
The normalized street name, which is any information
that remains after the address is matched. This field
will be cased if there is a value of “C” in P9ICASE.
15181521
P9O-A2-SUFFIX
4
The normalized street suffix. This field will be cased if
there is a value of “C” in P9ICASE.
Working With CODE-1 Plus
429
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 16 of 28)
Position
Name
Length
Contents
15221523
P9O-A2-POST-DIR
2
The normalized post directional indicator.
15241527
P9O-A2-APT-TYPE
4
The normalized apartment type (designator).
15281535
P9O-A2-APT-NR
8
The left-justified, normalized apartment string.
15361537
P9O-A2-RR-TYPE
2
A 2-character code indicating the normalized rural
route/highway contract type. One of the following
codes is stored:
• Blank — No type was stored.
• HC — The address contains a highway contact
number.
• RR — The address contains a rural route number.
15381540
P9O-A2-RRT-NR
3
The left-justified, normalized rural route number,
rural route/highway contract number.
15411550
P9O-A2-BOX NR
10
The left-justified, normalized box number.
15511554
P9O-A2-PMB-D
4
The left-justified Private Mailbox (PMB) Designator.
15551570
P9O-A2-PMB-NR
16
The left-justified Private Mailbox (PMB) Number.
15711572
P9O-A2-STREET-LEN
2
The normalized length of the street name.
15731593
Reserved
21
1594
P9O-A2-STD-PRE-DIR
1
A 1-character pre-directional standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1595
P9O-A2-STD-SUFFIX
1
A 1-character suffix standard format indicator. One of
the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
430
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 17 of 28)
Position
1596
Name
P9O-A2-STD-POST-DIR
Length
1
Contents
A 1-character post-directional standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1597
P9O-A2-STD-RR-TYPE
1
A 1-character rural route/highway contract type
standard format indicator. One of the following codes
is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1598
P9O-A2-STD-GD
1
A 1-character general delivery standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1599
P9O-A2-STD-APT-TYPE
1
A 1-character apartment type standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1600
P9O-A2-STD-PMB
1
A 1-character Private Mailbox (PMB) standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
1601
P9O-A2-STD-BOX
1
A 1-character box number type standard format
indicator. One of the following codes is stored:
• Blank — There was no box number.
• B — Input was a box number.
• N — Input was present, but was neither a box or
Post Office Box.
• P — Input was a Post Office Box.
16021610
Reserved
9
16111620
P9OPRG-LOW
10
The low primary range for the matching address.
16211630
P9OPRG-HIGH
10
The high primary range for the matching address.
Working With CODE-1 Plus
431
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 18 of 28)
Position
Name
Length
Contents
1631
P9OPRG-PARITY
1
The primary odd/even indicator for the matching
address.
16321639
P9OSRG-LOW
8
The low secondary range for the matching address.
16401647
P9OSRG-HIGH
8
The high secondary range for the matching address.
1648
P9OSRG-PARITY
1
The secondary odd/even indicator for the matching
address.
1649
P9O5RC
1
A 1-character code indicating the success or reason
for failure of the ZIP Code to be corrected:
• Blank — The match attempt was successful.
• A — Apartment number missing or not found on
database, and an apartment-level match was
required.
• B — Insufficient (or blank) address match
information.
• E — External match—auxiliary file processing.
• H — House/Box number was not found on street
• M — Multiple ZIP matches were found of equal
quality.
• S — Street name not found in ZIP Code.
• Z — ZIP Code was not found on database.
16501651
P9O-LB-ZL
2
The number of best-fit ZIP Codes found. If the number
is less than 10, the left-most character is blank.
1652
P9OICR
1
A 1-character code indicating the city match condition
which resulted when the input city name was used to
find a locality:
• Blank — Match successful.
• B — No input city could be found.
• C — No match could be found for the input city/
state.
• N — No locality attempt was made.
432
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 19 of 28)
Position
1653
Name
P9OOCR
Length
1
Contents
A 1-character code indicating the success or reason
for failure of the final output city match attempt (trying
to find the right city name for the ZIP Code
determined):
• Blank — Input city/state matched.
• N — Not used.
• B — Input City is blank (could not be found).
• C — City/state mismatch.
• I — Input used, no cities available for ZIP.
• S — Spelling error(s) in input were corrected.
NOTE: For certain large cities (for example, New
York), C1P extrapolates the state if only the city is
provided on the input.
1654
P9OCAO
1
A 1-character code specifying the status of the output
ZIP Code field, P9OCZP:
• A — P9OCZP contains a ZIP Code other than the
original, due to the address match found.
• B — P9OCZP contains blanks; no match was
available, and the original ZIP Code was blank.
• C — P9OCZP contains the original ZIP Code, which
was confirmed by address match.
• I — P9OCZP contains blanks; no match was
available, and the original ZIP Code was invalid.
• O — P9OCZP contains the original ZIP Code,
because no address match was found.
• U — P9OCZP contains the original ZIP Code. The
original ZIP Code was unique and did not
correspond to the input city/state.
1655
P9OOVC
1
ZIP+4 Override City Name Indicator:
• Blank — Not stored.
• O — ZIP+4 Override City Name Stored.
1656
P9OSFZ
1
A 1-character code reflecting the source of the final
ZIP Code:
• B — No ZIP Code was determined.
• M — The final ZIP Code was based on a match to the
USPS ZIPMOVE database.
• F — The final ZIP Code was determined from the
finance number locality.
• Z — The original ZIP Code was retained.
Working With CODE-1 Plus
433
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 20 of 28)
Position
1657
Name
P9OOZA
Length
1
Contents
A 1-character code indicating the results of the match
attempt in the original ZIP Code (only):
• Blank — Not attempted.
• I — Attempted, improved (a match was obtained).
• N — Attempted, no match found.
1658
P9OCBA
1
A 1-character code indicating the results of the match
attempt in the city-based locality:
• Blank — Not attempted.
• I — Attempted, improved (a match was obtained).
• N — Attempted, no match found.
1659
P9OFBA
1
A 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 obtained).
• N — Attempted, no match found.
16601679
P9OFNT-DPV-GRP
20
A 20-byte area to accommodate DPV footnote codes.
• AA — Input address matched to the ZIP+4 file.
• A1 — Input address not matched to the ZIP+4 file.
• BB — Input address matched to DPV (all
components).
• CC — Input address primary number matched to
DPV but secondary number not match (present but
not valid).
• F1 — Input address is military; DPV bypassed.
• G1 — Input address is general delivery; DPV
bypassed.
• M1 — Input address primary number missing.
• M3 — Input address primary number invalid.
• N1 — Input address primary number matched to
DPV but high rise address missing secondary
number.
• P1 — Input address missing RR or HC Box number.
• P3 — Input address missing PO, RR, or HC Box
number.
• PB — Input address is a P. O. Box Street Address
(PBSA).
• RR — Input address matched to CMRA.
• R1 — Input address matched to CMRA but
secondary number not present.
• R7 — Input address matched to phantom Carrier
Route R777 (not eligible for street delivery).
• U1 — Input address is unique ZIP; DPV bypassed.
434
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 21 of 28)
Position
16801681
Name
P9OLIA-RC
Length
2
Contents
License Management Return Code:
• Blank — Successful
• F1 — License File Not Found
• F2 — Client Record Missing
• F9 — Unknown Function Requested
• GI — Generic I/O Failed
16821683
P9OLIA-STATUS-RC
2
License Management Status Code:
• Blank — Product/Key Combination is Good
• XX — Product/Key Combination is Not Good
1684
P9OLIA-KEY-STATUS
1
License Management Product Key Status:
• Blank — Product/key combination is good
• B — Product key is marked bad
• N — Product key not found
• S — License ID does not match system
• X — Product key expired
16851686
Reserved
2
1687
P9OCSS
1
A 1-character code indicating the status of city/state
information in the following output fields: P9OCL9,
P9OCS9, P9OCTL, P9OCTS, and P9OSTA.
• Blank — No information available.
• M — Fields populated based upon match to
database.
• Z — No match to database; based upon input ZIP
Code.
16881693
P9OFIN
6
The USPS finance number from the output matched
city.
16941699
P9OLLN
6
The USPS last line number from the matched ZIP+4
record.
17001719
P9OZ-GRP
20
The first four additional ZIP Codes found, (that is, in
addition to the ZIP Code returned in field P9OCZP
below) if multiple ZIP matches were obtained. Each
ZIP Code is presented as a 5-digit number. If fewer
than five ZIP Code matches were obtained, the unused
fields contain zeros.
17201724
P9OCZP
5
Final ZIP Code, as best as it could be determined. This
field will be blank if no ZIP Code could be determined
and the original ZIP Code was invalid.
17251767
P9OCL9
43
Standardized City/State/ZIP+4 line, constructed using
the long (28-byte maximum) city name. This field will
be cased if there is a value of “C” in P9ICASE.
Working With CODE-1 Plus
435
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 22 of 28)
Position
Name
Length
Contents
17681795
P9OCS9
28
Standardized City/State/ZIP+4 line, constructed using
the short (13-byte maximum) city name. This field will
be cased if there is a value of “C” in P9ICASE.
17961823
P9OCTL
28
The long city name. This field will be cased if there is
a value of “C” in P9ICASE.
18241836
P9OCTS
13
The short city name. This field will be cased if there is
a value of “C” in P9ICASE.
18371838
P9OSTA
2
The USPS standard state abbreviation.
1839
P9OCITY-TYPE
1
The USPS standardized city name type:
• P — Primary. Preferred mailing name (the USPS
last line name).
• S — Secondary. Allowable mailing name (not the
USPS last line name).
• V — Vanity. Non-mailing name.
18401859
P90PMB
20
The formatted Private Mailbox (PMB) (from input).
1860
P9OPMB-TYP
1
A 1-character return code indicating the type of
Private Mailbox (PMB):
• S — Standard PMB number.
• N — Non-standard PMB number.
• # — Non-standard, pound sign PMB number.
1861
P9OZIP-CLASS
1
A 1-character code indicating the ZIP classification:
• Blank — Regular ZIP.
• M — Military ZIP.
• P — P.O. Box.
• U — Unique ZIP.
1862
P9OESM-FLAG
1
A 1-character code indicating whether enhanced
street matching (ESM) or All Street Matching (ASM)
processing was performed:
• Blank — No ESM performed.
• A — Matched using All Street Matching (matched
misspelled first letter).
• F — ASM performed but no match found.
• M — Matched using ESM.
• P — ESM performed but no match found.
1863
P9OSTELNK-RC
2
SuiteLink return code:
• A — Business name matched.
• 00 — Business name not matched.
436
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 23 of 28)
Position
1865
Name
P9OSTELNK-MATCHRC
Length
1
Contents
SuiteLink match code:
• A — Matched
• B — Not matched
• C — Business name was all noise
• D — Highrise default record not found
• E — Database is expired.
1866
P9OSTELNK-MATCHFID
1
SuiteLink match fidelity:
• 1 — Exact match
• 2 — Acceptable match (one word not matched)
• 3 — Unacceptable match (more than one word not
matched)
1867
P9OSTELNK-RLS-NUM
12
1879
Reserved
1
1880
P9OLOT-RC
1
SuiteLink release number.
A 1-character character indicating the level of match
obtained against the Line of Travel master file:
• Blank — Invalid input (zero or non-numeric ZIP/
ZIP+4 add-on)
• 9 — 9-digit ZIP+4 match successful
• C — Call to LTO10/LTO10C failed
• D — Unsuccessful 9-digit match, default coded
• F — Open/read failure on Line of Travel master file
• V — Line of Travel matcher software not compatible
with the Line of Travel master file
18811884
P9OLOT-CODE-NUM
4
Numeric portion of Line of Travel code.
1885
P9OLOT-CODE-SEQ
1
A 1-character character indicating USPS Line of
Travel sequence, as follows:
• A — Ascending
• D — Descending
18861887
P90LOT-ALT-SEQ
2
The 2-character alternate alphanumeric sequence
code (A0-T9).
1888
P9OLOT-ALT-HEX
1
The 1-character alternate hexadecimal sequence
code (X’21’ - X’E8’)
Working With CODE-1 Plus
437
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 24 of 28)
Position
1889
Name
P9OXRC
Length
1
Contents
Master file expiration code. One of the following codes
will be in this area:
• Blank — The master file is still “fresh.”
• W — The master file is in the USPS grace period
(60-105 days old). Check P9OMFX for the number of
days left until the end of the grace period.
• B — The master file expiration has been bypassed.
• V — The database and software are incompatible.
• X — The master file has expired (it is over 105 days
old).
18901892
P9OMFX
3
A 3-byte number indicating the number of days left
until the master file expires.
18931902
P9OMFD
10
Expiration date of the master file in MM/DD/YYYY
format.
19031912
P9OMFV
10
Vintage date of the master file in MM/DD/YYYY format.
1913
P9OCASS
1
CODE-1 Plus CASS cycle expiration return code.
• Blank — CODE-1 Plus is certified for the current
CASS cycle.
• C — The CASS cycle that certified this version of
CODE-1 Plus has expired.
1914
P9OEXP
1
Master file expiration return code.
• Blank — Master file is ok (within USPS file lifecycle)
• W — Master file has exceeded its life-cycle and is
within the USPS grace period (check P9OMFX for
days left until the end of the grace period)
• B — Master file expiration bypassed
• X — Master file has expired (grace period
exceeded).
19151924
438
P9OCASS-X-DATE
10
The USPS CASS cycle expiration date. This is the date
that CODE-1 Plus will stop providing a USPS Form
3553 for this CASS cycle. You can bypass this
expiration date.
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 25 of 28)
Position
1925
Name
P9OERR
Length
1
Contents
Represents the database for which an error occurred:
• Blank: unknown
• Z — ZIPIDX
• L — LCLDB
• D — DTLDB
• U or C — CITYDB
• N — COUNTY
• S — C1STRDB
• V — DPVMST
• F — SLKDB
1926
P9OERR-TYPE
1
Represents the operation being attempted:
• C — Close
• O — Open
• R — Read
• N — Record Number
19271928
P9OFST
2
19291934
Reserved
6
19351940
P9ODPV-DB-VINTAGE
6
File status code returned by COBOL.
DPV Database Vintage Date — MMYYYY format:
• P9ODPV-DB-MONTH
2
• P9ODPV-DB-YEAR
4
19411945
P9ODPV-DBSFW
5
Software version used to create DPV file.
19461951
P9ORDI-DB-VINTAGE
6
RDI Database Vintage Date — MMYYYY format:
• P9ORDI-DB-MONTH
2
• P9ORDI-DB-YEAR
4
19521956
P9ORDI-DBSFW
5
Software version used to create RDI file.
19571961
P9ODB-VERS
5
Database vintage for “database incompatible”
condition.
1962
Reserved
1
19631990
P9OURB
28
USPS urbanization name. This field will be cased if
there is a value of “C” in P9ICASE.
19911993
P9OCOUNTY-NR
3
The USPS FIPS county number.
Working With CODE-1 Plus
439
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 26 of 28)
Position
Name
Length
Contents
19942018
P9OCOUNTY
25
The USPS county name. This field will be cased if there
is a value of “C” in P9ICASE.
20192020
P9OCONGRESS
2
The congressional district.
20212120
P9OFNT-GRP
100
Up to 50, 2-character Delivery Sequence Footnotes
(DSF2).
21212150
P9OSTELNK-RLSNAME
30
SuiteLink release name.
21512160
P9OSTELNK-DB-DATE
10
SuiteLink database date (MM/DD/YYYY).
21612170
P9OSTELNK-DB-EXPDATE
10
SuiteLink expiration date (MM/DD/YYYY).
2171
P9OMATAL2-PREFERRC
1
Location on the output record for a 1-byte flag.
• Blank — No preferred alias processing attempted.
• A — Input address matched to an alias (preferred
alias processing is only attempted for base
addresses).
• N — Preferred alias not found for input address.
• Y — Preferred alias found for input address and
used in output standardized address.
2172
P9OMATAL2-ABBREVRC
1
Location on the output record for a 1-byte flag.
• Blank — No abbreviated alias processing
attempted.
• B — Output address set to base address.
• L — Original standardized address length already
<= max.
• N — Abbreviated alias not found for input address.
• Y — Abbreviated alias found for input address and
used in output standardized address.
21732220
Reserved
48
22212222
P9OSTACK-USED
2
Number of entries in address stack.
The following fields (positions 2223-2475) occur 10 times. The previous field, P9OSTACK-USED, indicates the
number of occurrences that are non-blank. Only the first occurrence of each field is listed.
440
2223
P90AS-RC
1
Return code
2224
P9OAS-OPRB
1
Overall probability of correctness
2225
P9OAS-RTP
1
USPS record type
Software Release 4.0.0/March 2015
The Output Results Call Area (P9OUT)
9
Table 3: Output Call Area (P9OUT) (Part 27 of 28)
Position
2226
Name
P90AS-DFR
Length
1
Contents
Code indicating the “default” match:
• H — High Rise Default
• M — Military Default
• R — Rural Route Default
• S — Street Default
• Blank — Not a default record.
22272290
P9OAS-SAD
64
Formatted standard address
22912292
P90AS-SAL
2
Length of standardized address
22932302
P9OAS-PRG-LOW
10
Primary range (low)
23032312
P90AS-PRG-HIGH
10
Primary range (high)
2313
P90AS-PRG-PARITY
1
Primary range parity
23142321
P9OAS-SRG-LOW
8
Secondary range (low)
23222329
P9OAS-SRG-HIGH
8
Secondary range (high)
2330
P9OAS-SRG-PARITY
1
Secondary range parity.
23312370
P9OAS-FIRM
40
Firm name
23712398
P9OAS-CTL
28
Long city name
23992411
P9OAS-CTS
13
Short city name
24122439
P9OAS-URB
28
Puerto Rico Urbanization name
24402441
P9OAS-STA
2
State abbreviation
24422446
P90AS-ZIP
5
ZIP Code
24472450
P90AS-ZP4
4
ZIP+4 Add-on
24512452
P9OAS-DP
2
Delivery point add-on
2453
P90AS-DPC
1
Delivery point check digit
Working With CODE-1 Plus
441
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 3: Output Call Area (P9OUT) (Part 28 of 28)
Position
Name
Length
Contents
24542457
P90AS-CRT
4
Carrier route code
24582460
P90AS-COUNTY
3
County number
24612462
P9OAS-CONGRESS
2
Congressional district
24632468
P9OAS-LL
6
Last line number
24692474
P9OAS-FIN
6
Finance number
2475
P90AS-SCORE
1
Score:
0-9
0 is the best score
Positions 2476-4752 contain the Address Stack return fields for each entry in the address stack.
47535000
442
Reserved
248
Software Release 4.0.0/March 2015
Output Audit Call Area (P9AUDIT)
9
Output Audit Call Area (P9AUDIT)
The following table is a map of the 800-byte Audit call area, which consists of
subfields (counters) that are maintained by C1MATCHx. You must initialize the
P9AUDIT area with blank spaces before your first call to C1MATCHx.
When C1MATCHx is first called, all numeric fields in this area are set to zero.
Thereafter, they are incremented as indicated by the field usage. You can, however,
clear all or some of these fields to zero after each match attempt, so that you can
report on the resource requirements of individual match attempts.
Each counter is a 9-digit packed number occupying 5 bytes, unless otherwise noted.
Table 4: Output Audit Call Area (P9AUDIT)
Positions
Name
Length
Contents
1-5
P9AZPX
5
Database read operations for the ZIP Index file.
6-10
P9ACTX
5
Database read operations for the City Details file.
11-15
P9ALCL
5
Database read operations for the Locality file.
16-20
P9ADTL
5
Database read operations for the Street Details file.
21-25
P9ACNT
5
Database read operations for the County file.
26-30
P9ASTR
5
Database read operations for Street information.
31-85
Reserved
55
86-90
P9ARZPX
5
Database read requests (whether or not an I/O
operation resulted) for the ZIP Index file.
91-95
P9ARCTX
5
Database read requests (whether or not an I/O
operation resulted) for the City Details file.
96-100
P9ARLCL
5
Database read requests (whether or not an I/O
operation resulted) for the Locality file.
101-105
P9ARDTL
5
Database read requests (whether or not an I/O
operation resulted) for the Street Details file.
106-110
P9ARCNT
5
Database read requests (whether or not an I/O
operation resulted) for the County file.
111-115
P9ARSTR
5
Database read operations for Street Name details.
116-800
Reserved
685
Working With CODE-1 Plus
443
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Unmatched Data Call Area (P9INTRF)
A map of the optional 2048-byte P9INTRF unmatched data call area is shown next.
NOTE: You must set P9I-PRM4 to 'Y' to indicate the presence of P9INTRF.
Table 5: Unmatched Data Call Area (P9INTRF)
Positions
Name
Length
Contents
1-100
P9INT-EXTRAADD1
100
Any unmatched data returned by the matcher that was
taken from the primary address line
101-200
P9IINT-EXTRAADD2
100
Any unmatched data returned by the matcher that was
taken from the secondary address line
201-300
P9INT-EXTRADUAL
100
Unmatched/unused portion of a dual address (e.g. 123
MAIN ST PO BOX 456)
301-400
P9INT-EXTRAFRM
100
Unused at this time
401-500
P9INT-EXTRACST
100
Unused at this time
501
P9INT-DUALSOURCE
1
Indicates the source of the dual address line (P9INTEXTRA-DUAL):
502-2048
Reserved
P
Primary input line
S
Secondary input line
1547
CICS Processing
If you are calling CODE-1 Plus under CICS, you must pass one, 01-level call area
which is 6,400 bytes long and encompasses P9IN, P9OUT, and P9AUDIT instead of
passing three individual call areas.
NOTE: P9INTRF is not supported in CICS.
G1CPDMI is provided as a sample program to interface with C1MATCHI under CICS.
Its “2000-SETUP-FUNCTION-RTN” paragraph is almost identical to the area used in
G1CPMAT to link to the interactive matcher. G1CPDMI can be invoked by defining
a CSD transaction entry to it. For example, “G1MI” is assigned in C1PCSD1.
444
Software Release 4.0.0/March 2015
CICS Processing
9
Data can be passed to the program in a comma-delimited string after the transid. If
no data is passed, the program emulates the following string using working storage
variables:
G1MI,4200 PARLIAMENT PL #600,LANHAM,MD,207061882,PITNEY BOWES
The following screen shows the output of G1CPDMI.
Data Returned from CODE-1 Plus NN.N
DATE:
DATABASE EXPIRES:
TIME:HH:MM:SS
DATABASE VINTAGE:
REQUEST:
** INPUT FIELDS **
** RETURNED VALUES **
STREET : 4200 PARLIAMENT PL #600
FIRM : PITNEY BOWES
CTY/ST/ZIP: LANHAM MD
207061882
USPS REC TYPE: F
GEN RETURN CD:
PROB CORRECT : 0
** OUTPUT FIELDS **
FINAL ZIP SRC: Z
STREET : 4200 PARLIAMENT PL STE 600
FIRM : PITNEY BOWES
CTY/ST/ZIP: LANHAM MD 20706-1882
URB/COUNTY:
LAST LINE:
FINANCE #:
Working With CODE-1 Plus
PRINCE GEORGES
V23825
235076
CARRIER #:
ZIP CORR RC:
RANGE PARITY : B
033
C059
445
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
COBOL Call to CICS Version of C1MATCHI
The following is a sample COBOL call to C1MATCHI in a CICS environment.
PROCEDURE DIVISION
.
.
.
MOVE SPACES TO P9COMM-AREA
MOVE ‘I’ TO P9IENV
EXEC CICS LINK
PROGRAM (‘C1MATCHI’)
COMMAREA (P9COMM-AREA)
LENGTH (LENGTH OF P9COMM-AREA)
.
.
.
01 P9COMM-AREA.
NOTE: P9-COMM-AREA is contained in member P9COMM from the sample
library.
NOTE: A value of “C” in P9OGRC indicates a VSAM file access problem. Refer to
the table in the last 50 bytes of P9OUT to resolve the problem. The table contains
five occurs of the file name (8 bytes) with the problem and the EIBRESP value (2
bytes numeric).
IMS Processing
When using C1MATCHx with IMS, in addition to call areas, you must also include
Program Control Blocks (PCB) in your 01-level linkage section. When calling any
matcher module, you must include the CODE-1 Plus database PCBs that are coded in
the PSBs distributed with the CODE-1 Plus IMS system installation/software tape.
The PCB is shown below.
446
Software Release 4.0.0/March 2015
IMS Processing
9
Batch Process PCB List
*-------------------------------------------------------------*
IMS PSB USED WITH THE BATCH IMS PROGRAM C1BM00
*-------------------------------------------------------------*
*
COUNTY DATA BASE
*
PCB
TYPE=DB,NAME=G1CPCNY,PROCOPT=GO,KEYLEN=5
SENSEG NAME=CNYSEG,PARENT=0
*
*
CITY DATA BASE
*
PCB
TYPE=DB,NAME=G1CPCTY,PROCOPT=GO,KEYLEN=2
SENSEG NAME=CTYSEG,PARENT=0
*
*
LOCALITY DETAILS DATA BASE
*
PCB
TYPE=DB,NAME=G1CPDTL,PROCOPT=GO,KEYLEN=2
SENSEG NAME=DTLSEG,PARENT=0
*
*
LOCALITY HEADER DATA BASE
*
PCB
TYPE=DB,NAME=G1CPLCL,PROCOPT=GO,KEYLEN=2
SENSEG NAME=LCLSEG,PARENT=0
*
*
CITY NAME DATA BASE
*
PCB
TYPE=DB,NAME=G1CPCNM,PROCOPT=GO,KEYLEN=4
SENSEG NAME=CNMSEG,PARENT=0
*
*
ZIP INDEX DATA BASE
*
PCB
TYPE=DB,NAME=G1CPZIP,PROCOPT=GO,KEYLEN=1
SENSEG NAME=ZIPSEG,PARENT=0
*
*
LINE OF TRAVEL DATA BASE
*
PCB
TYPE=DB,NAME=G1CPLOT,PROCOPT=GO,KEYLEN=2
SENSEG NAME=LOTSEG,PARENT=0
*
*
AUXILARY DATA BASE
*
PCB
TYPE=DB,NAME=G1C1AUX,PROCOPT=GO,KEYLEN=50
SENSEG NAME=AUXCSEG,PARENT=0
*
*
LICENSE MANAGEMENT DATA BASE
*
PCB
TYPE=DB,NAME=G1LICEN,PROCOPT=A,KEYLEN=23
SENSEG NAME=LMSSEG,PARENT=0
*
*
DELIVERY POINT VALIDATION (DPV) DATA BASE
*
PCB
TYPE=DB,NAME=G1DPVDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
*
DELIVERY POINT VALIDATION SPLIT (DPVS) DATA BASE
*
Working With CODE-1 Plus
447
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
PCB
TYPE=DB,NAME=G1DPVSDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
DELIVERY POINT VALIDATION HASH/FULL(DPVH) DATA BASE
PCB
TYPE=DB,NAME=G1DPVHDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
RESIDENTIAL DELIVERY INDICATOR DATA BASE
PCB
TYPE=DB,NAME=G1CPRDI,PROCOPT=GO,KEYLEN=2
SENSEG NAME=RDISEG,PARENT=0
*
*
*
MATCHER STREET POINTER DATA BASE
PCB
TYPE=DB,NAME=G1CPSTR,PROCOPT=GO,KEYLEN=2
SENSEG NAME=STRSEG,PARENT=0
*
*
*
SUITELINK DATA BASE
PCB
TYPE=DB,NAME=G1SLKDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
LACSLINK DATA BASE
PCB
TYPE=DB,NAME=G1LLKDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
LACSLINK SECURITY DATA BASE
PCB
TYPE=DB,NAME=G1CPSUD,PROCOPT=GR,KEYLEN=7
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
LACSLINK KEY DATA BASE
PCB
TYPE=DB,NAME=G1CPLKY,PROCOPT=GR,KEYLEN=19
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
ABBREVIATED AND PREFERRED ALIAS DATA BASE #1
PCB
TYPE=DB,NAME=C1PALA,PROCOPT=GO,KEYLEN=5
SENSEG NAME=AL2SEG,PARENT=0
*
*
*
ABBREVIATED AND PREFERRED ALIAS DATA BASE #2
PCB
TYPE=DB,NAME=C1PALP,PROCOPT=GO,KEYLEN=5
SENSEG NAME=AL2SEG,PARENT=0
*
*
*
GEO MASTER DATA BASE
PCB
TYPE=DB,NAME=GCMASTER,PROCOPT=GO,KEYLEN=3
SENSEG NAME=GCMAST,PARENT=0
*
*
*
GEO ZIP+4 MASTER DATA BASE
PCB
TYPE=DB,NAME=GCZ4MAST,PROCOPT=GO,KEYLEN=3
SENSEG NAME=GCZ4MAST,PARENT=0
*
448
Software Release 4.0.0/March 2015
IMS Processing
*
*
9
GEO ROOF TOP MASTER DATA BASE
PCB
TYPE=DB,NAME=GCZ6MAST,PROCOPT=GO,KEYLEN=3
SENSEG NAME=GCZ6MAST,PARENT=0
*
*
*
GEO TAX MASTER DATA BASE
PCB
TYPE=DB,NAME=GTMASTR,PROCOPT=GO,KEYLEN=40
SENSEG NAME=VTSEG,PARENT=0
*
*
*
GEO TAX SECONDARY INDEX DATA BASE (ALTERNATE KEY)
PCB
TYPE=DB,NAME=GTMSTALT,PROCOPT=GO,KEYLEN=34
SENSEG NAME=VTSEG,PARENT=0
*
PSBGEN PSBNAME=C1BM00,LANG=COBOL,CMPAT=YES
END
COBOL Call to IMS Version of C1MATCHx
The following is a sample COBOL call to the IMS version of C1MATCHx:
(C1MATCHB, C1MATCHS, C1MATCHM, C1MATCHL, C1MATCHH).
NOTE: You must set P9I-PRM4 to “Y” to indicate the presence of P9INTRF.
CALL WS-C1MATCHx USING P9IN
P9OUT
P9AUDT
P9INTRF
G1CPCNY-PCB
G1CPCTY-PCB
G1CPDTL-PCB
G1CPLCL-PCB
G1CPCNM-PCB
G1CPZIP-PCB
G1CPLOT-PCB
G1C1AUX-PCB
G1LICEN-PCB
G1DPVDB-PCB
G1DPVSDB-PCB
G1DPVHDB-PCB
G1CPRDI-PCB
G1CPSTR-PCB
G1SLKDB-PCB
G1LLKDB-PCB
G1CPSUD-PCB
G1CPLKY-PCB
G1CPALA-PCB
G1CPALP-PCB
Working With CODE-1 Plus
449
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Interactive Process PCB List
*-------------------------------------------------------------*
IMS PSB USED WITH THE ON-LINE IMS PROGRAM G1CPC10
*-------------------------------------------------------------*
*
ALTERNATE PCB USED FOR MSG SWITCH, ERROR MSGS, ETC.
*
PCB
TYPE=TP,MODIFY=YES
*
*
COUNTY DATA BASE
*
PCB
TYPE=DB,NAME=G1CPCNY,PROCOPT=GO,KEYLEN=5
SENSEG NAME=CNYSEG,PARENT=0
*
*
CITY DATA BASE
*
PCB
TYPE=DB,NAME=G1CPCTY,PROCOPT=GO,KEYLEN=2
SENSEG NAME=CTYSEG,PARENT=0
*
*
LOCALITY DETAILS DATA BASE
*
PCB
TYPE=DB,NAME=G1CPDTL,PROCOPT=GO,KEYLEN=2
SENSEG NAME=DTLSEG,PARENT=0
*
*
LOCALITY POINTER DATA BASE
*
PCB
TYPE=DB,NAME=G1CPPTR,PROCOPT=GO,KEYLEN=2
SENSEG NAME=PTRSEG,PARENT=0
*
*
LOCALITY HEADER DATA BASE
*
PCB
TYPE=DB,NAME=G1CPLCL,PROCOPT=GO,KEYLEN=2
SENSEG NAME=LCLSEG,PARENT=0
*
*
CITY NAME DATA BASE
*
PCB
TYPE=DB,NAME=G1CPCNM,PROCOPT=GO,KEYLEN=4
SENSEG NAME=CNMSEG,PARENT=0
*
*
CITY NAME DATA BASE USING
*
SECONDARY INDEX MADE FROM CITY NAME
*
PCB
TYPE=DB,NAME=G1CPCNM,PROCOPT=GO,KEYLEN=32,
PROCSEQ=G1CPXAA
SENSEG NAME=CNMSEG,PARENT=0
*
*
CITY NAME DATA BASE USING
*
SECONDARY INDEX MADE FROM STATE CODE AND CITY NAME
*
PCB
TYPE=DB,NAME=G1CPCNM,PROCOPT=GO,KEYLEN=34,
PROCSEQ=G1CPXAS
SENSEG NAME=CNMSEG,PARENT=0
*
*
ZIP INDEX DATA BASE
*
PCB
TYPE=DB,NAME=G1CPZIP,PROCOPT=GO,KEYLEN=1
SENSEG NAME=ZIPSEG,PARENT=0
450
X
X
Software Release 4.0.0/March 2015
IMS Processing
*
*
*
9
LINE OF TRAVEL DATA BASE
PCB
TYPE=DB,NAME=G1CPLOT,PROCOPT=GO,KEYLEN=2
SENSEG NAME=LOTSEG,PARENT=0
*
*
*
COMM AREA (TEMP STORAGE) DATA BASE
PCB
SENSEG
SENSEG
SENSEG
*
*
*
TYPE=DB,NAME=G1CPCOM,KEYLEN=16,PROCOPT=PA
NAME=LTERMSEG,PARENT=0,PROCOPT=PA
NAME=TYPESEG,PARENT=LTERMSEG,PROCOPT=PA
NAME=QUEUESEG,PARENT=TYPESEG,PROCOPT=A
CUSTOMIZATION DATA BASE
PCB
TYPE=DB,NAME=G1CPFDF,KEYLEN=16,PROCOPT=A
SENSEG NAME=G1CPDFT,PARENT=0,PROCOPT=A
*
*
*
LICENSE MANAGEMENT DATA BASE
PCB
TYPE=DB,NAME=G1LICEN,PROCOPT=A,KEYLEN=23
SENSEG NAME=LMSSEG,PARENT=0
*
*
*
DELIVERY POINT VALIDATION (DPV) DATA BASE
PCB
TYPE=DB,NAME=G1DPVDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
DELIVERY POINT VALIDATION SPLIT (DPVS) DATA BASE
PCB
TYPE=DB,NAME=G1DPVSDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
DELIVERY POINT VALIDATION HASH/FULL(DPVH) DATA BASE
PCB
TYPE=DB,NAME=G1DPVHDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
RESIDENTIAL DELIVERY INDICATOR DATA BASE
PCB
TYPE=DB,NAME=G1CPRDI,PROCOPT=GO,KEYLEN=2
SENSEG NAME=RDISEG,PARENT=0
*
*
*
MATCHER STREET POINTER DATA BASE
PCB
TYPE=DB,NAME=G1CPSTR,PROCOPT=GO,KEYLEN=2
SENSEG NAME=STRSEG,PARENT=0
*
*
*
SUITELINK DATA BASE
PCB
TYPE=DB,NAME=G1SLKDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
LACSLINK DATA BASE
PCB
TYPE=DB,NAME=G1LLKDB,PROCOPT=GO,KEYLEN=4
SENSEG NAME=SEGMENT,PARENT=0
*
Working With CODE-1 Plus
451
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
*
*
LACSLINK SECURITY DATA BASE
PCB
TYPE=DB,NAME=G1CPSUD,PROCOPT=GR,KEYLEN=7
SENSEG NAME=SEGMENT,PARENT=0
*
*
*
ABBREVIATED AND PREFERRED ALIAS DATA BASE #1
PCB
TYPE=DB,NAME=C1PALA,PROCOPT=GO,KEYLEN=5
SENSEG NAME=AL2SEG,PARENT=0
*
*
*
ABBREVIATED AND PREFERRED ALIAS DATA BASE #2
PCB
TYPE=DB,NAME=C1PALP,PROCOPT=GO,KEYLEN=5
SENSEG NAME=AL2SEG,PARENT=0
*
*
*
*
BATCH NOT CODED (BNC) INPUT DATA BASE
PCB
TYPE=DB,NAME=G1CPBNCI,PROCOPT=GO,KEYLEN=8
SENSEG NAME=BNCSEG,PARENT=0
*
*
*
BATCH NOT CODED (BNC) OUTPUT DATA BASE
PCB
TYPE=DB,NAME=G1CPBNCO,PROCOPT=A,KEYLEN=8
SENSEG NAME=BNCSEG,PARENT=0,PROCOPT=A
*
*
*
GEO MASTER DATA BASE
PCB
TYPE=DB,NAME=GCMASTER,PROCOPT=GO,KEYLEN=3
SENSEG NAME=GCMAST,PARENT=0
*
*
*
GEO ZIP+4 MASTER DATA BASE
PCB
TYPE=DB,NAME=GCZ4MAST,PROCOPT=GO,KEYLEN=3
SENSEG NAME=GCZ4MAST,PARENT=0
*
*
*
GEO ROOF TOP MASTER DATA BASE
PCB
TYPE=DB,NAME=GCZ6MAST,PROCOPT=GO,KEYLEN=3
SENSEG NAME=GCZ6MAST,PARENT=0
*
*
*
GEO TAX MASTER DATA BASE
PCB
TYPE=DB,NAME=GTMASTR,PROCOPT=GO,KEYLEN=40
SENSEG NAME=VTSEG,PARENT=0
*
*
*
GEO TAX SECONDARY INDEX DATA BASE (ALTERNATE KEY)
PCB
TYPE=DB,NAME=GTMSTALT,PROCOPT=GO,KEYLEN=34
SENSEG NAME=VTSEG,PARENT=0
*
PSBGEN PSBNAME=G1CPC10,LANG=COBOL
END
452
Software Release 4.0.0/March 2015
IMS Processing
9
COBOL Call to IMS Version of C1MATCHI
A sample COBOL call to the IMS version of C1MATCHI (interactive matcher only)
follows.
NOTE: C1MATCHI does not support P9INTRF.
CALL WS-C1MATCHI USING P9IN
P9OUT
P9AUDT
G1CPCNY-PCB
G1CPCTY-PCB
G1CPDTL-PCB
G1CPLCL-PCB
G1CPCNM-PCB
G1CPZIP-PCB
G1CPLOT-PCB
G1LICEN-PCB
G1DPVDB-PCB
G1DPVSDB-PCB
G1DPVHDB-PCB
G1CPRDI-PCB
G1CPSTR-PCB
G1SLKDB-PCB
G1LLKDB-PCB
G1CPALA-PCB
G1CPALP-PCB
NOTE: If you wish to call the IMS version of C1MATCHI from your CICS
application, you must first move 'C' to P9IENV in P9IN before making the call. This
will signal the matcher to call program C1PGETDT in order to obtain the current
date using CICS facilities as opposed to obtaining it by a non-CICS compliant
method. You must also add to your CICS CSD a program entry for the COBOL
program C1PGETDT.
Working With CODE-1 Plus
453
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Calling CODE-1 Plus from Unix, Windows, or VMS
The instructions in this chapter assume that the application from which you want to
call CODE-1 Plus is written in COBOL. If your application is not written in COBOL,
please refer to the programmer documentation for that language for instructions on
calling programs outside your application. The documentation provided with the
COBOL compiler on your system should also be consulted for details about calling
COBOL programs from programs written in other languages.
The ACUCOBOL-GT environment is used by the Unix, Linux, and Windows versions
of these routines. The variables are also defined in bin/setup.
Sample COBOL Batch Program
The sample COBOL batch program, SMPLDRVR2, demonstrates the techniques used
to call the following modules.
Module
Description
C1MATCHx
Callable matching module
EXTADDR2
Address line extraction module
C1PRPT
Callable print program
The source code for SMPLDRVR2 can be found with the sample files distributed with
CODE-1 Plus.
454
Software Release 4.0.0/March 2015
Calling C1ANZADR
9
Calling C1ANZADR
The C1ANZADR module analyzes the ANALYSIS-PARAMETERS call area, which is
2,512 bytes and contains the input address. C1ANZADR returns normalized address
information through the 150-byte ANALYSIS-NORMALIZATION parameter. Based
on the analysis, CODE-1 Plus determines the appropriate address standardization.
ANALYSIS-PARAMETERS Call Area
The following table is a map of the positions in the call area passed to C1ANZADR.
Table 6: Call Area Passed To C1ANZADR (Part 1 of 2)
Position
1
Name
ANALYZE-FNC
Length
1
Contents
A 1-character code indicating the analyzation
control function. Specify one of the following
codes:
• E — End the program, close the tables, and do
not return any output.
• P — Analyze the input address string and return
analyzed output (default).
2
ADDR-ORIGIN
1
A 1-character code indicating from where the input
address string originated. One of the following
codes is stored:
• U — This is user address data.
• Z — This is the USPS ZIP+4 street name.
3
DIR-SPLIT
1
A 1-character code indicating whether to split a
complete directional word from the beginning of
the word (i.e., “WESTERN” becomes “W ERN”).
Specify one of the following codes:
• Y — Attempt to split the complete directional
word (default).
• N — Do not attempt to split the complete
directional word.
4
SUFFIX-SPLIT
1
A 1-character code indicating whether to split a
complete street suffix word from the end of the
word (i.e., “BROADWAY” becomes “BROAD WAY”).
Specify one of the following codes:
• Y — Attempt to split the complete suffix word
(default).
• N — Do not attempt to split the complete suffix
word.
Working With CODE-1 Plus
455
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 6: Call Area Passed To C1ANZADR (Part 2 of 2)
Position
5
Name
NORMALIZEFNC
Length
1
Contents
A 1-character code indicating the normalize
control function. Specify one of the following
codes:
• N — Analyze the input address string and return
“normalized” output.
• X — Do not return “normalized” address
elements (default).
6-10
Reserved
5
11-110
ADDRESSSTRING
100
The input address string. C1ANZADR assumes that
the last byte is always blank.
1112,512
N/A
2,402
These bytes are reserved for internal matching
variables.
NOTE: For Unisys-A users, this position is 1112516 and the length for this position is 2,406.
ANALYSIS-NORMALIZATION Call Area
The following table is a map of the positions in the call area passed to C1ANZADR.
Table 7: Call Area Passed To C1ANZADR (Part 1 of 3)
Position
Name
Length
Contents
Normalized Address Elements
456
1-10
HOUSE-NR
10
The left-justified, normalized house number.
11-12
PRE-DIR
2
The normalized pre-directional indicator.
13-57
STREET-NAME
45
The normalized street name, which is any
information that remains after all other address
elements are identified and extracted
58-61
SUFFIX
4
The normalized street suffix.
62-63
POST-DIR
2
The normalized post directional indicator.
64-67
APT-TYPE
4
The normalized apartment type (designator).
68-75
APT-NR
8
The left-justified, normalized apartment string.
Software Release 4.0.0/March 2015
Calling C1ANZADR
9
Table 7: Call Area Passed To C1ANZADR (Part 2 of 3)
Position
76-77
Name
RR-TYPE
Length
2
Contents
A 2- character code indicating the normalized rural
route/highway contract type. One of the following
codes is stored:
• Blank — No type was stored.
• HC — The address contains a highway contact
number.
• RR — The address contains a rural route
number.
78-80
RRT-NR
3
The left-justified, normalized rural route/highway
contract number.
81-90
BOX-NR
10
The left-justified, normalized box number.
91-94
PMB-D
4
Private Mailbox Descriptor
• # — Nonstandard Private Mailbox Designator
• PMB — Standard Private Mailbox Designator
95-110
PMB-NR
16
The left-justified, formatted Private Mailbox (PMB)
string. This does not include the Private Mailbox
Descriptor.
111-112
STREET-LEN
2
The normalized length of the street name.
113-133
Reserved
21
134
STD-PRE-DIR
1
A 1-character pre-directional standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the
input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
135
STD-SUFFIX
1
A 1-character suffix standard format indicator.
One of the following codes is stored:
• Blank — The element was not present in the
input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
136
STD-POST-DIR
1
A 1-character post-directional standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the
input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
Working With CODE-1 Plus
457
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 7: Call Area Passed To C1ANZADR (Part 3 of 3)
Position
137
Name
STD-RR-TYPE
Length
1
Contents
A 1-character rural route/highway contract type
standard format indicator. One of the following
codes is stored:
• Blank — The element was not present in the
input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
138
STD-GD
1
A 1-character general delivery standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the
input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
139
STD-APT-TYPE
1
A 1-character apartment type standard format
indicator. One of the following codes is stored:
• Blank — The element was not present in the
input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
140
STD-PMB
1
A 1-character Private Mailbox (PMB) string
indicator. One of the following codes is stored:
• Blank — The element was not present in the
input.
• N — The input was in a non-standard format.
• S — The input is in a standard format.
141
STD-BOX
1
A 1-character box number type standard format
indicator. One of the following codes is stored:
• Blank — There was no box number.
• B — Input was the literal “Box.”
• N — Input was present, but was neither of the
above.
• P — Input was the literal “Post Office Box.”
142-150
458
Reserved
9
Software Release 4.0.0/March 2015
Calling C1BMCBD
9
Calling C1BMCBD
The callable batch driver C1BMCBD allows a program supplied by the user to submit
one address at a time to CODE-1 Plus for matching. The batch driver analyzes the
address and attempts a match with the database. When an “END” call is issued to
C1BMCBD, it produces the same reports as batch driver C1BM00. The USPS form
3553 is also produced. C1BMCBD runs with all parameters used by C1BM00.
The ADDRDF, CS ZIP, FILEDF, HEADER, and at least one xx OUT parameters are
required. When calling C1BMCBD for matching, send a space in the CBD-ACTIONCODE and the input record in CBD-INPUT. C1CBCBD will use the input file
parameters (ADDRDF, CS ZIP, and FIRMNM) to define the input and returns an
output record formatted as described by any xx OUT parameters in CBD-OUTPUT.
C1BMCBD will close processing and produce reports when an “E” is sent in CBDACTION-CODE.
The following parameters will not function with C1BMCBD. Their data are ignored:
•
FILEDF—except for C1BMSTA
•
CHCKPT
•
NTHSEL
•
SEQCHK
However, if present, these parameters must be in proper format to pass the edits. The
FILEDF parameter for C1BMNAM must be present, although data from it will be
ignored (instead, the program supplied by the user defines the input file).
NOTE: The source code for SMPLCBD, a sample COBOL batch program for calling
C1BMCBD, is included with the other sample files you received with CODE-1 Plus.
The parameters to be passed to C1BMCBD are supplied as a COBOL copybook
(CBDPARM) with the software as detailed below:
Working With CODE-1 Plus
459
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Table 8: The Call Area Passed to C1BMCBD (CBDPARM)
Positions
1
Name
CBD-ACTION-CODE
Length
1
Contents
Code indicating whether C1BMCBD should match
address or print reports.
• Blank — Match address given in input area.
• E — End processing, close files, and print
reports.
2-3
CBD-RC
2
Return code from C1BMCBD
• 1 — Parameter Error
• 4 — Z4 Change Error
• 8 — Z4 Change Error
• 12 — Parameter Error
• 16 — Parameter Error
• 22 — General CODE-1 Plus Error
• 24 — Geographic Coding Error
• 26 — Z4 Change Error
• 99 — General Error
460
4-32763
CBD-INPUT
32760
Input record of name and address file.
3276465523
CBD-OUTPUT
32760
Output record.
Software Release 4.0.0/March 2015
Calling C1BMCBD
9
Calling C1BMCBD in IMS
The call to C1BMCBD in IMS must also include the PCBs used by C1BMCBD. Calling
the IMS version of C1BMCBD in COBOL would look like the following example:
CALL “C1BMCBD” USING CBD-ACTION CODE
CBD-RC
CBD-INPUT
CBD-OUTPUT
IO-PCB
G1CPCNY-PCB
G1CPCTY-PCB
G1CPDTL-PCB
G1CPLCL-PCB
G1CPCNM-PCB
G1CPZIP-PCP
G1CPLOT-PCP
G1C1AUX-PCB
G1LICEN-PCB
G1CPDPM-PCP
G1CPDPL-PCB
GCMASTER-PCB
GCZ4MAST-PCB
GCZ6MAST-PCB
GTMASTR-PCB
GTMSTALT-PCB
Working With CODE-1 Plus
461
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Calling the Address Line Extraction Module (EXTADDR2)
The CODE-1 Plus Address Line Extraction Module (EXTADDR2):
1. Accepts up to six address lines as input.
2. Processes the input address lines and returns the following fields:
•
Primary address field
•
Secondary address field
•
Firm name field
•
Urbanization name field for Puerto Rican addresses
•
City/state
•
ZIP Code
3. Passes the returned fields to the CODE-1 Plus matcher to code the address
4. Returns input information that was not used to create the returned fields. This
unused information is not necessary for the matcher to code an address and is
being provided for your convenience.
Calling EXTADDR2
EXTADDR2 is a separate routine that can be called independently of the CODE-1
Plus matcher. The EXT2PARM and EX2DATA parameters are required to call
EXTADDR2. Pitney Bowes supplies the EXT2PARM and EX2DATA parameters as
COBOL copybooks with the CODE-1 Plus software. For more information on these
copybooks, please refer to “Supplied Copybooks” on page 463.
When first calling EXTADDR2:
1. The entire EXT2PARM structure should be initialized to spaces before being
called and not thereafter.
2. The “Input Types” value should be set to "A
and not modified thereafter.
" (uppercase "A" and five spaces)
3. The EXT2DATA call area should be initialized to spaces for each and every call.
462
Software Release 4.0.0/March 2015
Calling the Address Line Extraction Module (EXTADDR2)
9
Sample COBOL Batch Program
Pitney Bowes supplies a sample COBOL batch program, SMPLDRVR2, that
demonstrates techniques for calling:
•
C1MATCHx
•
EXTADDR2
•
C1PRPT (callable print program)
You can find the source code for the SMPLDRVR2 program with the other sample
files included with your CODE-1 Plus software.
Special Processing Switches
As stated previously, EXTADDR2 parses the input lines and returns the primary
address field, secondary address field, Firm name field, city and state in one field, and
the ZIP Code in a separate field.
•
If you do not need EXTADDR2 to identify the input line that contains the Firm
name, set the "Firm Identification Switch” to "S".
•
If you do not need EXTADDR2 to identify the City, State, and ZIP Code, set the
"City/State/ZIP Identification Switch" to "S".
•
If you do not need EXTADDR2 to identify the Urbanization name, set the
"Urbanization Identification Switch" to "S".
Supplied Copybooks
The two call areas for EXTRADDR2 are defined in the supplied EXT2PARM copybook
and as a 600-byte array defined in the EXT2DATA copybook. The EXT2PARM and
EXT2DATA copybooks are defined below.
EXT2PARM Copybook
Position
Field Name
Length
Description
Input Fields
1
EXT2-ADDR-LINE-1
100
Address Line 1
101
EXT2-ADDR-LINE-2
100
Address Line 2
201
EXT2-ADDR-LINE-3
100
Address Line 3
301
EXT2-ADDR-LINE-4
100
Address Line 4
Working With CODE-1 Plus
463
9
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Position
Field Name
Length
Description
401
EXT2-ADDR-LINE-5
100
Address Line 5
501
EXT2-ADDR-LINE-6
100
Address Line 6
601
Reserved
20
621
EXT-NO-MERGE-SEC-PMB
1
Secondary and PMB merge switch:
• Blank — Merge any secondary or
PMB information with the primary
address.
• S — Do not merge secondary or PMB
information with the primary address
line.
622
EXT-SKIP-FIRM
1
Firm identification switch:
• Blank — Identify the likely firm line
from the input lines.
• S — Do not attempt to identify the
firm from the input lines.
623
EXT-SKIP-URB
1
Urbanization identification switch:
• Blank — Attempt to identify the
urbanization line from the input
lines.
• S — Do not attempt to identify the
urbanization line from the input
lines.
624
EXT-SKIP-CSZ
1
City, State, and ZIP Code identification
switch:
• Blank — Attempt to identify the city,
state, and ZIP Code from the input
lines.
• S — Do not try to identify the city,
state, and ZIP Code from the input
lines.
625
Reserved
76
EXT2-P9IZIP
5
Output Fields
701
Output ZIP Code.
ZIP Code identified unless the City/
State/ZIP identification switch was set
to “S”.
706
EXT2-P9IZIP4
4
Output ZIP+4 add-on.
ZIP + 4 add-on code identified unless
the City/State/ZIP identification switch
was set to “S”.
464
710
EXT2-P9IAD1
100
Primary address line.
810
EXT2-P9IAD2
100
Secondary address line.
Software Release 4.0.0/March 2015
Calling the Address Line Extraction Module (EXTADDR2)
Position
Field Name
Length
9
Description
910
EXT2-P9IFRM
100
Firm name.
1010
EXT2-P9ICST
100
City/state.
1110
EXT2-P9IURB
35
Urbanization name.
1145
Reserved
11
1156
EXT2-INPUT-TYPES
6
Input types.
Should be set to “A “ (uppercase "A"
and five spaces) to activate processing
using the Firm, Urbanization, and City/
State/ZIP identification switches.
1162
Reserved
39
EXT2DATA Copybook
The second parameter that must be passed to EXTADDR2 is defined in the table
below and in the EXT2DATA copybook. EXTADDR2 returns information from the six
input lines that was not used to create the data fields that are passed to the matcher
to code an address (this data is referred to as Additional Input Data). This call area is
required but the information is returned for your convenience and is not needed to
code an address.
Position
Field Name
Length
Description
1
EXTRA-DATA-LINE1
100
Extra data from input line 1
101
EXTRA-DATA-LINE2
100
Extra data from input line 2
201
EXTRA-DATA-LINE3
100
Extra data from input line 3
301
EXTRA-DATA-LINE4
100
Extra data from input line 4
401
EXTRA-DATA-LINE5
100
Extra data from input line 5
501
EXTRA-DATA-LINE6
100
Extra data from input line 6
Working With CODE-1 Plus
465
9
466
Calling CODE-1 Plus Matching, Analyzer, and Callable Batch Driver Modules
Software Release 4.0.0/March 2015
CHAPTER 10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
This chapter discusses the callable routines C1PRPT, C1CTYLKx, and G1CPLKx.
C1PRPT allows you to print the CODE-1 Plus reports without using C1BM00, the
Pitney Bowes-provided CODE-1 Plus batch driver. By using C1PRPT, you can call
CODE-1 Plus from your own applications and still generate the
CODE-1 Plus
reports. C1CTYLKx enables you to match ZIP Codes to city/state combinations.
G1CPLKx enables you to browse the CODE-1 Plus database from your own
application.
What is C1PRPT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling C1PRPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The C1PRPT Call Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is C1CTYLKx?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZIP Code Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
City and State Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ZIP Code and City/State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling from an IMS Application . . . . . . . . . . . . . . . . . . . . . . . . . .
The C1CTYLKx Call Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What is G1CPLKx? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling G1CPLKC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G1CPLK-USER-REQUEST-AREA . . . . . . . . . . . . . . . . . . . . . . . . .
G1CPLK-USER-RESULT-AREA . . . . . . . . . . . . . . . . . . . . . . . . . . .
G1CPLK-IPC-AREAS-LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling G1CPLKB from an IMS Application . . . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
468
469
471
481
482
482
482
483
484
485
489
489
490
494
496
497
467
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
What is C1PRPT?
C1PRPT is a callable routine that you can use to generate the CODE-1 Plus reports
when you are calling CODE-1 Plus from your own batch driver. The CODE-1 Plus
batch driver provided by Pitney Bowes prints these reports:
•
NDI Report
•
Control Totals Report
•
Analysis of Matched Records Report
•
Address-Match Execution Statistics Report
•
ZIP+4 Coding by State
•
Carrier Route Coding by State
•
Line of Travel Coding by State
•
ZIP+4 Coding by List Code
•
Carrier Route Coding by List Code
•
Line of Travel Coding by List Code
•
ZIP+4 Coding by 3-Digit ZIP Code
•
Carrier Route Coding by 3-Digit ZIP Code
•
Line of Travel Coding by 3-Digit ZIP Code
•
Processing Summary by State
•
Processing Summary by List Code
•
Processing Summary by 3-Digit ZIP Code.
You can specify which of these reports are to be printed, based on information in the
call area passed to C1PRPT. You also have the option of producing these reports in
all upper case or in upper and lower case.
NOTE: The USPS Form 3553 is not printed from C1PRPT. Current USPS
regulations require any user-written program calling CODE-1 Plus for the
purpose of claiming automation discounts to undergo CASS certification.
Therefore, the user-written program must generate and print the USPS Form
3553.
468
Software Release 4.0.0/March 2015
Calling C1PRPT
10
Calling C1PRPT
When you call C1PRPT, you must pass the P9IN, P9OUT, P9AUDIT, and C1PRPT call
areas, in that order. The P9IN, P9OUT, and P9AUDIT areas are the same areas that
you use when you call the C1MATCHx modules.
NOTE: You must initialize the C1PRPT call area to spaces and the counters to
zeros prior to your first call to C1PRPT. The COBOL copy member RPTPARM is
provided on the distribution media for the C1PRPT call area.
Each time you place a call to the C1MATCHx, you must also call C1PRPT (i.e., call
C1PRPT once for each input record in your file, plus once more to close processing).
On all but the last call to C1PRPT, C1PRPT compiles statistics based on the match
results of each record. On the last call (as indicated by an E in P9IFNC), C1PRPT
prints the requested reports, using the statistics compiled on previous calls.
Between each call to C1MATCHx and C1PRPT, you must increase the counters for
the number of input records read (RP-CT-AMA) and the number of input records
processed (RP-CT-PRC). Additionally, you must reset the return code fields in the
C1PRPT call area to reflect the return codes from C1MATCHx for your input record.
These return code fields are RP-BM0ARC, RP-BM0CRC, RP-BM0SRC, RP-BM05RC,
RP-BM09RC, and RP-BM0LOT.
Please refer to the following example call program (continued on the next page) for
clarification of the issues discussed above.
0050-INITIALIZE.
* INITIALIZE FOR C1PRPT ROUTINE
MOVE SPACES TO C1PRPT-CALL
MOVE ZEROS TO
RP-CT-NAM
RP-CT-PRC
RP-CT-BYP
RP-CT-COK
RP-CT-NCO
RP-CT-IZP
RP-CT-ZP4
RP-CT-AMA
RP-CT-VAL
RP-CT-APO
RP-CT-MIL
RP-CT-GOV
* OTHER INITIALIZATION LOGIC
...
0050-EXIT. EXIT.
0100-MAIN-LOOP.
* READ INPUT RECORD
PERFORM 0200-GET-INPUT-RECORD THRU 0200-EXIT
IF END-OF-FILE
PERFORM 0800-WRAPUP
ELSE
Working With CODE-1 Plus
THRU 0800-EXIT
469
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
ADD 1 TO RP-CT-NAM
* MANIPULATE INPUT
PERFORM 0300-PROCESS-RECORD THRU 0300-EXIT
IF BYPASS-THIS-RECORD
ADD 1 TO RP-CT-BYP
PERFORM 0350-BYPASS-PROCESS THRU 0350-EXIT
ELSE
* INITIALIZE P9IN FIELDS
PERFORM 0400-SETUP-P9IN THRU 0400-EXIT
CALL 'C1MATCHx' USING P9IN P9OUT P9AUDIT
ADD 1 TO RP-CT-AMA
ADD 1 TO PR-CT-PRC
MOVE
MOVE
MOVE
MOVE
MOVE
MOVE
P9OSAR
P9OCRC
P9OSRC
P9O5RC
P9O9RC
P9OLOT
TO
TO
TO
TO
TO
TO
RP-BM0ARC
RP-BM0CRC
RP-BM0SRC
RP-BM05RC
RP-BM09RC
RP-BM0LOT
* THE RP-BMOXXX CODES ABOVE CAN BE ADJUSTED AS REQUIRED
...
CALL 'C1PRPT' USING P9IN P9OUT P9AUDIT RPTPARM
* PROCESS OUTPUT AND WRITE IT
ADD 1 TO RP-CT-COK
PERFORM 0500-WRITE THRU 0500-EXIT.
0100-EXIT. EXIT.
...
0800-WRAPUP.
MOVE 'E' TO P9IFNC
CALL 'C1MATCHx' USING P9IN P9OUT P9AUDIT
* SET THE REPORT SELECTION FLAGS
MOVE 'Y' TO RP-RPNDI
...
* SET THE REPORT DATE, HEADER, ADDITIONAL HEADERS & FOOTERS
...
CALL 'C1PRPT' USING P9IN P9OUT P9AUDIT RPTPARM.
0800-EXIT. EXIT.
470
Software Release 4.0.0/March 2015
Calling C1PRPT
10
The C1PRPT Call Area
The following table shows you a map of the 1,348-byte C1PRPT call area.
NOTE: A copybook, called RPTPARM, of this area is provided on your installation
tape.
Table 1: The C1PRPT Call Area (Part 1 of 11)
Position
Name
Length
Contents
The following detail-level parameters are used for all but the last call to C1PRPT.
1
RP-RETURNCODE
1
A code filled in by C1PRPT when control is passed
back to your driver program. It will contain one of
the following codes:
• Blank — C1PRPT encountered no problems
during processing.
• E — C1PRPT encountered an error. Look for a
message in your print file.
Working With CODE-1 Plus
471
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
Table 1: The C1PRPT Call Area (Part 2 of 11)
Position
2
Name
RP-BM0ARC
Length
1
Contents
A code indicating whether or not the standardized
address was stored in the output record, and if not,
why not. Your driver should construct this field by
moving the value that is in the P9OSAR area (as
returned by C1MATCHx) to the RP-BM0ARC area.
RP-BM0ARC will then contain one of the following
values:
• Blank — The standardized address was stored
successfully.
• A — Apartment number missing or not found in
database, and an apartment level match was
required.
• B — Insufficient (or blank) address information
for a match.
• H — House/Box number not found on street.
• M — Multiple matches of equal quality were
found.
• S — Street name not found in ZIP Code.
• U — Auxiliary File Processing unavailable.
• Z — ZIP Code not found in database.
Additionally, if P9OSAR was blank, your driver
program may place one of the following codes in
this area:
• C — The address probable correctness or overall
probable correctness was too high.
• D—
Information was dropped.
• L — The standardized address was too long.
• M — Multiple ZIP Codes or multiple standardized
addresses were found.
• N — The standardized address wasn't stored
because the processing requirements specified
that it was not to be stored.
If any other value is in RP-BM0ARC, the report
program will assume that the standardized address
was not stored for some unknown reason.
472
Software Release 4.0.0/March 2015
Calling C1PRPT
10
Table 1: The C1PRPT Call Area (Part 3 of 11)
Position
3
Name
RP-BM0CRC
Length
1
Contents
A code indicating whether or not the carrier route
was stored in the output record, and if not, why not.
Your driver should construct this field by moving the
value that is in the P9OCRC area (as returned by
C1MATCHx) to the RP-BM0CRC area. RP-BM0CRC
will then contain one of the following values:
• Blank — The carrier route was stored
successfully.
• A — Apartment number missing or not found in
database, and an apartment level match was
required.
• B — Insufficient (or blank) address information
for a match.
• H — House/Box number not found on street.
• M — Multiple matches of equal quality were
found.
• S — Street name not found in ZIP Code.
• U — Auxiliary File Processing unavailable.
• Z — ZIP Code not found in database.
Additionally, if P9OCRC was blank, your driver
program may place one of the following codes in
this area:
• C — The address probable correctness or overall
probable correctness was too high.
• D — Information was dropped.
• L — The standardized address was too long.
• M — Multiple ZIP Codes or multiple standardized
addresses were found.
• N — The carrier route wasn't stored because the
processing requirements specified that it was not
to be stored.
If any other value is in RP-BM0CRC, the report
program will assume that the carrier route was not
stored for some unknown reason.
Working With CODE-1 Plus
473
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
Table 1: The C1PRPT Call Area (Part 4 of 11)
Position
4
Name
RP-BM0SRC
Length
1
Contents
A code indicating whether or not the standardized
city and state were stored in the output record, and
if not, why not. Your driver should construct this
field by moving the value that is in the P9O5RC area
(as returned by C1MATCHx) to the RP-BM0SRC
area. This field is constructed from the P9O5RC,
which is the return code for the 5-digit ZIP Code.
RP-BM0SRC will contain one of the following
values:
• Blank — The input ZIP Code was stored
successfully.
• Z — ZIP Code not found in database.
• A — Apartment number missing or not found in
database, and an apartment level match was
required.
• B — Insufficient (or blank) address information
for a match.
• H — House/Box number not found on street.
• M — Multiple matches of equal quality were
found.
• S — Street name not found in ZIP Code.
Additionally, if P9O5RC was blank, your driver
program may place one of the following codes in
this area:
• C — The address probable correctness or overall
probable correctness was too high.
• D — Information was dropped.
• L — The standardized address was too long.
• M — Multiple ZIP Codes or multiple standardized
addresses were found.
• N — The standardized city and state were not
stored because the processing requirements
specified that it was not to be stored.
• X — No city match was found and we chose not to
store the default name (i.e, P9OOCR was not a
blank and the default name returned by
C1MATCHx was not stored).
If any other value is in RP-BM05RC, the report
program will assume that the standardized city and
state were not stored for some unknown reason.
474
Software Release 4.0.0/March 2015
Calling C1PRPT
10
Table 1: The C1PRPT Call Area (Part 5 of 11)
Position
5
Name
RP-BM05RC
Length
1
Contents
A code indicating whether or not the matched 5-digit
ZIP Code was stored in the output record, and if not,
why not. Your driver should construct this field by
moving the value that is in the P9O5RC area (as
returned by C1MATCHx) to the RP-BM05RC area.
RP-BM05RC will then contain one of the following
values:
• Blank — The ZIP Code was stored successfully.
• A — Apartment number missing or not found in
database, and an apartment level match was
required.
• B — Insufficient (or blank) address information
for a match.
• E — External match — Auxiliary File Processing.
• H — House/Box number not found on street.
• M — Multiple matches of equal quality were
found.
• S — Street name not found in ZIP Code.
• Z — ZIP Code not found in database.
Additionally, if P9O5RC was blank, your driver
program may place one of the following codes in
this area:
• C — The address probable correctness or overall
probable correctness was too high.
• D — Information was dropped.
• L — The standardized address was too long.
• M — Multiple ZIP Codes or multiple standardized
addresses were found.
• N — The matched ZIP Code wasn't stored
because the processing requirements specified
that it was not to be stored.
If any other value is in RP-BM05RC, the report
program will assume that the matched ZIP Code
was not stored for some unknown reason.
Working With CODE-1 Plus
475
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
Table 1: The C1PRPT Call Area (Part 6 of 11)
Position
6
Name
RP-BM09RC
Length
1
Contents
A code indicating whether or not the matched ZIP+4
Code was stored in the output record, and if not, why
not. Your driver should construct this field by
moving the value that is in the P9O9RC area (as
returned by C1MATCHx) to the RP-BM09RC area.
RP-BM09RC will then contain one of the following
values:
• Blank — The ZIP+4 Code was stored successfully.
• A — Apartment number missing or not found in
database, and an apartment level match was
required.
• B — Insufficient (or blank) address information
for a match.
• H — House/Box number not found on street.
• M — Multiple matches of equal quality were
found.
• S — Street name not found in ZIP Code.
• U — Auxiliary File Processing unavailable.
• V — The input record matched a non-deliverable
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 in database.
Additionally, if P9O9RC was blank, your driver
program may place one of the following codes in
this area:
• C — The address probable correctness or overall
probable correctness was too high.
• D — Information was dropped.
• L — The standardized address was too long.
• M — Multiple ZIP Codes or multiple standardized
addresses were found.
• N — The matched ZIP+4 Code wasn't stored
because the processing requirements specified
that it was not to be stored.
If any other value is in RP-BM09RC, the report
program will assume that the matched ZIP+4 Code
was not stored for some unknown reason.
476
Software Release 4.0.0/March 2015
Calling C1PRPT
10
Table 1: The C1PRPT Call Area (Part 7 of 11)
Position
7
Name
RP-BM0LOT
Length
1
Contents
A code indicating the level of match obtained against
the Line of Travel masterfile. Your driver should
construct this field by moving the value that is in the
P9OLOT area (as returned by C1MATCHx) to the RPBM0LOT area. RP-BM0LOT will then contain one of
the following values:
• Blank — Invalid input (zero or non-numeric ZIP/
ZIP+4 add-on)
• 9 — 9-digit ZIP+4 match successful
• C — Call to LTO10/LTO10C failed
• D — Unsuccessful 9-digit match, default coded
• F — Open/read failure on Line of Travel master
file
• V — Line of Travel matcher software not
compatible with the Line of Travel master file
Additionally, if P9OLOT was blank, your driver
program may place one of the following codes in
this area:
• C — The address probable correctness or overall
probable correctness was too high.
• D — Information was dropped.
• L — The standardized address was too long.
• M — Multiple ZIP Codes or multiple standardized
addresses were found.
• N — The matched ZIP+4 Code wasn't stored
because the processing requirements specified
that it was not to be stored.
If any other value is in RP-BM0LOT, the report
program will assume that the matched LOT code
was not stored for some unknown reason.
8-16
RP-LCDNEW
9
The list code for the current record.
17
RP-INP-ZP4
1
A code indicating if an input ZIP+4 Code was defined
for the input file. Moved for every record whether it
was a blank or not.
18-21
RP-INP-ZP4-VAL
4
The ZIP+4 Code that was in the input record, if RPINP-ZP4 is Y.
22-57
Reserved
36
The following total-level parameters are used for the last call to C1PRPT. These areas are not
referenced for any call to C1PRPT except the last.
NOTE: All of these fields should be initialized to zero and then updated by your own program, as
necessary.
58-67
Working With CODE-1 Plus
RP-CT-NAM
10
A counter that reflects the number of input records
read.
477
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
Table 1: The C1PRPT Call Area (Part 8 of 11)
Position
Name
Length
Contents
68-77
RP-CT-PRC
10
A counter that reflects the number of input records
processed.
78-87
RP-CT-BYP
10
A counter that reflects the number of input records
bypassed.
88-97
RP-CT-COK
10
A counter that reflects the number of records
written to the C1BMCOK (or equivalent) output file.
98-107
RP-CT-ZP4
10
A counter that reflects the number of records
written to the C1BMZP4 (or equivalent) output file.
108-117
RP-CT-NCO
10
A counter that reflects the number of records
written to the C1BMNCO (or equivalent) output file.
118-127
RP-CT-IZP
10
A counter that reflects the number of records
written to the C1BMIZP (or equivalent) output file.
128-137
RP-CT-AMA
10
A counter that reflects the number of calls made to
the address match routine.
138-147
RP-CT-VAL
10
A counter that reflects the number of records that
were confirmed without processing due to a flag in
the records.
148-157
RP-CT-APO
10
A counter that reflects the number of records that
were confirmed without processing due to APO ZIP
Codes.
158-167
RP-CT-MIL
10
A counter that reflects the number of records that
were confirmed without processing due to military
ZIP Codes.
168-177
RP-CT-GOV
10
A counter that reflects the number of records that
were confirmed without processing due to
government agency ZIP Codes.
178-227
Reserved
50
NOTE: All of the report flags listed below default to Y except the RP-RPNDI report flag, which defaults
to N.
228
RP-RPNDI
1
A code that indicates whether or not the National
Deliverability Index (NDI) Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
478
Software Release 4.0.0/March 2015
Calling C1PRPT
10
Table 1: The C1PRPT Call Area (Part 9 of 11)
Position
229
Name
RP-RPANMR
Length
1
Contents
A code that indicates whether or not the Analysis of
Matched Records Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
230
RP-RPZ4ST
1
A code that indicates whether or not the ZIP+4
Coding by State Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
231
RP-RPCRST
1
A code that indicates whether or not the Carrier
Route Coding by State Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
232
RP-RPLTST
1
A code that indicates whether the Line of Travel
Coding by State Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
233
RP-RPZ4LC
1
A code that indicates whether or not the ZIP+4
Coding by List Code Records Report should be
printed.
• Y — Print the report (default).
• N — Do not print the report.
234
RP-RPCRLC
1
A code that indicates whether or not the Carrier
Route Coding by List Code Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
235
RP-RPLTLC
1
A code that indicates whether the Line of Travel
Coding by List Code Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
236
RP-RPZ43D
1
A code that indicates whether or not the ZIP+4
Coding by 3-Digit ZIP Code Report should be
printed.
• Y — Print the report (default).
• N — Do not print the report.
237
RP-RPCR3D
1
A code that indicates whether or not the Carrier
Route Coding by 3-Digit ZIP Code Report should be
printed.
• Y — Print the report (default).
• N — Do not print the report.
Working With CODE-1 Plus
479
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
Table 1: The C1PRPT Call Area (Part 10 of 11)
Position
238
Name
RP-RPLT3D
Length
1
Contents
A code that indicates whether the Line of Travel
Coding by 3-Digit ZIP Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
239
RP-RPSMST
1
A code that indicates whether or not the Summary
by State Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
240
RP-RPSMLC
1
A code that indicates whether or not the Summary
by List Code Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
241
RP-RPSM3D
1
A code that indicates whether or not the Summary
by 3-Digit ZIP Code Report should be printed.
• Y — Print the report (default).
• N — Do not print the report.
242
RP-RPUPLO
1
A code indicating whether or not the reports should
be printed in all upper case.
• Y — Print the reports in all upper case (default).
• N — Print the reports in mixed case.
480
243-252
RP-DATE
10
The date that is to be printed at the top of the
reports.
253-292
RP-HEADER
40
The main header that is to be printed at the top of
the reports.
293-424
RP-UHD-(1)
132
The first line of the additional header that is to be
printed at the top of the reports.
425-556
RP-UHD-(2)
132
The second line of the additional header that is to be
printed at the top of the reports.
557-688
RP-UHD-(3
132
The third line of the additional header that is to be
printed at the top of the reports.
689-820
RP-UHD-(4)
132
The fourth line of the additional header that is to be
printed at the top of the reports.
821-952
RP-UFT-(1)
132
The first line of the footer that is to be printed at the
bottom of the reports.
953-1084
RP-UFT-(2)
132
The second line of the footer that is to be printed at
the bottom of the reports.
Software Release 4.0.0/March 2015
What is C1CTYLKx?
10
Table 1: The C1PRPT Call Area (Part 11 of 11)
Position
Name
Length
Contents
10851216
RP-UFT-(3)
132
The third line of the footer that is to be printed at the
bottom of the reports.
12171348
RP-UFT-(4)
132
The fourth line of the footer that is to be printed at
the bottom of the reports.
What is C1CTYLKx?
There are two forms of C1CTYLKx:
•
C1CTYLKP
•
C1CTYLKC
C1CTYLKP is a COBOL subroutine that you can call from your own program; it uses
your copy of the CODE-1 Plus database to obtain its results. C1CTYLKP allows you
to match ZIP Codes to city/state combinations. By using C1CTYLKP, you can have
CODE-1 Plus retrieve a city/state for a given ZIP Code, a ZIP Code for a given
city/state (see important restrictions below), or provide verification that a given ZIP
Code and city/state combination is correct. C1CTYLKP can also be used to retrieve
detailed information for a given city/state, including the short city name.
C1CTYLKC performs the identical function in CICS.
NOTE: C1CTYLKx can return a correct ZIP Code for a given city/state only if the
city/state has a unique ZIP Code. Many cities have more than one ZIP Code
assigned to them. When this is the case, C1CTYLKx returns the lowest ZIP Code
in the range of the ZIP Codes for the input city/state and all the ZIP Codes that
the city/state falls within. This answer must be considered to be unreliable, as
C1CTYLKx has no way to determine which ZIP Code is the correct one. When this
is the case, the only reliable information returned is the short city name, long city
name, and state abbreviation.
If at all possible, sort your input file in ZIP Code sequence before it is run through
C1CTYLKx. This gives you the best possible performance. If this is not possible,
sort the file by city name to produce the next best performance level.
C1CTYLKx can provide three different functions, depending upon the type of data
that is passed from the calling program. The functions for each data type are
described in the following sections.
Working With CODE-1 Plus
481
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
ZIP Code Only
When C1CTYLKx is passed only a ZIP Code with no city/state, it attempts to return a
city/state for that ZIP Code, as follows:
1. If a primary city/state is found on the database for the ZIP Code, it is returned.
2. If no primary city/state is found for that ZIP Code, the first secondary city/state
combination is returned, if one exists.
3. If no primary or secondary city/state is found for the input ZIP Code, the first
city/state on the database that matches the ZIP Code is returned.
NOTE: Under certain conditions, no city/state is returned. For example,
if vanity city names are not allowed, and only vanity cities are found for a
ZIP Code, no city/state is returned.
City and State Only
When C1CTYLKx is passed the city and state without a ZIP Code, C1CTYLKx
attempts to return the ZIP Code for that city and state. C1CTYLKx can return a
correct ZIP Code for a given city/state only if the city/state has a unique ZIP Code.
Many cities have more than one ZIP Code assigned to them. When this is the case,
C1CTYLKx returns the lowest ZIP Code in the range of the ZIP Codes for the input
city/state and all the ZIP Codes that the city/state fall within. This answer must be
considered to be unreliable, as C1CTYLKx has no way to determine which ZIP Code
is the correct one. When this is the case, the only reliable information returned is the
short city name, long city name, and state abbreviation.
ZIP Code and City/State
Please read the
previous section,
entitled “City and
State Only.”
482
When C1CTYLKx is passed the ZIP Code and the city and state, it attempts to find a
match for the ZIP Code as if only the ZIP Code was passed. If a match is found,
C1CTYLKx attempts to find the input city/state on the list of city/states for the input
ZIP Code. If the city/state is not found within the ZIP Code, a new city/state is
returned (following the rules for determining a city/state when only a ZIP Code is
passed). If the input ZIP Code is not on the database, C1CTYLKx performs as if only
a city and state were passed. If neither the input ZIP Code nor the input city and state
are found on the database, no match is returned.
Software Release 4.0.0/March 2015
Calling C1CTYLKx
10
Output Results
When a match is found for an input ZIP Code, city and state, or combination, the
following information is returned to your program:
•
USPS City name
•
USPS Short city name
•
USPS State abbreviation
•
City type (primary, secondary, or vanity)
•
USPS Finance number
•
USPS Last line number
•
A table of up to 100 cities that are found to be within the returned ZIP Code.
Each entry in the table contains the information listed above.
•
A table of up to 999 ZIP Codes that a city/state falls within. Each entry includes
the information listed above including the USPS ZIP Code.
•
USPS ZIP Code
•
Return Codes indicating the results of the match attempt
•
Audit trail information showing I/O counts.
Vanity City Names
A field has been provided in the calling interface that indicates whether vanity city
names are to be allowed or not allowed. Not allowing vanity city names can prevent
any city names from being returned, if the only cities for the ZIP Code are vanity
cities. If the input city name is a vanity city name, and vanity city names are allowed,
the output city name can be a vanity city name if one is found on the database. If
vanity city names are not allowed, only primary or secondary city names are returned.
Calling C1CTYLKx
When you call C1CTYLKx, you must pass a ZIP Code, a city and state, or all of the
above. In addition, you can set the Vanity City flag to “X” if you want to allow vanity
city names to be returned. Finally, there is also a function code that should be set to
“E” when making the last call to C1CTYLKx to have C1CTYLKx close its open files.
This should be done after the last match attempt has been made, but before
terminating the calling program.
A COBOL copy member called CSPRM is supplied with the CODE-1 Plus software.
Please use this copy member when calling C1CTYLKx.
A sample driver, SMPLCKP, is distributed with the software. This sample driver calls
the CICTYLKB program.
Working With CODE-1 Plus
483
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
For CICS, the logic is identical except for the call:
CALL C1CTYLKC’ USING DFHEIBLK
DFHCOMMAREA
CS-PRM-DATA
Calling from an IMS Application
If you are calling C1CTYLKP from an IMS application, please include the PCB’s as
calling parameters, as shown below.
CALL 'C1CTYLKP' USING CS-PRM-DATA
IO-PCB
G1CPCNY-PCB
G1CPCTY-PCB
G1CPDTL-PCB
G1CPLCL-PCB
G1CPCNM-PCB
G1CPZIP-PCB
Your application can use the PSB shown below to define the PCB's presented above:
*
*
*
COUNTY DATA BASE
PCB
TYPE=DB,NAME=G1CPCNY,PROCOPT=GO,KEYLEN=5
SENSEG NAME=CNYSEG,PARENT=0
*
*
*
CITY DATA BASE
PCB
TYPE=DB,NAME=G1CPCTY,PROCOPT=GO,KEYLEN=2
SENSEG NAME=CTYSEG,PARENT=0
*
*
*
LOCALITY DETAILS DATA BASE
PCB
TYPE=DB,NAME=G1CPDTL,PROCOPT=GO,KEYLEN=2
SENSEG NAME=DTLSEG,PARENT=0
*
*
*
LOCALITY HEADER DATA BASE
PCB
TYPE=DB,NAME=G1CPLCL,PROCOPT=GO,KEYLEN=2
SENSEG NAME=LCLSEG,PARENT=0
*
*
*
CITY NAME DATA BASE
PCB
TYPE=DB,NAME=G1CPCNM,PROCOPT=GO,KEYLEN=4
SENSEG NAME=CNMSEG,PARENT=0
*
*
*
ZIP INDEX DATA BASE
PCB
TYPE=DB,NAME=G1CPZIP,PROCOPT=GO,KEYLEN=1
SENSEG NAME=ZIPSEG,PARENT=0
*
*
*
LINE OF TRAVEL DATA BASE
PCB
TYPE=DB,NAME=G1CPLOT,PROCOPT=GO,KEYLEN=2
SENSEG NAME=LOTSEG,PARENT=0
*
PSBGEN PSBNAME=SMPLCLKP,LANG=COBOL,CMPAT=YES
END
484
Software Release 4.0.0/March 2015
Calling C1CTYLKx
10
The C1CTYLKx Call Area
The following table shows you a map of the 14,523-byte C1CTYLKx call area.
NOTE: A copybook, called CSPRM, of this area is provided on your installation
tape.
Table 2: The C1CTYLKx Call Area (Part 1 of 5)
Position
Name
Length
Contents
1-5
CS-PRM-ZIPI
5
The input ZIP Code.
6-105
CS-PRM-CSTI
100
The input city and state.
106
CS-PRM-FNC
1
The input function code. Leave this blank for
a match call, set this to E for the final call.
107
CS-PRM-VANITYCTY
1
The vanity city name flag. If you want
C1CTYLKx to return vanity city names, set this
to X. Otherwise, when C1CTYLKx matches a
vanity city, it will return the primary or
secondary city name.
108-117
CS-PRM-DBL
10
Database library name (AS/400 specific).
118-150
Reserved
33
151
CS-PRM-GRC
1
The general return codes for the match
attempt. One of the following codes is
returned:
• Blank — Match was successful.
• A — The original ZIP Code was altered to
match a single-ZIP city.
• B — Insufficient information for a match.
• D — City-state mismatch (different
spelling found, or city-state was a vanity
name and vanity matching was not
allowed, or city-state did not match ZIP
Code).
• E — End of job encountered, so the job was
terminated.
• L — The original ZIP Code was altered to
be the lowest ZIP Code of the matched
city's ZIP Code range. This is an unreliable
answer.
• M — Multiple matches on city-state.
• X — CODE-1 Plus master file has expired;
processing aborted.
• Z — ZIP Code not found in the database.
Working With CODE-1 Plus
485
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
Table 2: The C1CTYLKx Call Area (Part 2 of 5)
Position
152
Name
CS-PRM-INPUT-ZIPRC
Length
1
Contents
The input ZIP Code return code. One of the
following codes is returned:
• Blank — Match was successful.
• B — Original ZIP Code no good, or blank.
• Z — ZIP Code not found in database.
153
CS-PRM-OUTPUTZIP-RC
1
The output ZIP Code return code. One of the
following codes is stored:
• A — The original ZIP Code was altered to
match a single-ZIP city.
• B — Original ZIP Code no good, or blank.
• C — Original ZIP Code was confirmed.
• L — The original ZIP Code was altered to
be the lowest ZIP Code of the matched
city's ZIP Code range. This is an unreliable
answer.
• Z — The ZIP Code was not found in the
database.
154
CS-PRM-INPUTCITY-RC
1
The input city return code. One of the
following codes is stored:
• Blank — Match was successful.
• B — Input city was blank, or no match
found.
155
CS-PRM-OUTPUTCITY-RC
1
The output city return code. One of the
following codes is stored:
• Blank — Match was successful.
• B — Input city was blank, or no match
found.
• D — City-state mismatch (different
spelling found, or city-state was a vanity
name and vanity matching was not
allowed, or city-state did not match ZIP
Code).
• M — Multiple matches on city-state.
486
156-170
Reserved
15
171-198
CS-PRM-CITYO
28
The output USPS full city name
199-211
CS-PRM-SHORTCITYO
13
The output USPS short city name.
212-213
CS-PRM-STATEO
2
The output USPS state abbreviation.
Software Release 4.0.0/March 2015
Calling C1CTYLKx
10
Table 2: The C1CTYLKx Call Area (Part 3 of 5)
Position
214
Name
CS-PRM-CTYPEO
Length
1
Contents
The output city type for the matched city
name. One of the following codes is stored:
• P — Primary
• S — Secondary
• V — Vanity.
215-220
CS-PRM-FINO
6
The output USPS finance number for the
matched city name.
221-226
CS-PRM-LL-LBO
6
The USPS last line number for the output city/
state/ZIP Code combination.
227-231
CS-PRM-ZIPO
5
The output USPS ZIP Code.
232
CS-PRM-SZIP
1
A code indicating whether there is more than
one ZIP Code in the input city. If a successful
match based on the input ZIP Code is
obtained, this code will not be set. One of the
following codes is stored:
• Blank — This city has more than one ZIP
Code.
• S — This city has only a single ZIP Code.
233
CS-PRM-NUM-ZIPENTRIES
3
The number of ZIP Codes that are in the
output table of ZIP Codes for the input city/
state.
The following CSP-ZIP CODE field occurs 999 times.
The previous CS-PRM-NUM-ZIP-ENTRIES field indicates the number of occurrences that are nonblank.
236-240 (1st
occurrence)
CSP-ZIP-CODE
5
The output USPS ZIP Code.
5231-5233
CS-PRM-NUM-CITYENTRIES
3
The number of cities that are in the output
table of cities for the input ZIP Code. The
maximum is 150 times.
The following fields occur 150 times.
The previous CS-PRM-NUM-CITY-ENTRIES field indicates the number of occurrences that are nonblank.
5234 (1st
occurrence)
CSP-CITYO
28
The output USPS city name.
5262 (1st
occurrence)
CSP-SHORT-CITYO
13
The output USPS short city name.
5275 (1st
occurrence)
CSP-STATEO
2
The output USPS state name.
Working With CODE-1 Plus
487
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
Table 2: The C1CTYLKx Call Area (Part 4 of 5)
Position
5277 (1st
occurrence)
Name
CSP-CTYPEO
Length
1
Contents
The output city type. One of the following
codes is stored:
• P — Primary
• S — Secondary
• V — Vanity.
5278 (1st
occurrence)
CSP-FINO
6
The output USPS finance number.
5284 (1st
occurrence)
CSP-LL-LBO
6
The output USPS last line number.
5290 (1st
occurrence)
CSP-ZIP-TABLE
5
The output USPS ZIP Code.
14384-14433
Reserved
50
The following fields are statistical fields for the audit trail.
488
14,434 14,442
CS-PRM-READ-CTY
9
The number of times a read request was
made for the cities in a ZIP Code logical file.
14,443 14,451
CS-PRM-READ-ZPX
9
The number of times a read request was
made for the ZIP Codes in a city logical file.
14,452 14,460
CS-PRM-READ-LCL
9
The number of times a read request was
made for the locality street directory logical
file.
14,461 14,478
Reserved
18
Software Release 4.0.0/March 2015
What is G1CPLKx?
10
Table 2: The C1CTYLKx Call Area (Part 5 of 5)
Position
Name
Length
Contents
14,479 14,487
CS-PRM-IO-CTY
9
The number of actual I/O calls that were
made to the cities in a ZIP Code logical file.
14,488 14,496
CS-PRM-IO-ZPX
9
The number of actual I/O calls that were
made to the ZIP Codes in a City logical file.
14,497 14,505
CS-PRM-IO-LCL
9
The number of actual I/O calls that were
made to the locality street directory logical
file.
14,506 14,523
Reserved
18
What is G1CPLKx?
The G1CPLKx callable module enables you to browse the contents of the
CODE-1 Plus database. G1CPLKC is a CICS application, and G1CPLKB is a batch
lookup program. The following is a list of the three areas that G1CPLKx uses:
•
G1CPLK-USER-REQUEST-AREA—controlled by the caller and contains all
information pertinent to the input request (150 bytes).
•
G1CPLK-USER-RESULT-AREA—accessed by the caller and should not be
modified. It contains all information necessary to produce the output (2,450
bytes).
•
G1CPLK-IPC-AREAS—used and accessed by G1CPLKx and should not be
modified (a minimum of 0 bytes and maximum of 10,000 bytes).
Calling G1CPLKC
Pitney Bowes provides the sample program G1CPDSM, which calls the G1CPLKC
callable routine for your platform. The following example is a sample from G1CPDSM.
For the most current version, please refer to G1CPDSM included on your installation
media.
01 WS-C1P-DBLOOK-PGM
PIC X(8) VALUE ’G1CPLKC’.
01 WS-MISC-LENGTHS.
05 WS-LENGTH-DBLOOK-AREAS
PIC S9(04) COMP.
.
01 WS-C1P-DBLOOK-AREAS COPY LOOKREQ.
.
MOVE LENGTH OF WS-C1P-DBLOOK-AREAS TO WS-LENGTH-DBLOOK-AREAS.
EXEC CICS LINK
PROGRAM (WS-C1P-DBLOOK-PGM)
COMMAREA (WS-C1P-DBLOOK-AREAS)
LENGTH (WS-LENGTH-DBLOOK-AREAS)
END-EXEC.
Working With CODE-1 Plus
489
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
To ensure the integrity of the database to be passed, initialize the following areas in
the calling program, along with any other fields accessing data to be passed:
•
Move spaces to G1CPLK-USER-REQUEST-AREA
•
Move LOW-VALUES to G1CPLK-MAX-RETURN-CONTROL.
NOTE: Your CODE-1 Plus installation media contains sample source code for
COBOL language only.
G1CPLK-USER-REQUEST-AREA
The following table shows you a map of the user input call area for G1CPLKx.
490
Software Release 4.0.0/March 2015
Calling G1CPLKC
10
Table 3: The G1CPLK-USER-REQUEST-AREA Call Area (Part 1 of 3)
Name
G1CPLKCOMMAND
Length
6
Contents
This field is required for all G1CPLKx calls, and specifies the
command executed by G1CPLKx. Type one of the following:
• AH — G1CPLKx returns all the apartments within a specific
house range. For each apartment, the results rows display the
address, ZIP Code range, apartment number ranges, ZIP
Codes, ZIP+4 Code ranges, carrier route codes, USPS record
types, and number of firms. You may execute this command
only immediately after an HS command.
• CM — G1CPLKx returns an alphabetical listing of all the cities
within the CODE-1 Plus database. For each city, the results row
displays the state abbreviation and the ZIP Code (or range of
ZIP Codes) valid for the city.
• CS — G1CPLKx returns an alphabetical listing of all the cities
within the specified state. For each city, the results row
displays the state abbreviation state and the ZIP Code (or range
of ZIP Codes) valid for the city.
• CZ — G1CPLKx returns an alphabetical listing of all cities
within the specified ZIP Code. For each city, the results row
displays the long city names, short city names, and city type.
• FM — G1CPLKx returns all firms within the specified street.
The result rows display 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. You may execute this command only immediately
after an HS or AH command.
• HS — G1CPLKx returns all the house ranges within the
specified street. In addition to even/odd house number ranges,
the results rows display ZIP and ZIP+4 Code ranges, carrier
routes, number of apartments, and number of firms. You may
execute this command only immediately after an SC or SZ
command.
• SC — G1CPLKx returns an alphabetical listing of all the streets
within the specified city. For each street, the results rows
display directionals (NE, SW, etc.), suffixes (ST, BLVD, etc.),
number of houses, number of firms, and ZIP Code ranges. You
may execute this command only immediately after a CM or CS
command.
Working With CODE-1 Plus
491
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
Table 3: The G1CPLK-USER-REQUEST-AREA Call Area (Part 2 of 3)
Name
Length
Contents
G1CPLK-COMMAND, continued
• ZC — G1CPLKx returns all ZIP Codes within a specified city. You
may execute this command only immediately after a CM or CS
command.
• SZ — G1CPLKx returns an alphabetical listing of all the streets
within the specified ZIP Code. For each street, the results rows
display directionals (NE, SW, etc.), suffixes (ST, BLVD, etc.),
number of houses, number of firms, and ZIP Code ranges.
• OPEN — G1CPLKx validates the database version and returns
the database “signature” of the CODE-1 Plus database
currently in use.
• QUIT — G1CPLKx closes the database and relinquishes all
work areas.
• * — Use the asterisk (*) to continue searching.
• BOT — Moves to bottom of current data list — all data positions.
• TOP — Moves to top of current data list — all data positions.
• DOWN — Moves down in data at same level (equivalent to *).
• UP — Moves up in data at same level.
• BACK — Returns to previous level. NOTE: If you use the BACK
command, CS and CZ display the Cities screen, because the
Cities screen cannot move back any farther.
• LOCAT — Generally positions the database inquiry to the first
entry that starts with <string>.
• ALIAS — Displays alias information in G1CPLK-ALIASINFO
field. You may execute this command only immediately after an
AH or FM command.
• RIGHT — Scrolls to right of firm/alias name field. You may
execute this command only immediately after an HS command.
• LEFT — Scrolls to original position for firm/alias name field.
You may execute this command only immediately after an HS
command.
G1CPLKSEARCHCRITERIA
105
This element specifies the various address components used in
the address search for the following commands:
• CM — Specify the leading characters of a city name. Blanks
cause the search to begin from the beginning of the database.
• CS — Specify the state abbreviation in the first two characters.
You can specify the leading characters of a city name.
• CZ — Specify a ZIP Code.
• HS — Specify the leading characters of a house range returned
in the results.
• SC — Specify the leading characters of a street name returned
in the results.
• SZ — Specify the leading characters of a street name returned
in the results.
492
Software Release 4.0.0/March 2015
Calling G1CPLKC
10
Table 3: The G1CPLK-USER-REQUEST-AREA Call Area (Part 3 of 3)
Name
Length
Contents
G1CPLK-MAXRETURNCONTROL
2 (x 6)
This field is required for all G1CPLKx calls (except OPEN) and
consists of six, 2-byte binary fields. Specify the number of data
rows you want returned by the current command. The maximum
is 25. You may access additional rows by subsequently invoking
G1CPLKx multiple times (using the “*” (asterisk) command).
Specify the count desired in the appropriate counter. There is one
counter for each of the address elements that can be returned.
The counters include the following: G1CPLKx-MAX-CITIES,
G1CPLKx-MAX-STREETS, G1CPLKx-MAX-ZIPS, G1CPLKx-MAXHOUSES, G1CPLKx-MAX-APTS, and G1CPLKx-MAX-FIRMS.
Populate the desired counter with a value and clear out the rest.
G1CPLK-SELECT
2
Specify the occurrence of data to be used for browsing further into
the database. For example,“02” for second city name to be used
for a street lookup.
Reserved
25
Working With CODE-1 Plus
493
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
G1CPLK-USER-RESULT-AREA
The following table shows you a map of the returned information area for G1CPLKx.
Table 4: The G1CPLK-USER-RESULT-AREA Call Area (Part 1 of 2)
Name
Length
Contents
G1CPLK-RMSG
79
This field contains any returned error or informational message.
G1CPLKRETURN-CODES
4
G1CPLKx returns one of the following codes:
• blank — The command was successful.
IN01 through IN09
Non-fatal error — An invalid command string was specified in
G1CPLK-COMMAND. The command may be invalid for one of two
reasons:
1
2
It is an illegal command string.
The requested command is not allowed from
this point in the database hierarchy.
• IN11 — Attempt to back up a level when none exists.
• LK01 — Fatal error — Invalid command requested.
• LK02 — Fatal error — Non-numeric SELECT FIELD passed.
• LK03 — Fatal error — MAX-RETURN-CONTROL counter was
out of range.
• LK04 — Fatal error — Incompatible database found.
• 0040 — Non-fatal error — ZIP Codes do not exist for the
selected item.
• 0041 — Non-fatal error — No firms exist for the selected item.
• 0042 — Non-fatal error — No houses/apartments exist for the
selected item.
• 0043 — Non-fatal error — No apartments exist for the selected
item.
• 0045 — Non-fatal error — No streets exist for the selected
item.
• 0050 — Information — Alias information was returned in the
G1CPLK-ALIASINFO field only. (Usually information is returned
to the table in G1CPLK-DATA-TABL.)
G1CPLK-IPCAREA-LENGTH
494
2
This is a 2-byte binary field, that contains the length of a
communication area used internally. Do not modify this field.
Software Release 4.0.0/March 2015
Calling G1CPLKC
10
Table 4: The G1CPLK-USER-RESULT-AREA Call Area (Part 2 of 2)
Name
G1CPLK-DBSIGNATURE
Length
95
Contents
The fields in this group item are populated as the result of the
“OPEN” command. The field contains the month and year string of
the vintage date of the database, as well as the expiration data.
This field includes the following subfields:
• G1CPLK-DB-DATE-STRING. This field contains the database
month and year string for a length of 15.
• G1CPLK-DB-PRODUCT. This field contains the software
product name and version for a length of 50.
• G1CPLK-DB-VINTAGE-DATE. This field contains the database
vintage date in the MM/DD/YY format for a length of 10.
• G1CPLK-DB-QUARTER-DATE. This field contains the database
quarterly vintage date in the MM/DD/YY format for a length of
10.
• G1CPLK-DB-EXPIRATION-DATE. This field contains the
database expiration date in the MM/DD/YY format for a length
of 10.
G1CPLK-LINEBREAKDOWN
79
Used by the caller to examine lines returned by the call. Once a
result set is returned, move each line here for further
examination.
G1CPLK-BEGCOUNT
4
The position of the first database element reserved relative to all
successive data in the database. For example, 40 for the 40th city
in Maryland.
NOTE: This field is packed decimal consisting of 7 nibbles of
binary-coded decimal digits and one nybble of sign.
G1CPLK-ENDCOUNT
4
The relative position of the last data elements available on the
database.
NOTE: This field is packed decimal consisting of 7 nibbles of
binary-coded decimal digits and one nybble of sign.
G1CPLKALIASINFO
80
The type and street name of the house range alias.
G1CPLKRESULT-DATA
96
Data identified by G1CPLKx as required by the user (through
G1CPLK-SELECT) to search further into the data.
G1CPLK-DATATABLE
25 (X 79)
25 occurrences of 79 bytes of data returned from the current
request. The number of occurrences of valid data depends on the
applicable G1CPLK-MAX-RETURN-CONTROL value.
Filler
32
Reserved.
Working With CODE-1 Plus
495
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
G1CPLK-IPC-AREAS-LENGTH
The following table shows a map of the last area used for G1CPLKx.
Table 5: The G1CPLK-IPC-AREAS LENGTH Call Area
Name
G1CPLK-IPCAREAS
496
Length
10,000
Contents
This area is reserved for inter-program communications.
(THIS FIELD MUST NEVER BE MODIFIED BY THE CALLER)
Software Release 4.0.0/March 2015
Calling G1CPLKB from an IMS Application
10
Calling G1CPLKB from an IMS Application
If you are calling G1CPLKB from an IMS application, include the following PCB’s as
calling parameters:
CALL "G1CPLKB" USING LOOKREQ
IO-PCB
G1CPCNY-PCB
G1CPCTY-PCB
G1CPDTL-PCB
G1CPPTR-PCB
G1CPLCL-PCB
G1CPCNM-PCB
G1CPZIP-PCB
G1CPLOT-PCB
G1CPXAA-PCB
G1CPXAS-PCB
G1CPCOM-PCB
Your application can use the PSB shown below to define the PCBs presented above:
*-------------------------------------------------------------*
SAMPLE IMS PSB TO BE USED WITH THE DB PRINT
*-------------------------------------------------------------*
*
COUNTY DATA BASE
*
PCB
TYPE=DB,NAME=G1CPCNY,PROCOPT=GO,KEYLEN=5
SENSEG NAME=CNYSEG,PARENT=0
*
*
CITY DATA BASE
*
PCB
TYPE=DB,NAME=G1CPCTY,PROCOPT=GO,KEYLEN=2
SENSEG NAME=CTYSEG,PARENT=0
*
*
LOCALITY DETAILS DATA BASE
*
PCB
TYPE=DB,NAME=G1CPDTL,PROCOPT=GO,KEYLEN=2
SENSEG NAME=DTLSEG,PARENT=0
*
*
LOCALITY POINTER DATA BASE
*
PCB
TYPE=DB,NAME=G1CPPTR,PROCOPT=GO,KEYLEN=2
SENSEG NAME=PTRSEG,PARENT=0
*
*
LOCALITY HEADER DATA BASE
*
PCB
TYPE=DB,NAME=G1CPLCL,PROCOPT=GO,KEYLEN=2
SENSEG NAME=LCLSEG,PARENT=0
*
*
CITY NAME DATA BASE
*
PCB
TYPE=DB,NAME=G1CPCNM,PROCOPT=GO,KEYLEN=4
SENSEG NAME=CNMSEG,PARENT=0
*
*
ZIP INDEX DATA BASE
*
PCB
TYPE=DB,NAME=G1CPZIP,PROCOPT=GO,KEYLEN=1
SENSEG NAME=ZIPSEG,PARENT=0
*
*
LINE OF TRAVEL DATA BASE
*
PCB
TYPE=DB,NAME=G1CPLOT,PROCOPT=GO,KEYLEN=2
SENSEG NAME=LOTSEG,PARENT=0
*
*
*
*
CITY NAME DATA BASE USING
SECONDARY INDEX MADE FROM CITY NAME
PCB
TYPE=DB,NAME=G1CPCNM,PROCOPT=GO,KEYLEN=32,
PROCSEQ=G1CPXAA
SENSEG NAME=CNMSEG,PARENT=0
*
*
Working With CODE-1 Plus
X
CITY NAME DATA BASE USING
497
10
Calling C1PRPT, C1CTYLKx, or G1CPLKx
*
*
SECONDARY INDEX MADE FROM STATE CODE AND CITY NAME
PCB
TYPE=DB,NAME=G1CPCNM,PROCOPT=GO,KEYLEN=34,
PROCSEQ=G1CPXAS
SENSEG NAME=CNMSEG,PARENT=0
*
*
*
X
COMM AREA (TEMP STORAGE) DATA BASE
PCB
SENSEG
SENSEG
SENSEG
TYPE=DB,NAME=G1CPCOM,KEYLEN=16,PROCOPT=PA
NAME=LTERMSEG,PARENT=0,PROCOPT=PA
NAME=TYPESEG,PARENT=LTERMSEG,PROCOPT=PA
NAME=QUEUESEG,PARENT=TYPESEG,PROCOPT=A
*
PSBGEN PSBNAME=psbname,LANG=COBOL,CMPAT=YES
END
498
Software Release 4.0.0/March 2015
CHAPTER 11
Using LACSLink
This chapter introduces LACSLink. It describes what LACSLink is and does, its features
and benefits, and what is involved in using LACSLink.
NOTE: 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.
What is LACSLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What are the Benefits of LACSLink?. . . . . . . . . . . . . . . . . . . . . . .
Who is Eligible to Use LACSLink?. . . . . . . . . . . . . . . . . . . . . . . . .
How Does LACSLink Work?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the LACSLink Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LACSLink Processing Requirements . . . . . . . . . . . . . . . . . . . . . .
How Do I Install the LACSLink Option? . . . . . . . . . . . . . . . . . . . .
How Do I Install the LACS Database? . . . . . . . . . . . . . . . . . . . . . .
Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
z/OS/IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Do I Activate LACSLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the CODE-1 Plus GUI to Activate LACSLink . . . . . . . .
Using Batch Processing to Activate LACSLink . . . . . . . . . . .
Activating LACSLink in Interactive Mode . . . . . . . . . . . . . . . .
Activating LACSLink in Callable Mode . . . . . . . . . . . . . . . . . .
LACSLink Processing Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LACSLink Information on USPS Form 3553. . . . . . . . . . . . . . . . .
Seed Record Violations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What If My Mailing Generates a Seed Violation? . . . . . . . . . . . . .
LACSLink Seed Record Reporting . . . . . . . . . . . . . . . . . . . . .
Obtaining a LACSLink License . . . . . . . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
500
500
501
501
502
502
502
503
503
504
506
507
507
508
510
512
512
515
517
517
517
518
518
519
499
11
Using LACSLink
What is LACSLink?
LACSLink is a CODE-1 Plus feature that allows users to implement the Locatable
Address Conversion System (LACS) service offered by the USPS. 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, but in some instances
conversions may result in the renaming or renumbering of existing city-style
addresses.
NOTE: The USPS regulations require LACSLink processing for CASS certification.
What are the Benefits of LACSLink?
LACSLink provides the following benefits to those who use it:
500
•
Ensures compliancy with USPS CASS regulations. LACSLink processing is a USPS
CASS requirement.
•
Ensures preparedness 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.
Software Release 4.0.0/March 2015
What is LACSLink?
11
Who is Eligible to Use LACSLink?
The LACS service is available only through NCOA licensees. This service is offered as
a stand-alone process or as a back-end process with the NCOA service to ensure a
high quality mailing list. All CODE-1 Plus customers operating in the United States
are eligible to use LACSLink.
NOTE: 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?
LACSLink works in a series of two steps: input address information is standardized to
conform with Postal Service requirements including the ZIP+4 Code, and then an
attempt is made to match the address against the LACS file. If an exact match is made
with the old address information on the LACS file, the address is updated accordingly.
After LACSLink processing takes place and a match is found, you will receive the
following information from CODE-1 Plus:
•
the original input address from the mailer
•
the input address, standardized and appended with the ZIP+4 Code, if possible
•
a standardized new address when the standardized input address matches the old
address on the LACS file
•
a National Delivery Index (NDI) report, which includes a breakdown of
deliverable address information.
If no match is found, you will receive the following information from CODE-1 Plus:
•
the original input address
•
the standardized ZIP+4 coded version of the input address
•
PS Form 3553
•
NDI report.
Working With CODE-1 Plus
501
11
Using LACSLink
Using the LACSLink Option
The following information discusses the explanation and use of LACSLink.
LACSLink Processing Requirements
The LACSLink security file is required for LACSLink processing. In z/OS1, there are two
versions of this file:
•
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. This VSAM file, an 80-byte file called
lacssud.80E, is packaged along with a new jcl called LLSUDLOD, to create the
VSAM version of the LACSLink security file. Also delivered is a revised C1PCSD jcl
that defines 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.
502
Software Release 4.0.0/March 2015
Using the LACSLink Option
11
How Do I Install the LACS Database?
In this section, we provide platform-specific instructions for installing your LACSLink
database. Please note that the LACSLink database has a 120-day expiration cycle.
Databases expire on the following schedule:
Table 1: 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 LACSLink Database CD-ROM or
downloaded llk.db from our website. Follow these steps to load the LACSLink
Database:
NOTE: For files downloaded from our web site, 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.
Working With CODE-1 Plus
503
11
Using LACSLink
1. Load the database from the database media. If loading from CD-ROM, place the
Database CD-ROM into your CD-ROM drive.
2. 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.
3. 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 will use this
value for the destination location of the database files.
4. If the load completed without errors, you may proceed and run your CODE-1 Plus
jobs. However, if there were errors, please contact Technical Support.
Unix
Perform the following steps to install your LACSLink database from the CD-ROM.
1. Place the CD in the drive and close the drive door. If your system auto-mounts,
go to Step 4 now.
504
Software Release 4.0.0/March 2015
Using the LACSLink Option
11
2. Issue the appropriate mount command to indicate that the CD device is a file
system:
mount
/dev/xxx
...where xxx is the CD-ROM device name.
3. 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 CD-ROM device on your system.
NOTE: Your system must allow CDs created under the ISO 9660 format to be
mounted as a file system.
4. Issue the appropriate source command to setup the environment:
. ./setup (for Bourne shells)
source ./setup.csh (for C shells)
5. Execute the script for installing the database by typing the following command:
$G1DIR/g1bin/installdb
or
cd to $G1DIR/g1bin and type installdb
Working With CODE-1 Plus
505
11
Using LACSLink
6. Select CODE-1 Plus from the menu options, and a sub-menu will appear listing
your file install options.
7. 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.
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.
506
Software Release 4.0.0/March 2015
Using the LACSLink Option
11
NOTE: Please refer to the IVPFILE JCL in the Installation Library on the product
tape for examples of what DD names are required.
NOTE: 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.
VMS
To load the LACSLink database on VMS, follow these steps:
1. Change the directory (set the default) to the CODE-1 Plus batch subdirectory, for
example:
$set def device:[c1p290.batch]
2. Run the LACSLink Database load script, C1LACSLD.com, with the following
command:
$@C1LACSLD
3. Enter the source, target device, and directory names when prompted. The load
program will load the LACSLink file in the specified output area.
How Do I Activate LACSLink?
There are four ways in which you can activate LACSLink processing:
•
With the CODE-1 Plus GUI
•
In batch processing, using the LACS parameter record
•
By entering “LACS” in the command line for Interactive processing
•
By calling the CODE-1 Plus matcher from a user-written application and setting
the LACSLink indicator in the P9IN area.
Working With CODE-1 Plus
507
11
Using LACSLink
NOTE: CODE-1 Plus customers should be aware that batch jobs running with
DPV Split, LACSLink, and SuiteLink may require up to 377M of GETVIS.
Using the CODE-1 Plus GUI to Activate LACSLink
To activate LACSLink using the CODE-1 Plus GUI, go to Options>Define LACS
Parameter from the Primary Window to bring up the Define LACS Processing
Indicator screen. This screen will allow you to determine how you want LACS
processing performed.
The table below describes the entries on the Define LACS Processing Indicator dialog
box.
Table 2: Options on the Define LACS Processing Indicator Dialog Box
This option...
And maps to this
parameter...
Performs this function...
No LACS
Processing
Tells CODE-1 Plus not to perform LACS processing.
LACS
Perform ZIP+4
Match before LACS
Perform the ZIP+4 coding process and only call
LACSLink if the ZIP+4 process returns a LACS
indicator.
LACS
• Z — Perform the ZIP+4 processing prior to
LACSLink.
508
Software Release 4.0.0/March 2015
Using the LACSLink Option
11
Table 2: Options on the Define LACS Processing Indicator Dialog Box
This option...
Return Limited
LACS Results
Performs this function...
This option allows LACSLink to return output
Standardized Address Field, City Field, and State
Field instead of the LACS Converted Address
information:
And maps to this
parameter...
LACS
• 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
• R — Invoke full LACSLink subsystem processing.
Provides all LACS converted address information
to the output standardized address and parsed
element fields.
Per CASS Regulations, the output ZIP, ZIP+4 Code,
and the Delivery Point Barcode must be maintained
for the LACS Converted Address.
Stop Processing on
a Seed
This option allows LACSLink to stop batch jobs when
a false-positive (seed record) has been
encountered:
LACS
• S — Shuts down CODE-1 Plus processing when a
false-positive (seed record) is encountered.
• 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.
Working With CODE-1 Plus
509
11
Using LACSLink
Table 2: Options on the Define LACS Processing Indicator Dialog Box
This option...
And maps to this
parameter...
Performs this function...
Suppress 99 Code
for Seed
Tells CODE-1 Plus to produce the “99” return code
when a false-positive (seed record) has been
encountered.
LACS
• Y — Do not produce “99” return code for LACS
seed record processing.
• N — LACS seed record processing results in “99”
return code.
NOTE:
LACSLink Memory
Module Size
Indicator
An “S” in pos. 10 overrides this option.
This option allows you to specify size of LACSLink
module.
LACS
• Blank — LACS process will be using Medium
memory model (default).
• 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).
Using Batch Processing to Activate LACSLink
To activate LACSLink using batch processing, create the LACS parameter record as
shown below:.
Table 3: 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:
Required.
Default is
blank.
• Z — Perform the ZIP+4 processing prior to
LACSLink.
510
Software Release 4.0.0/March 2015
Using the LACSLink Option
11
Table 3: Fields on the LACS Parameter (Part 2 of 2)
Position
10
Field Name
TERMINATE LACS
Description
This option allows LACSLink to stop batch jobs
when a false-positive (seed record) has been
encountered:
Comments
Optional
Default: W
• S — Shuts down CODE-1 Plus processing
when a false-positive (seed record) is
encountered.
• 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:
Optional
Default: R
• 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
• R — Invoke full LACSLink subsystem
processing. Provides all LACS converted
address information to the output
standardized address and parsed element
fields.
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.
Required
• Blank — LACS process will be using
Medium memory model (default).
• 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).
Working With CODE-1 Plus
511
11
Using LACSLink
NOTE: Positions 52-54 and 56-58 of the AM2OUT parameter record store
return codes that resulted from LACSLink processing.
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.
NOTE: 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.
512
Software Release 4.0.0/March 2015
Using the LACSLink Option
11
NOTE: You can find the P9COMM copybook (a combination of P9IN, P9OUT, and
P9AUDIT for use with CICS) with other copybooks delivered from Group-1
Software.
To activate LACSLink in callable mode, call the CODE-1 Plus matcher and set the
LACSLink indicator as shown below.
Table 4: 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.
Working With CODE-1 Plus
513
11
Using LACSLink
The following table describes the LACSLink fields in the P9OUT call area structure.
Table 5: 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.
12161217
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.
514
Software Release 4.0.0/March 2015
Using the LACSLink Option
11
Table 5: The P9OUT Output Call Area
Position
Field Name
12181226
Length
P9OLACSLINK-DBINFO
9
Comments
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.
12271239
P9OLACSLINKVERSION
13
Version number of the LACSLink database,
LACSLink Processing Codes
The following return codes indicate the success of LACS processing:
Table 6: 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 was encountered,
LACS function was 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
Working With CODE-1 Plus
515
11
Using LACSLink
Table 6: LACS Processing Return Codes
Return Code Name
Return Code
Description
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
LACS_ERROR_STMEM
-16
Error getting st. member
LACS_TEST_BREAK
-17
Break for test
:
Table 7: LACS Return Codes
Return Code Name
516
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.
Software Release 4.0.0/March 2015
Seed Record Violations
11
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
Seed Record Violations
This section provides information on LACSLink seed record violations.
Introduction
Seed records are artificially manufactured addresses provided as part of the LACSLink
option. The USPS has put in place security measures to ensure mailers using LACSLink
processing do not use these applications to generate mailing lists. If the USPS
identifies a mailer as repetitively generating false-positive violations, the USPS may
direct Pitney Bowes to invalidate their license. Towards that end, the USPS has
created and monitors addresses that generate a false-positive result. The USPS
requires Pitney Bowes to report any organization generating a false-positive result
during LACSLink processing. If you generate a false-positive result, CODE-1 Plus
generates an error message and the security file becomes invalidated. CODE-1 Plus
continues to process your mailing file; however, LACSLink processing is flagged as
unavailable. The mailing that generated the false-positive result is identified as not
CASS certified.
NOTE: If you wish to test your file using seed records, go to the Rapid Information
Bulletin Board System (RIBBS) Web site at http://ribbs.usps.gov. LACSLink, and
click the LACSLINK_PUBLICSEED.txt file to see a list of seed records for
LACSLink.
Working With CODE-1 Plus
517
11
Using LACSLink
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 do two things:
1. Report the seed record match to Pitney Bowes.
2. Get a new license key to turn LACS back on.
You can accomplish both tasks by going to the Pitney Bowes Web site. Details of how
to do so are provided below.
LACSLink Seed Record Reporting
For all forms of processing with CODE-1 Plus, if you encounter a seed, it must be
reported to the USPS. We have made available via the Pitney Bowes site, http://
www.g1.com/support, a method in which to report all seeds to the USPS. When you
go through our Support site to report the seed violation, you will also be given a
reactivation license or key to be applied to restart the function in which the violation
occurred. To access the Seed Reporting/License area of our Support site:
If for some reason
you cannot access
the Pitney Bowes
website, you can
also report seed
violations to
Technical Support
at 800-367-6950.
1. Login to the Pitney Bowes Support site, http://www.g1.com/Support.
NOTE: If you do not know your User ID and password for the Support website,
please go to the Login screen (http://www.g1.com/support/login.asp) and select
the option to have it e-mailed to you. When you enter your e-mail address as
instructed, it must be an exact match to our customer database. If a successful
match is found, your User ID and password will be e-mailed to the address entered.
2. Go to My Products.
3. Select CODE-1 Plus.
4. Select the appropriate platform with which you are running CODE-1 Plus.
5. Under the Database section, you will see listings for: Delivery Point Validation
(DPV) and LACSLink. For each, there will be a View Available Downloads link under
the LICENSE column of the Database table. Click this View Available Downloads
link for the database of the function that the violation was incurred.
You have now reported your seed record violation and you must obtain a new key to
continue using LACSLink processing.
518
Software Release 4.0.0/March 2015
Seed Record Violations
11
Obtaining a LACSLink License
To obtain a replacement LACS License File from the Pitney Bowes Web site,
customers must attach the associated LACSSEED file. In turn, Pitney Bowes will
supply and replace the LACS License File and report the associated Seed Record
information to the USPS.
To obtain a LACSLink Key, you will need to select via the license form, one of the
following:
1. Batch. 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.
Table 8: 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
LACSKEY
NOTE: Replace “yourhlq” with your own high-level
qualifier.
VMS
The directory where your environment variable
LACSKEY is set. The default is device:[<TARGET
AREA>.DATA], where “TARGET AREA” is the directory
where you installed CODE-1 Plus).
LACSLK
NOTE: 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.
Working With CODE-1 Plus
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.
519
11
Using LACSLink
2. Interactive. If you encounter a LACSLink Seed Violation using the MatcherInquiry/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. See table Table 8 on page 519 for more
information.
b.
The Seed File contains all of the necessary information for reporting a falsepositive record. You must create this file using any text editor, reporting
the following information in the specified record position:
Table 9: LACSLink SEED File 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
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.
NOTE: 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.
520
Software Release 4.0.0/March 2015
CHAPTER 12
Using SuiteLink
This chapter introduces SuiteLink. It describes what SuiteLink is and does, how it’s
used within CODE-1 Plus, and its benefits.
NOTE: 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.
What is SuiteLink? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What are the Benefits of SuiteLink? . . . . . . . . . . . . . . . . . . . . . . .
Who is Eligible to Use SuiteLink? . . . . . . . . . . . . . . . . . . . . . . . . .
How Does SuiteLink Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the SuiteLink Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How do I Install the SuiteLink Option? . . . . . . . . . . . . . . . . . . . . .
How do I Install the SuiteLink Database?. . . . . . . . . . . . . . . . . . .
How Do I Activate SuiteLink?. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DD Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SuiteLink Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input and Output Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SuiteLink Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working With CODE-1 Plus
522
522
523
523
524
524
524
529
536
536
537
537
521
12
Using 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.”
NOTE: SuiteLink cannot be used as part of a standalone process; it must be used
in conjunction with CODE-1 Plus.
NOTE: The USPS regulations require SuiteLink processing for CASS certification.
NOTE: 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.
522
Software Release 4.0.0/March 2015
What is SuiteLink?
12
Some of the benefits available to CODE-1 Plus customers through SuiteLink
processing are described below.
•
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.
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.
NOTE: 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:
•
Working With CODE-1 Plus
–
Firm name
–
Valid ZIP code
–
Valid ZIP+4 code
–
Primary number exists
A match has been made to a high-rise default record
523
12
Using SuiteLink
•
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.
Using the SuiteLink Option
The following information discusses the installation and use of SuiteLink.
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.
How do I Install the SuiteLink Database?
In this section, we provide platform-specific instructions for installing your SLKDB
database. Please note that the SLKDB database has a 120-day expiration cycle.
Databases expire on the following schedule:
Table 1: SuiteLink Database Expiry Cycle
Database Month
524
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
Software Release 4.0.0/March 2015
Using the SuiteLink Option
12
Table 1: SuiteLink Database Expiry Cycle
Database Month
Expiration
October
January 31
November
February 28
December
March 31
In addition, for Windows, Unix, and VMS, 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 an BSLKD database CD-ROM. Follow
these steps to load the SLKDB database:
NOTE: 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. Load the database from the database media. If loading from CD-ROM, place the
database CD-ROM into your CD-ROM drive.
2. 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.
Working With CODE-1 Plus
525
12
Using SuiteLink
3. Select the SuiteLink radio button 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 SLKDB 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.
4. If the load completed without errors, you may proceed and run your CODE-1 Plus
jobs. However, if there were errors, please contact Technical Support.
Unix
Perform the following steps to install your SuiteLink database from the DVD.
NOTE: Our DVDs are formatted as UDF with Rockridge extension.
1. Place the DVD in the drive and close the drive door. If your system auto-mounts,
go to Step 4 now.
526
Software Release 4.0.0/March 2015
Using the SuiteLink Option
12
2. 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.
3. 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.
NOTE: Your system must allow DVDs created under the ISO 9660 format
to be mounted as a file system.
4. Issue the appropriate command to setup the environment. Do the following:
> cd <target directory>/c1p/bin
> . ./setup (for Bourne shells)
source ./setup.csh (for C shells)
5. Execute the script for installing the database by typing the following command:
$G1DIP/bin/installdb
or
cd to $G1C1P/bin and type installdb
Working With CODE-1 Plus
527
12
Using SuiteLink
6. On the CODE-1 Plus database menu, select option #6 for SuiteLink.
7. Follow the prompt to specify input and output locations and install the selected
database.
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.
528
Software Release 4.0.0/March 2015
Using the SuiteLink Option
12
VMS
To load the SuiteLink database on VMS, follow these steps:
1. Change the directory (set the default) to the CODE-1 Plus batch subdirectory, for
example:
$set def device:[c1p290.batch]
2. Run the SuiteLink Database load script, C1SLKLDB.com, with the following
command:
$@C1SLKLDB
Enter the source, target device, and directory names when prompted. The load
program will load the SLKDB the specified output area.
How Do I Activate SuiteLink?
There are four ways in which you can activate SuiteLink processing:
•
With the CODE-1 Plus GUI
•
By using the STELNK parameter record for batch processing
•
By entering “SUITE” in the command line for Interactive processing
•
By calling the CODE-1 Plus matcher from a user-written application and setting
the SuiteLink indicator in the P9IN area.
NOTE: CODE-1 Plus customers should be aware that batch jobs running with
DPV Split, LACSLink, and SuiteLink may require up to 377M of GETVIS.
Working With CODE-1 Plus
529
12
Using SuiteLink
Using the CODE-1 Plus GUI to Activate SuiteLink
To activate SuiteLink using the CODE-1 Plus GUI, go to Options>Define Suite Link
Parameter from the Primary Window to bring up the Define the SuiteLink Parameter
screen. This screen will allow you to determine how you want SuiteLink processing
performed.
The table below describes the entries on the Define SuiteLink Parameter dialog box.
Table 2: Options on the Define SuiteLink Parameter Dialog Box (Part 1 of 2)
This option...
Enable SuiteLink
530
And maps to this
parameter...
Performs this function...
Tells CODE-1 Plus to perform SuiteLink processing.
STELNK
Software Release 4.0.0/March 2015
Using the SuiteLink Option
12
Table 2: Options on the Define SuiteLink Parameter Dialog Box (Part 2 of 2)
This option...
SuiteLink Error
Indicator
Performs this function...
Determine s whether to shut down when SuiteLink
reports an error.
And maps to this
parameter...
STELNK
• 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”.
• 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”.
SuiteLink Memory
Model Flag
This option allows you to specify size of SuiteLInk
memory module.
STELNK
• Blank — SuiteLink process will use the Medium
memory model (default.)
• 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.)
Working With CODE-1 Plus
531
12
Using SuiteLink
Activating SuiteLink in Batch Mode
To activate SuiteLink in batch mode, create the STELNK parameter record as shown
below:
Table 3: Fields on the STELNK Parameter
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.
Optional
• 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”.
• 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”.
10
SuiteLink Memory
Model Flag
This option allows you to specify size of
SuiteLInk memory module.
Required
• Blank — SuiteLink process will use the
Medium memory model (default.)
• 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:
Optional
• A — Business name matched.
• 00 — Business name not matched.
532
Software Release 4.0.0/March 2015
Using the SuiteLink Option
12
Table 3: Fields on the STELNK Parameter
Position
16-18
Field Name
SuiteLink Match Code
Location
Description
Location for SuiteLink match code:
Comments
Optional
• A — Matched
• 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:
Optional
• 1 — Exact match
• 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.
Optional
• I — Include secondary information
from SuiteLink on the output address
line.
• 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.
Optional
• I — Include the invalid input
secondary information.
• E — Exclude the invalid input
secondary information.
• blanks — Defaults to I.
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.
Working With CODE-1 Plus
533
12
Using SuiteLink
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.
NOTE: 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
534
•
Determine whether an expired SuiteLink database can cause a job to terminate
•
Set the Small Memory Model flag.
Software Release 4.0.0/March 2015
Using the SuiteLink Option
12
Table 4: The P9IN Input Call Area for SuiteLInk
Position
29
Name
P9ISTE
Length
1
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”.
• 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
1
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).
• Y — Bypass SuiteLink database expiration processing.
31
P9ISTESMM
1
This field controls the SuiteLink memory module size to
use for processing.
• Blank — DPV process will be using Medium memory
model (default).
• 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).
NOTE: See positions 1863-1878 and 2121-2170 of the P9OUT callable area for
SuiteLink output.
Working With CODE-1 Plus
535
12
Using SuiteLink
The output from the SuiteLink job posts as follows in the P9OUT call area:
Table 5: The P9OUT Output Call Area for SuiteLInk
Position
Name
1863
P9OSTELNK-RC
Length
Contents
SuiteLink return code:
2
• A — Business name matched.
• 00 — Business name not matched.
1864
P9OSTELNKMATCH-RC
SuiteLink match code:
1
• A — Matched
• B — Not matched
• C — Business name was all noise
• D — Highrise default record not found
• E — Database is expired.
1865
P9OSTELNKMATCH-FID
SuiteLink match fidelity:
1
• 1 — Exact match
• 2 — Acceptable match (one word not matched)
• 3 — Unacceptable match (more than one word not
matched)
1866
P9OSTELNKRLS-NUM
12
SuiteLink release number.
DD Names
DD names for SuiteLink include the following:
•
SLKDB
SuiteLink Return Codes
The following return codes indicate the success of SuiteLink processing:
Table 6: SuiteLink Return Codes
Return Code
536
Description
00
No SuiteLink record match found
A
SuiteLink record match found
Software Release 4.0.0/March 2015
Using the SuiteLink Option
12
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 CASS 3553 report and the Control Reports are include SuiteLink information.
CASS 3553 Report
SuiteLink information has been added to the Qualitative Statistical Summary section
of the CASS 3553 report:
Control Reports
Line items for SuiteLink are on the Control Reports as follows:
SuiteLink Database version: March 2007, 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
nn.nn%
Working With CODE-1 Plus
537
12
538
Using SuiteLink
Software Release 4.0.0/March 2015
GLOSSARY
Alphabetic character
Alphanumeric
character
Any one of the letters A through Z (upper case and lower case).
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 double-byte coding
system, 2 bytes represent a character.
Character
Carrier code
Coded output file
Constant
Any letter, number or other symbol in the data character set that is part of the
organization, control, or representation of data.
A code assigned to each address on a mail carrier’s route.
Output file that contains processed records coded with ZIP+4 and/or carrier
route codes.
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.
Default value
A value supplied by the system that is used when no other value is specified by
the user.
Working With CODE-1 Plus
539
GL
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
Firm name
General delivery
A generic term for a set of related records treated as a unit.
The company name associated with an address.
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
Invalid ZIP Code
File
Job description
Job queue
Library
540
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.
Output file that contains addresses that have invalid ZIP Codes.
A set of characters that defines how the system handles a job.
A waiting list. In this case, a list of the jobs waiting for processing.
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.
Software Release 4.0.0/March 2015
GL
Leading zeros
Zeroes that are place-holders to the left of numbers that are right-aligned and smaller
than the specified field length.
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
Matching
algorithm
Member
Number of tries the system made to match the input address.
Program logic that controls address matching.
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
Parameter
Record
Record layout
Record position
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.
Data passed to or received from another program.
A collection of related data or words, treated as a unit, such as one name, address, and
telephone number.
Layout of a record, showing all the fields it contains along with each field's length,
type, and position in the record.
The position in a record where a field is located.
Working With CODE-1 Plus
541
GL
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.
Seasonal
Indicator
Uncoded output
file
ZIP Code
ZIP+4 Code
542
A 12-byte code indicating when mail can be delivered to a specific address.
Output file that contains processed records left uncoded with either ZIP+4 or carrier
route codes.
A 5-digit code identifying the post office or delivery station associated with an
address.
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.
Software Release 4.0.0/March 2015
INDEX
Numerics
5-digit ZIP Code
where to store on the output record, 221
A
Accessing Line of Travel, 323
Activating the Auxiliary File/Early Warning System File
Option, 371
ADDRDF parameter record
ADDRESS fields, 91, 92
ADDRESS FORMAT, 91
defined, 91
URBANIZATION NAME fields, 92
Address Correction
maximum
Z4 OUT parameter record, 218
Address correctness
maximum, 204
Address elements, 94
definition locations, 94
Address example
CMRA, 199
ADDRESS FORMAT field (ADDRDF), 91
Address line extraction module (EXTADDR2), 462
EXT2Parm, 462
Address Match Execution Statistics Report, 192
Address matching function (interactive environment)
Address Match Screen, 233
Address Stack Screen, 266
Delivery Sequence Footnotes Screen, 236
Dropped Information/Base Address Screen, 239
Expanded Return Codes Screen, 242
Geocoder Information Screen, 244
Match Settings Screen, 246
Multiple Elements Screen, 249
Parsed Elements Screen, 252
Return Codes Screen, 254
Statistics Screen, 262
Address Match Screen (Interactive), 233
Address Return Code
SA OUT parameter record, 200
Address Source Code
SA OUT parameter record, 202
Address Stack Screen, 266
Address with Apartment
SA OUT parameter record, 201
Address without Apartment
Working With CODE-1 Plus
SA OUT parameter record, 201
storage conditions, 201
Administration Sign-on Screen (Interactive), 294
AE OUT parameter record
APARTMENT DESIGNATOR, 95
BOX NUMBER, 95
defined, 94
DISPOSITION INDICATOR, 95
field-by-field, 94
HOUSE NUMBER, 94
LEADING DIRECTIONAL, 94
picture, 94
RR/HC NUMBER, 95
RR/HC ROUTE TYPE, 95
STREET NAME, 94, 95
SUFFIX, 95
Alias/Base Return Option
SA OUT parameter record, 203
Alias and Base street name output
table, 198
Alias and Base street names
defined, 197
Alias Return Code
SA OUT parameter record, 203
ALIAS RETURN CODE field (SA OUT), 203
Alias Type Code
SA OUT parameter record, 203
ALIAS TYPE CODE field (SA OUT), 203
Alphabetic Portion of LOT Code
LOTOUT parameter record, 181
Alternate city name, defined, 276
Alternate Sequence Code
LOTOUT parameter record, 181
AM2OUT parameter record
defined, 103
field-by-field, 103
HIGH RISE DEFAULT, 103
RURAL ROUTE DEFAULT, 103
street default flag, 105
AM OUT parameter record
ADDRESS PROBABLE CORRECTNESS CODE, 100
APARTMENT RETURN CODE, 99
defined, 97
DELIVERY SEQUENCE FILE FOOTNOTES, 101
DIRECTIONAL RETURN CODE, 98
field-by-field, 97
FIRM NAME MATCH SCORE, 100
FIRM NAME RETURN CODE, 99
GENERAL RETURN CODE, 98
OVERALL PROBABLE CORRECTNESS CODE, 100
STREET NAME MATCH SCORE, 100
SUFFIX RETURN CODE, 99
543
IX
Index
USPS RECORD TYPE CODE, 97
ANALYSIS-NORMALIZATION call area
defined (for C1ANZADR), 455
Analysis of Matched Records
REPORT parameter record, 192
ANALYSIS OF MATCHED RECORDS field (REPORT), 192
ANALYSIS-PARAMETERS call area
defined (for C1ANZADR), 455, 456
Apartment/PMB
SA OUT parameter record, 201
storage conditions, 202
Apartments at a House Range Screen (Interactive), 270
APO/FPO ZIP Codes, 130
AP OUT, 106
AP OUT parameter record
defined, 106
DROPPED PRIMARY CHARACTERS, 110
DROPPED SECONDARY CHARACTERS, 111
field-by-field, 106
Format of extra data in output record, 107
Location for additional input data, 108
NORM. PRIMARY ADDRESS LINE, 108, 109
NORM. SECONDARY ADDRESS LINE, 109
Normalization Type (No match), 112
Ascending/descending sequence, 322
Automation-based postal discounts, 123
AUXIL, 115
AUXIL0 parameter record
G1AUXBLD program, 115
AUXIL1, 115
AUXIL1 parameter record
G1AUXBLD program, 115
Auxiliary File
building in NT, 368
building in Unix, 368
building in z/OS/VSE/IMS, 368
building with EWS, 367
Auxiliary File Build (C1AUXBLD) Reports, 372
Auxiliary File Build Execution Log, 372
Auxiliary File Build Report, 372
Auxiliary File processing
introduction, 365
Auxiliary File Reporting in the CODE-1 Plus Matcher, 373
Auxiliary File Reports, 372
Auxiliary Reference File, 115
AUXIL Parameter, 369
AUXIL parameter record
Field-by-Field, 370
B
BLANK UNUSED ADDRESS LINES
SA OUT parameter record, 201
Block Size
FILEDF parameter record, 163
544
BLOCK SIZE field (FILEDF), 163, 377
Browsing database
from CICS application, 490
Building
RDI file, 355
Building the Auxiliary File with the Early Warning System,
367
Building Your Auxiliary File
in NT, 368
in Unix, 368
in z/OS/VSE/IMS, 368
Bypassing an expired database, 116
BYPEXP parameter record
defined, 116
C
C1ANZADR callable module
defined, 455
C1AUXBLD Utility Program, 367
C1BM00XL driver program
L CODE parameter record, 177
C1BMCOK output file, 159
C1BMIZP output file, 159
C1BMNAM input file, 159
C1BMNCO output file, 159
C1BMZP4 output file, 159
C1CTYLKP callable module
calling, 483
defined, 481
output results, 483
passing city and state, 482
passing ZIP Code and city/state, 482
passing ZIP Code only, 482
vanity city name indicator, 483
C1CTYLKP call area
CSP-CITYO, 487
CSP-CTYPEO, 488
CSP-FINO, 488
CSP-LL-LBO, 488
CS-PRM-CITYO, 486
CS-PRM-CSTI, 485
CS-PRM-CTYPEO, 487
CS-PRM-FINO, 487
CS-PRM-FNC, 485
CS-PRM-GRC, 485
CS-PRM-INPUT-CITY-RC, 486
CS-PRM-INPUT-ZIP-RC, 486
CS-PRM-IO-FCZ, 489
CS-PRM-IO-FLD, 489
CS-PRM-IO-FZC, 489
CS-PRM-LL-LBO, 487
CS-PRM-OUTPUT-CITY-RC, 486
CS-PRM-OUTPUT-ZIP-RC, 486
CS-PRM-READ-FCZ, 488
Software Release 4.0.0/March 2015
IX
CS-PRM-READ-FLD, 488
CS-PRM-READ-FZC, 488
CS-PRM-STATEO, 486
CS-PRM-SZIP, 487
CS-PRM-ZIPI, 485
CS-PRM-ZIPO, 487
CSP-SHORT-CITYO, 487
CSP-STATEO, 487
C1DBRDI
RDI utility program
definition, 356
C1MATCHx, 463
C1MATCHx address matching, 398
alternate memory modules, 190
C1MATCHx call areas
P9AUDIT, defined, 403
P9AUDIT, mapped, 443, 444
P9IN, defined, 403
P9IN, mapped, 405
P9OUT, defined, 403
P9OUT, mapped, 414
C1PRPT, 454, 463
C1PRPT callable module
defined, 468
C1PRPT call area
mapped, 471
RP-BMOARC, 472, 473, 474, 475, 476
RP-CT-AMA, 478
RP-CT-APO, 478
RP-CT-BYP, 478
RP-CT-COK, 478
RP-CT-GOV, 478
RP-CT-IZP, 478
RP-CT-MIL, 478
RP-CT-NAM, 477
RP-CT-NCO, 478
RP-CT-PRC, 478
RP-CT-VAL, 478
RP-DATE, 480
RP-HEADER, 480
RP-INP-ZP4, 477
RP-INP-ZP4-VAL, 477
RP-LCDNEW, 477
RP-RETURN-CODE, 471
RP-RPANMR, 479
RP-RPCR3D, 479
RP-RPCRLC, 479
RP-RPCRST, 479
RP-RPSM3D, 480
RP-RPSMLC, 480
RP-RPSMST, 480
RP-RPUPLO, 480
RP-RPZ43D, 479
RP-RPZ4LC, 479
RP-RPZ4ST, 479
Callable modules
defined, 398
sample batch program, 399, 454
Working With CODE-1 Plus
Callable subroutine
LTO10 callable subroutine, 323
Call areas
defined, 399
for C1ANZADR defined, 455
for C1CTYLKP, 485
for C1PRPT, 471
for G1CPLKP, 489
maps, defined, 399
P9AUDIT (for C1MATCHx) defined, 403
P9AUDIT (for C1MATCHx) mapped, 443
P9IN (for C1MATCHx) defined, 403
P9IN (for C1MATCHx) mapped, 405
P9OUT (for C1MATCHx) defined, 403
P9OUT (for C1MATCHx) mapped, 414
Unmatched data call area (for C1MATCHx) mapped,
444
Calling CODE-1 Plus
from your applications, 398
requirements for CICS, 444
Calling Z4CHANGE
from your own driver, 317
Carrier Coding by 3-Digit ZIP
REPORT parameter record, 194
CARRIER CODING BY 3-DIGIT ZIP field (REPORT), 194
Carrier Coding by 3-Digit ZIP Report, 194
Carrier Coding by List Code
REPORT parameter record, 194
CARRIER CODING BY LIST CODE field (REPORT), 194
Carrier Coding by List Code Report, 194
Carrier Coding by State
REPORT parameter record, 193
CARRIER CODING BY STATE field (REPORT), 193
Carrier Coding by State Report, 193
Carrier Route, 322
Carrier Route Data
CR OUT, 134
Carrier route data
CR OUT parameter record, 134
CASS
certification, 123
CASSA1 parameter record
defined, 117
CASSA4, 119
Z4CHANGE-certified Software Name, 119
CASSA4 parameter record
defined, 119
Z4CHANGE-certified Company Name, 119
CASSA7, 120
CASSA7 parameter record
defined, 120
ELOT-certified Company Name, 120
ELOT-certified Software Name, 120
CASS Configurations
CONFIG parameter record, 123
CASS Form
separate print file, 196
Census Block Group
545
IX
Index
G9 OUT parameter record, 168
Census Geocode
G9 OUT parameter record, 168
Census Tract
G9 OUT parameter record, 168
CENSUS TRACT field, 168
CHANGE parameter record (for G1G001)
defined, 393
field-by-field, 393
CHCKPT, 121
CHCKPT parameter record
Checkpoint Count, 122
Device Type, 122
CHCKPT parameter record, defined, 121
CICS
example procedure division, 446
Cities in a State Screen (Interactive), 273
Cities in a ZIP Code Screen (Interactive), 276
City Information Screen (Interactive), 278
City name
alternate, 276
short, 276
City Type, defined, 276
City types
returned, 128
CLASS CODE field, 171
Client Code
L CODE parameter record, 177
CMRA, 339, 360
defined, 199
CMRA address example, 199
Commercial Mail Receiving Agency, 360
commercial mail receiving agency, 339
Commercial Mail Receiving Agents
defined, 199
Concatenated commands
using in interactive system, 232
CONFIDENCE CODE field, 170
CONFIG, 123
CONFIG parameter record
defined, 123
DIRECTIONAL/SUFFIX MATCH CODE, 124
DUAL ADDRESS MATCH LOGIC, 126
ENHANCED HIGH RISE ALTERNATE MATCHING, 127
FIRMN NAME MATCH CODE, 124
MAXIMUM ADDRESS CORRECTNESS, 124
MAXIMUM OVERALL CORRECTNESS, 125
MULT. SECONDARY COMPONENT PROCESSING, 127
MULTIPLE MATCH ACCEPTANCE, 124
OUTPUT CASE OPTION, 125
PMB HANDLING, 126
STREET NAME MATCH CODE, 124
TERMINATE IF NON-CASS, 125
UNIQUE ZIP HANDLING, 126
USE NON-STANDARD CITY NAMES, 128
USER-SPECIFIED CONFIG. NUMBER, 125
CONFIRM APO/FPO ZIP field (CONFRM), 131
Confirmation flags, 130
546
eliminates matching, 130
CONFIRMATION VALUE fields (CONFRM), 132
Confirming records without processing, 130
CONFIRM MILITARY BASE ZIPS field (CONFRM), 131
CONFRM, 130
CONFRM parameter record
CONFIRM APO/FPO ZIPs, 131
CONFIRMATION FLAG, 131
CONFIRMATION VALUE fields, 132
CONFIRM GOVERNMENT AGENCY ZIPS, 131
CONFIRM MILITARY BASE ZIPs, 131
defined, 130
EQUAL/NOT EQUAL CODE, 132
OUTPUT CONFIRMATION CODE, 131
CONSTANT parameter record (for G1G001)
defined, 385
field-by-field, 385
CONTRL parameter record
defined, 133
example, 134
CONTRL parameter record (for G1G001)
defined, 383
field-by-field, 384
Control Totals Report, 192
Correcting uncoded records
G1CPNBC user exit program, 307
interactive system, 307
Correctness
maximum overall
SA OUT parameter record, 204
Z4 OUT parameter record, 218
CROSS SECT. SAMPLING field (FILEDF), 378
Cross-sectional sampling, 187
CR OUT parameter record
CARRIER ROUTE CODE, 135
CARRIER ROUTE RETURN CODE, 134
defined, 134
DISPOSITION INDICATOR, 136
MAXIMUM ADDRESS CORRECTNESS, 135
MAXIMUM OVERALL CORRECTNESS, 135
Storage conditions INFO. DROPPED, 135
Storage conditions MULTIPLE CR-RT ROUTE, 135
Storage conditions MULTIPLE ZIP CODE, 136
CS OUT, 137
CS OUT parameter record
CITY/STATE RETURN CODE, 138
CITY NAME, 138
defined, 137
DISPOSITION INDICATOR, 141
MAXIMUM ADDRESS CORRECTNESS, 141
MAXIMUM OVERALL CORRECTNESS, 141
SHORT CITY NAME, 139
STANDARDIZED CITY/STATE LINE, 139
STANDARDIZED URBANIZATION NAME, 139
STATE ABBREVIATION, 139
Storage conditions INFO. DROPPED, 140
Storage conditions INPUT SHORT CITY NAME, 138
Storage conditions MULTIPLE ZIP+4, 141
Software Release 4.0.0/March 2015
IX
Storage conditions MULTIPLE ZIP CODE, 141
Storage conditions NO ADDRESS MATCH, 139
Storage conditions NO CITY MATCH, 141
Storage conditions NO STATE MATCH, 139
CSP-CITYO call area field, 487
CSP-CTYPEO call area field, 488
CSP-FINO call area field, 488
CSP-LL-LBO call area field, 488
CS-PRM-CITYO call area field, 486
CS-PRM-CSTI call area field, 485
CS-PRM-CTYPEO call area field, 487
CS-PRM-FINO call area field, 487
CS-PRM-FNC call area field, 485
CS-PRM-GRC call area field, 485
CS-PRM-INPUT-CITY-RC call area field, 486
CS-PRM-INPUT-ZIP-RC call area field, 486
CS-PRM-IO-FCZ call area field, 489
CS-PRM-IO-FLD call area field, 489
CS-PRM-LL-LBO call area field, 487
CS-PRM-OUTPUT-CITY-RC call area field, 486
CS-PRM-OUTPUT-ZIP-RC call area field, 486
CS-PRM-READ-FCZ call area field, 488
CS-PRM-READ-FLD call area field, 488
CS-PRM-READ-FZC call area field, 488
CS-PRM-STATEO call area field, 486
CS-PRM-SZIP call area field, 487
CS-PRM-ZIPI call area field, 485
CS-PRM-ZIPO call area field, 487
CSP-SHORT-CITYO call area field, 487
CSP-STATEO call area field, 487
CS ZIP parameter record
CITY/STATE/ZIP CODE, 142, 143
defined, 142
EXTRACTED ZIP CODE, 143
MASTER FILE LITERAL DATE, 144
MASTER FILE VINTAGE DATE, 144
ORIGINAL CARRIER ROUTE CODE, 144
ORIGINAL ZIP+4 CODE, 143, 144
SEPARATE STATE, 143
SEPARATE ZIP CODE, 143
D
Database
browsing from CICS application, 490
for Z4CHANGE, 314
Database expiration
bypassing, 116
Database inquiry function (interactive system)
Apartments at a House Range Screen, 270
Cities in a State Screen, 273
Cities in a ZIP Code Screen, 276
City Information Screen, 278
Firms on a Street Screen, 281
Houses on a Street Screen, 283
Working With CODE-1 Plus
Streets in a City Screen, 286
DATE field (HEADER), 174
Date Received
L CODE parameter record, 177
Delivery Point Barcode
location for (Z4 OUT), 216
Delivery Point Barcode (DPBC)
Z4 OUT parameter record, 216
Delivery Point Validation
error messages, 361
false/positive flag, 360
Getting started with, 341
introduction, 337
License Management, 341
Delivery Point Validation database
installing, 341
MVS/VSE/IMS, 346, 528
Unix, 343, 526
VMS, 345, 507, 529
Windows NT, 342, 343, 503, 525
z/OS/VSE/IMS, 506
verify the install, 344, 517
Delivery Point Validation processing
expiration of, 361
Delivery Sequence File Footnotes, 97
Delivery Sequence Footnotes Screen (Interactive), 236
Device Type
FILEDF parameter record, 163
DIR./SUFFIX MATCH CODE field
(CONFIG), 124
Dispatcher4
Address and City/State/ZIP Code Layout dialog box, 36
Address Matcher Memory Configuration dialog box, 58
CASS configuration, 53
Confirm Without Matching dialog box, 50
Job Summary dialog box, 65
Limit Records to Process dialog box, 48
List and Mailer dialog box, 72
Rearrange Field After Processing dialog box, 42
Disposition Indicator
LOTOUT parameter record, 181
SA OUT parameter record, 205
Z4 OUT parameter record, 220
Z5 OUT parameter record, 224
DISPOSITION INDICATOR field
(AE OUT), 95
(CR OUT), 136
(CS OUT), 141
(SA OUT), 205
(Z4 OUT), 220
(Z5 OUT), 224
Domestic Mail Manual, 322, 339
DPBC
Z4 OUT parameter record, 216
DPV
error messages, 361
false/positive flag, 360
Getting started with, 341
547
IX
Index
introduction, 337
License Management, 341
DPV010L, 359
DPV by List Code Report, 363
DPV CMRA
DPV parameter record, 153
DPV database
installing, 341
Unix, 343, 526
VMS, 345, 507, 529
Windows NT, 342, 343, 503, 525
z/OS/VSE/IMS, 346, 506, 528
verify the install, 344, 517
DPV errors
interactive, 234
DPV False/Positive
DPV parameter record, 153
DPV Footnote Codes
description, 360
DPVIN Parameter, 359
DPV Large Memory Module, 359
DPV message
interactive, 234
DPVOUT Parameter, 360
DPV parameter record
description, 146
DPV CMRA, 153
DPV FALSE/POSITIVE, 153
DPV RETURN CODE, 152
Multiple Match Option, 148
DPV Parameters and Return Codes, 359
DPV processing
expiration of, 361
improving speed of, 359
DPV Processing Summary Report, 363
DPV Return Code
DPV parameter record, 152
Dropped address information
defining locations for, 106
Dropped Information/Base Address Screen (Interactive),
239
Dropped Information Code
SA OUT parameter record, 202
Dual address match logic, 126
E
Early Warning System
what is it?, 366
ELOT
overriding certification data (CASSA7), 120
Enhanced Alternate Highrise Match
storage options
SA2OUT parameter record, 207
Enhanced Carrier Route, 322, 339
548
Enhanced High Rise Alternate Matching, 127
Environment, 396
EQUAL/NOT EQUAL CODE field (CONFRM), 132
Error messages
DPV, 361
EWS
what is it?, 366
Example procedure division
for CICS, 446
Examples of Multiple Matches in CODE-1 Plus, 340
Excluding
nth records, 188
Executing Line of Travel, 323
Execution Log, 192
Execution Log Counter, 125
EXITOP parameter record
defined, 157
OPERATING EXIT ROUTINE NAME, 158
Exit routine
LTO60 exit routine, 323
Exit Routine Name
FILEDF parameter record, 164
EXIT ROUTINE NAME field (FILEDF), 164, 378
Exit routines
input, defined, 160
operating exit routine, 157
output, defined, 160
Expanded Return Codes Screen (Interactive), 242
Expired database
bypassing, 116
EXT2PARM, 462
EXTADDR2, 399, 454, 462, 463
EXT2PARM, 462
SMPLDRVR2 sample COBOL batch program, 463
special processing switches, 463
EXTRADDR2
supplied copybooks, 463
F
False/Positive
seed record
report, 364
false/positive, 360
False/Positive Table
reporting a match, 348
Field Labels
predefined, 73
FILEDF, 186
FILEDF parameter record
BLOCK SIZE, 163
defined, 159
DEVICE TYPE, 163
EXIT ROUTINE NAME, 164
FILE NAME, 162
Software Release 4.0.0/March 2015
IX
FRACTIONAL RECORD SELECTION, 164
fractional record selection, 161
LABEL TYPE, 163
limiting processing, 161
MAXIMUM NUMBER OF RECORDS, 164
NUMBER OF RECORDS TO SKIP, 164
RECORD FORMAT, 162
RECORD LENGTH, 162
TAPE REEL HANDLING, 163
FILEDF parameter record (for G1G001)
BLOCK SIZE, 377
CROSS SECTIONAL SAMPLING, 378
defined, 377
EXIT ROUTINE NAME, 378
field-by-field, 377
FILE NAME, 377
MAXIMUM NUMBER OF RECORDS, 378
NUMBER OF RECORDS TO SKIP, 378
RECORD FORMAT, 377
RECORD LENGTH, 377
FILEDT parameter record
field-by-field, 358
File Name
FILEDF parameter record, 162
FILE NAME field (FILEDF), 162, 377
File names
C1BMCOK output file, 159
C1BMIZP output file, 159
C1BMNAM input file, 159
C1BMNCO output file, 159
C1BMZP4 output file, 159
for G1G001 (report generator), 394
Final ZIP Code
source of, 223
FIPS County Code
G9 OUT parameter record, 168
FIPS State Code
G9 OUT parameter record, 168
Firm Name
defined, 165
FIRMNM parameter record, 166
FIRM NAME MATCH CODE field (CONFIG), 124
FIRMNM parameter record
defined, 165
FIRM NAME, 166
Firms on a Street Screen (Interactive), 281
First Interactive Customization Screen (Interactive), 296
Footers
UFTxx parameter record, 214
Footer Text
UFTxx parameter record, 214
FOOTER TEXT field (UFTxx), 214, 381
FORM, 196
FORMAT parameter record (for G1G001)
defined, 386
field-by-field, 386
Fractional Record Selection
FILEDF parameter record, 164
Working With CODE-1 Plus
Fractional record selection
FILEDF parameter record, 161
Fraction of Records
NTHSEL parameter record, 186
G
G1C1AUX, 371
G1CPBNC user exit program
correcting uncoded records (interactive system), 307
for correcting uncoded records, 311
G1CPFDF, 305
G1CPLKB browsing database
calling from an IMS application, 497
G1CPLKC browsing database (from CICS)
calling, 489
defined, 489
LOOKREQ call area, 490
G1G001 parameter records
CHANGE, 393
CONSTANT, 385
CONTRL, 383
FILEDF, 377
FORMAT, 386
HEADER, 379
HEADxx, 380
MOVE, 388
PAGESZ, 389
SELECT, 392
TESTIT, 390
UFT, 381
UHD, 382
UNPK, 391
G1G001 report generator program
defined, 376
headers and footers, 379
input file, 377
report layout, 383
selecting reports, 392
using, 376
G9 OUT parameter record
CENSUS BLOCK GROUP, 168
CENSUS GEOCODE, 168
CENSUS TRACT, 168
defined, 168
FIPS COUNTY CODE, 168
FIPS STATE CODE, 168
LATITUDE/LONGITUDE, 169
MSA CODE, 169
MSA NAME, 169
G9XOUT parameter record
CLASS CODES, 171
CONFIDENCE CODE, 170
defined, 170
GEOTAX OUTPUT KEY, 172
549
IX
Index
GEOTAX RETURN CODE, 172
INCORPORATED FLAG, 171
LAST ANNEXED DATE, 171
LAST UPDATED DATE, 171
LAST VERIFIED DATE, 172
Minor Civil Division/Census County Division, 170
PRIZM CLUSTER, 171
PRIZM SOCIAL GROUP CODE, 171
G9ZIP9 parameter record
defined, 173
Generating reports
for Z4CHANGE processing, 318
Geocoder Information Screen (Interactive), 244
Geographic Coding Plus
G9ZIP9 parameter record, 173
Output Layout File Definition Field Labels, 84
storage locations, 168, 170
Geographic Coding System
storage locations, 168
Geographic Coding System Interface (Interactive), 288
GeoTAX Key, 292
GeoTAX Key Return Code, 292
GeoTAX Output Key
G9XOUT parameter record, 172
GeoTAX Return Code
G9XOUT parameter record, 172
Getting Started with Delivery Point Validation, 341
Government agency ZIP Codes, 130
H
HEADER parameter record
DATE, 174
defined, 174
HEADING, 174
START ZIP CODE, 174
STOP ZIP CODE, 174
HEADER parameter record (for G1G001)
defined, 379
field-by-field, 379
Header Text
UHDxx parameter record, 215
HEADER TEXT field (UHDxx), 215, 382
Heading
HEADER parameter record, 174
HEADING field (HEADER), 174
Headings
UHDxx parameter record, 215
HEADxx parameter record (for G1G001)
defined, 380
field-by-field, 380
Houses on a Street Screen (Interactive), 283
550
I
IMS environment
processing for C1MATCHx, 446
program control blocks (PCBs) for C1MATCHx, 446
IMS JCL
for G1G001 (report generator), 394
Include/Exclude Option
NTHSEL parameter record, 186
Including
nth records, 188
INCORPORATED FLAG field, 171
Information Dropped
storage conditions
Z4 OUT parameter record, 218
Z5 OUT parameter record, 223
INP Option
using, 198
Input exit routine, 160
Input file
check sequence of (SEQCHK), 208
Input record array, 183
Installation
DPV database, 341
Installing
DPV database, 341
z/OS/VSE/IMS, 528
Unix, 343, 526
verify the install, 344, 517
VMS, 345, 507, 529
Windows NT, 342, 343, 503, 525
z/OS/VSE/IMS, 346, 506
LACSLink database
Unix, 504
Installing the DPV Database, 341
Interactive Screen Reference
GeoTAX Key, 292
Interactive site customization
Administration Sign-on screen, 294
First Interactive Customization screen, 296
Second Interactive Customization screen, 299
Interactive system
Address Match Screen, 233
Address Stack Screen, 266
Administration Sign-on Screen, 294
Apartments at a House Range Screen, 270
Cities in a State Screen, 273
Cities in a ZIP Code Screen, 276
City Information Screen, 278
Delivery Sequence Footnotes Screen, 236
Dropped Information/Base Address Screen, 239
Expanded Return Codes Screen, 242
Firms on a Street Screen, 281
First Interactive Customization Screen, 296
Geocoder Information Screen, 244
Houses on a Street Screen, 283
Software Release 4.0.0/March 2015
IX
Match Settings Screen, 246
Multiple Elements Screen, 249
Parsed Elements Screen, 252
Return Codes Screen, 254
Second Interactive Customization Screen, 299
site customization file (G1CPFDF), 305
Statistics Screen, 262
Streets in a City Screen, 286
using concatenated commands, 232
Internal Program Name
PGMNAM parameter record, 191
Invoking Line of Travel, 323
L
Label Type
FILEDF parameter record, 163
LACS
See Locatable Address Correction Service (LACS), 199
LACS Indicator
SA OUT parameter record, 203
LACSLink
eligibility, 501
introduction, 499, 521
processing requirements, 502
using batch processing, 510
using Interactive processing, 512
Using the CODE-1 Plus GUI, 508, 530
LACSLink
LACS parameter record, 175
LACSLink database
installing
Unix, 504
LACS parameter record, 175
defined, 175
Latitude/Longitude
G9 OUT parameter record, 169
LATITUDE/ LONGITUDE COORDINATE field, 169
LATITUDE/ LONGITUDE LEVEL field, 169
L CODE parameter record
CLIENT CODE, 177
DATE RECEIVED, 177
defined, 177
LIST CODE, 177
processing up to 10,000 list codes (C1BM00XL), 177
License Management
DPV processing, 341
Limiting processing, 174
FILEDF parameter record, 161
Line Number
UFTxx parameter record, 214
UHDxx parameter record, 215
LINE NUMBER field
(UFTxx), 214, 381
(UHDxx), 215, 382
Working With CODE-1 Plus
Line of Travel
accessing, 323
executing, 323
LTO10 callable subroutine, 323
LTO60 exit routine, 323
output records, 322
Line of Travel code
LOT code, 322
Line of Travel Coding by 3-Digit ZIP Code
REPORT parameter record, 195
Line of Travel Coding by List Code
REPORT parameter record, 195
Line of Travel Coding by State
REPORT parameter record, 195
Line of Travel number, 322
Line of Travel reports
LOTOUT parameter record must be defined, 192
Line of Travel sequence code, 322
Line Side
UFTxx parameter record, 214
UHDxx parameter record, 215
LINE SIDE field
(UFTxx), 214, 381
(UHDxx), 215, 382
Lines-per-page
PAGESZ parameter record, 189
LINES-PER-PAGE field (PAGESZ), 189, 389
List Code
defined in L CODE parameter record, 177
L CODE parameter record, 177
List Code Report
DPV, 363
List codes
processing up to 10,000 list codes (C1BM00XL driver
program), 177
List ID
LISTID parameter record, 178
LISTID parameter record
defined, 178
List name
LISTNM parameter record, 179
LISTNM parameter record
defined, 179
LIST PROCESSOR NAME, 179
List Processor Name
LISTNM parameter record, 179
Locatable Address Correction Service (LACS)
description, 199
LONGITUDE field, 169
LOOKREQ call area (for G1CPLKC)
defined, 490
LOT code, 322, 339
defined, 322
LOT coded records
alternate sequence code, 324
hexadecimal sequence code, 324
Sorting, 324
LOT Coding by 3-Digit ZIP Code
551
IX
Index
REPORT parameter record, 195
LOT Coding by List Code
REPORT parameter record, 195
LOT Coding by State
REPORT parameter record, 195
LOTOUT parameter record
ALPHABETIC PORTION OF LOT CODE, 181
ALTERNATE SEQUENCE CODE, 181
defined, 180
DISPOSITION INDICATOR, 181
LOT RETURN CODE, 180
NUMERIC PORTION OF LOT CODE, 181
LOT reports
LOTOUT parameter record must be defined, 192
LOT Return Code
LOTOUT parameter record, 180
M
Mailer information
MAILER parameter record, 182
MAILER parameter record
defined, 182
Maps
of call areas, 399
Master File Literal Date
CS ZIP parameter record, 144
Master File Vintage Date
CS ZIP parameter record, 144
Z4 OUT parameter record, 217
Match
reporting a seed record, 348
Matching modules, 398
Match Settings Screen (Interactive), 246
Maximum Address Correctness
SA OUT parameter record, 204
Z4 OUT parameter record, 218
MAXIMUM ADDRESS CORRECTNESS field
(CONFIG), 124
(CR OUT), 135
(CS OUT), 141
(SA OUT), 204
(Z4 OUT), 218
(Z5 OUT), 223
Maximum Number of Records
FILEDF parameter record, 164
Maximum Overall Correctness
SA OUT parameter record, 204
Z4 OUT parameter record, 218
MAXIMUM OVERALL CORRECTNESS field
(CONFIG), 125
(CR OUT), 135
(CS OUT), 141
(SA OUT), 204
(Z4 OUT), 218
552
MAXIMUM RECORDS field (FILEDF), 164, 378
MCD/CCD field, 170
Memory Configuration Program Name
PGMNAM parameter record, 191
Military base ZIP Codes, 130
Minor Civil Division/Census County Division
G9XOUT parameter record, 170
Mixed case
how to print reports in, 192
MOVE I parameter record
defined, 183
SOURCE, 184
SOURCE/TARGET, 184
TARGET, 184
MOVE O parameter record
defined, 185
SOURCE, 185
SOURCE/TARGET, 185
TARGET, 185
Move output fields
MOVE O parameter record, 185
MOVE parameter record (for G1G001)
defined, 388
field-by-field, 388
MSA Code
G9 OUT parameter record, 169
MSA Name
G9 OUT parameter record, 169
MULT. MATCH ACCEPT. field (CONFIG), 124
multiple conditions, 339
Multiple Elements Screen (Interactive), 249
Multiple Match Option
DPV parameter record, 148
Multiple match options, 359
Multiple ZIP+4
storage conditions
Z4 OUT parameter record, 219
Multiple ZIP Code
storage conditions
SA OUT parameter record, 204
Z4 OUT parameter record, 219, 224
N
National Deliverability Index Report (NDI)
REPORT parameter record, 194
NDI
REPORT parameter record, 194
Normalized address
defining locations for, 106
Nth Number
NTHSEL parameter record, 186
NTHSEL parameter record
defined, 186
FRACTION OF RECORDS, 186
Software Release 4.0.0/March 2015
IX
INCLUDE/EXCLUDE OPTION, 186
Nth NUMBER, 186
sampling used with FILEDF, 186
skipping and limiting record example, 187
NUM. RECORDS TO SKIP field (FILEDF), 164, 378
Number of Records to Skip
FILEDF parameter record, 164
Numeric Portion of LOT Code
LOTOUT parameter record, 181
O
of, 177, 201, 202
Open/Read failure
DPV, 361
Open VMS command file
for G1G001 (report generator), 394
Operating exit routine, 157
Operating Exit Routine Name
EXITOP parameter record, 158
OPERATING EXIT ROUTINE NAME field (EXITOP), 158
Operating exit routines
EXITOP parameter record, 157
Output exit routine, 160
operating (EXITOP), 157
Output File Definition Field Labels, 81
Output Layout File Definition Field Labels, 74
Output Layout File Definition Field Labels for Geographic
Coding Plus, 84
Output record array, 185
Output records, 322
Overriding other parameter records with CONFIG, 123
P
P9AUDIT, 443
P9AUDIT call area (for C1MATCHx)
defined, 403
mapped, 443, 444
P9IAD2 call area field, 411
P9IAUX, 371
P9ICST call area field, 412
P9IDSM call area field, 406
P9IENV call area field, 412
P9IFMM call area field, 406
P9IFNC call area field, 405
P9IFRM call area field, 411
P9IN call area (for C1MATCHx)
defined, 403
mapped, 405
P9IAD2, 411
P9ICST, 412
P9IDSM, 406
Working With CODE-1 Plus
P9IDUAL, 407
P9IENV, 412
P9IFMM, 406
P9IFNC, 405
P9IFRM, 411
P9ISTM, 405
P9ITEST, 406
P9IZIP, 411
P9ISTM call area field, 405
P9IZIP call area field, 411
P9O#AM call area field, 416
P9O9RC call area field, 419
P9OAP# call area field, 423
P9OAPR call area field, 416
P9OARC call area field, 416
P9OAT# call area field, 423
P9OATP call area field, 423
P9OBX# call area field, 423
P9OCAO call area field, 433
P9OCBA call area field, 434
P9OCIT call area field, 420
P9OCL9 call area field, 435
P9OCRC call area field, 419
P9OCRT call area field, 420
P9OCS9 call area field, 436
P9OCSV call area field, 422
P9OCZP call area field, 435
P9OD2R call area field, 427
P9ODBV call area field, 422
P9ODFR call area field, 418
P9ODI1 call area field, 423
P9ODI2 call area field, 423
P9ODIT call area field, 418
P9ODPC call area field, 420
P9ODRC call area field, 416
P9OFBA call area field, 434
P9OFRC call area field, 417
P9OFSC call area field, 417
P9OGRC call area field, 415
P9OHS# call area field, 423
P9OICR call area field, 432
P9OOCR call area field, 433
P9OOZA call area field, 434
P9OPRA call area field, 417
P9OPRB call area field, 415
P9ORP# call area field, 423
P9ORR# call area field, 423
P9ORTP call area field, 421
P9OSAB call area field, 420
P9OSAD call area field, 423
P9OSAL call area field, 423
P9OSAR call area field, 426
P9OSFR call area field, 427
P9OSFX call area field, 423
P9OSFZ call area field, 433
P9OSMA call area field, 417
P9OSNR call area field, 427
P9OSRC call area field, 416
553
IX
Index
P9OSSC call area field, 415
P9OSTA call area field, 436
P9OSTH call area field, 423
P9OSTN call area field, 423
P9OSTR call area field, 423
P9OSWD call area field, 422
P9OSWV call area field, 422
P9OUT call area (for C1MATCHx)
defined, 403
mapped, 414
P9O#AM, 416
P9O9RC, 419
P9OAP#, 423
P9OAPR, 416
P9OARC, 416
P9OAT#, 423
P9OATP, 423
P9OBX#, 423
P9OCAO, 433
P9OCASS, 438
P9OCASS-X-DATE, 438
P9OCBA, 434
P9OCIT, 420
P9OCITY-TYPE, 436
P9OCL9, 435
P9OCRC, 419
P9OCRT, 420
P9OCS9, 436
P9OCSV, 422
P9OCZP, 435
P9OD2R, 427
P9ODBV, 422
P9ODFR, 418
P9ODI1, 423
P9ODI2, 423
P9ODIT, 418
P9ODPBC, 420
P9ODPC, 420
P9ODRC, 416
P9OFBA, 434
P9OFRC, 417
P9OFSC, 417
P9OGRC, 415
P9OHS#, 423
P9OICR, 432
P9OMFD, 438
P9OMFV, 438
P9ONTP, 420
P9OOCR, 433
P9OOZA, 434
P9OPRA, 417
P9OPRB, 415
P9ORR#, 423
P9ORTP, 421
P9OSAB, 420
P9OSAD, 423
P9OSAL, 423
P9OSAR, 426
554
P9OSFR, 427
P9OSFX, 423
P9OSFZ, 433
P9OSMA, 417
P9OSNR, 427
P9OSRC, 416
P9OSSC, 415
P9OSTA, 436
P9OSTH, 423
P9OSTN, 423
P9OSTR, 423
P9OSWD, 422
P9OSWV, 422
P9OURC, 420
P9OXRC, 438
P9OZ, 435
P9OZ call area field, 435
PAGESZ parameter record
defined, 189
LINES-PER-PAGE, 189
REPORT OR LOG CODE, 189
PAGESZ parameter record (for G1G001)
defined, 389
field-by-field, 389
LINES-PER-PAGE, 389
REPORT OR LOG CODE, 389
Parameter Record List Report, 192
Parsed Elements Screen (Interactive), 252
Password
finding, 353, 518
PCBs (program control blocks), IMS
for C1MATCHx, 446
PFKEYS (Interactive)
Definition of, 303
PGMNAM parameter record
defined, 190
INTERNAL PROGRAM NAME, 191
MEMORY CONFIGURATION PROGRAM NAME, 191
PLACE CODE fields, 170
platform-specific
building your RDI file, 356
PMB, 339
SA2OUT parameter record, 206
PMB designation, 199
PMBs
requirements for, 199
PO Box-only ZIP Code, 223
Postal discounts, automation-based, 123
Predefined Field Labels, 73
Preferred city name, defined, 276
Print upper/lower case
REPORT parameter record, 194
Private Mailbox
SA2OUT parameter record, 206
Private Mailboxes
requirements for, 199
private mail boxes, 339
Private Mailbox Handling, 126
Software Release 4.0.0/March 2015
IX
PRIZM CLUSTER fields, 171
PRIZM SOCIAL GROUP CODE field, 171
Processing Requirements
LACSLink, 502
Processing Summary Report
DPV, 363
Program Control Blocks, IMS
for C1MATCHx, 446
Program parameters
for correcting uncoded records, 310
Q
Qualifying for automation-based discounts, 123
R
R777, 419
R777 record suppression of ZIP+4 (DPBC)
Z4 OUT parameter record, 218
RDI
definition of, 355
RDI processing, 355
Activating RDI processing, 150
building the RDI File step-by-step, 356
building your RDI file, 355
building your RDI file in
z/OS/VSE/IMS, 356
building your RDI file in Windows, 356
Residential Delivery File Build Execution Log
Residential Delivery File processing
Residential Delivery File Build Execution Log, 364
Residential Delivery File Build Report, 364
Specifying location for RDI flag, 156
RDI utility program
C1DBRDI, 356
Rearrange input fields
MOVE I parameter record, 183
Rearrange output fields
MOVE O parameter record, 185
Record Format
FILEDF parameter record, 162
RECORD FORMAT field (FILEDF), 162, 377
Record Length
FILEDF parameter record, 162
RECORD LENGTH field (FILEDF), 162, 377
Rejecting
nth records, 188
Reporting a match
seed record, 348
Report or Log Code
Working With CODE-1 Plus
PAGESZ parameter record, 189
REPORT OR LOG CODE field (PAGESZ), 189, 389
REPORT parameter record
ANALYSIS OF MATCHED RECORDS, 192
CARRIER CODING BY 3-DIGIT ZIP, 194
CARRIER CODING BY LIST CODE, 194
CARRIER CODING BY STATE, 193
defined, 192
LINE OF TRAVEL CODING BY 3-DIGIT ZIP CODE, 195
LINE OF TRAVEL CODING BY LIST CODE, 195
LINE OF TRAVEL CODING BY STATE, 195
NATIONAL DELIVERABILITY INDEX (NDI) REPORT, 194
PRINT UPPER/LOWER CASE, 194
SUMMARY BY 3-DIGIT ZIP, 194
SUMMARY BY LIST CODE, 194
SUMMARY BY STATE, 194
USPS FORM 3553 SEPARATE PRINT FILE, 196
ZIP+4 CODING BY 3-DIGIT ZIP Code, 194
ZIP+4 CODING BY LIST CODE, 193
ZIP+4 CODING BY STATE, 192
Reports
Address-Match Execution Statistics, 192
Carrier Coding by 3-Digit ZIP, 194
Carrier Coding by List Code, 194
Carrier Coding by State, 193
Control Totals, 192
Execution Log, 192
how to print in mixed case, 192
Parameter Record Listing, 192
printed automatically, 192
Residential Delivery File Build, 364
Summary by 3-Digit ZIP, 194
Summary by List Code, 194
Summary by State, 194
USPS Form 3553, 192
ZIP+4 Coding by 3-Digit ZIP Code, 194
ZIP+4 Coding by List Code, 193
ZIP+4 Coding by State, 192
Residential Delivery File Build Report, 364
Residential Delivery File Processing, 355
Residential Delivery File processing
building the RDI file step-by-step, 356
building your RDI file, 355
building your RDI file in
z/OS/VSE/IMS, 356
building your RDI file in Windows, 356
C1DBRDI, 356
definition of, 355
Residential Delivery File Build Execution Log, 364
Residential Delivery File Build Report, 364
Return codes
batch matching, 97
defining locations for, 97, 103
for geographic coding, 168
Return Codes Screen (Interactive), 254
RP-BMOARC call area field, 472, 473, 474, 475, 476
RP-CT-AMA call area field, 478
RP-CT-APO call area field, 478
555
IX
Index
RP-CT-BYP call area field, 478
RP-CT-COK call area field, 478
RP-CT-GOV call area field, 478
RP-CT-IZP call area field, 478
RP-CT-MIL call area field, 478
RP-CT-NAM call area field, 477
RP-CT-NCO call area field, 478
RP-CT-PRC call area field, 478
RP-CT-VAL call area field, 478
RP-DATE call area field, 480
RP-HEADER call area field, 480
RP-INP-ZP4 call area field, 477
RP-INP-ZP4-VAL call area field, 477
RP-LCDNEW call area field, 477
RP-RETURN-CODE call area field, 471
RP-RPANMR call area field, 479
RP-RPCR3D call area field, 479
RP-RPCRLC call area field, 479
RP-RPCRST call area field, 479
RP-RPS4ST call area field, 479
RP-RPSM3D call area field, 480
RP-RPSMLC call area field, 480
RP-RPSMST call area field, 480
RP-RPUPLO call area field, 480
RP-RPZ43D call area field, 479
RP-RPZ4LC call area field, 479
S
SA2OUT parameter record
defined, 206
ENHANCED ALTERNATE HIGHRISE MATCH STORAGE
OPTIONS, 207
PRIVATE MAILBOX (PMB), 206
Sampling your input file
cross-sectional sampling, 187
nth record inclusion/exclusion, 188
SA OUT parameter record, 204
ADDRESS RETURN CODE, 200
ADDRESS SOURCE CODE, 202
ADDRESS WITH APARTMENT, 201
ADDRESS WITHOUT APARTMENT, 201
ALIAS/BASE RETURN OPTION, 203
Alias and Base street names, 197
ALIAS RETURN CODE, 203
ALIAS TYPE CODE, 203
APARTMENT/PMB, 201
BLANK UNUSED ADDRESS LINES, 201
defined, 197
DISPOSITION INDICATOR, 205
DROPPED INFORMATION CODE, 202
Information Dropped, 204
LACS INDICATOR, 203
Location for PMB RETURN CODE
PMB Return Code
556
SA OUT parameter record, 204
MAXIMUM ADDRESS CORRECTNESS, 204
MAXIMUM OVERALL CORRECTNESS, 204
storage conditions, 204
Storage conditions ADDRESS WITH APARTMENT
Address with Apartment
SA OUT parameter record
storage conditions, 201
Storage conditions ADDRESS WITHOUT APARTMENT,
201
Storage conditions APARTMENT/PMB, 202
Storage conditions INFORMATION DROPPED, 204
Storage conditions MULTIPLE STANDARDIZED
ADDRESSES
Multiple Standardized Addresses
storage conditions
SA OUT parameter record, 204
Storage conditions MULTIPLE ZIP CODE, 204
using the INP Option, 198
Screens (Interactive)
Address Match Screen, 233
Address Stack Screen, 266
Administrative Sign-on Screen, 294
Apartments at a House Range Screen, 270
Cities in a State Screen, 273
Cities in a ZIP Code Screen, 276
City Information Screen, 278
correcting uncoded records, 307
Delivery Sequence Footnotes Screen, 236
Dropped Information/Base Address Screen, 239
Expanded Return Codes Screen, 242
Firms on a Street Screen, 281
First Interactive Customization Screen, 296
Geocoder Information Screen, 244
Geographic Coding System Interface, 288
Houses on a Street Screen, 283
Match Settings Screen, 246
Multiple Elements Screen, 249
Parsed Elements Screen, 252
program parameters for correcting records, 310
Return Codes Screen, 254
Second Interactive Customization Screen, 299
Statistics Screen, 262
Streets in a City Screen, 286
Second Interactive Customization Screen (Interactive), 299
Seed ID
interactive, 254
what does it look like?
interactive, 254
Seed Record
reporting a match, 348
Seed records
definition, 362
Selecting
nth records, 188
SELECT parameter record (for G1G001)
Software Release 4.0.0/March 2015
IX
defined, 392
field-by-field, 392
SEQCHK parameter record
defined, 208
Short city name, defined, 276
Site customization file (G1CPFDF), 305
recovering, 305
Skipping and Limiting Record Example, 187
SMPLDRVR2
sample COBOL batch program, 399, 454
SMPLDRVR2 sample COBOL batch program, 463
Sorting LOT-coded records, 324
Source
MOVE I parameter record, 184
MOVE O parameter record, 185
Source/Target
MOVE I parameter record, 184
MOVE O parameter record, 185
Source of Final ZIP Code
Z5 OUT parameter record, 223
Special ZIP Codes, 130
Speed of
improving DPV processing, 359
Standardized
city, state, ZIP (CS ZIP), 142
city and state (CS OUT), 137
firm name (FIRMNM), 165
Standardized Urbanization Name
CS OUT, 139
START ZIP CODE field (HEADER), 174
Statistics Screen, 262
STOP ZIP CODE field (HEADER), 174
Street default flag, 105
STREET NAME MATCH CODE field
(CONFIG), 124
Streets in a City Screen (Interactive), 286
SuiteLink
defined, 522
eligibility, 523
input and output examples, 537
mainframe DD names, 536
reporting, 537
return codes, 536
using batch processing, 347, 532
using Interactive processing, 347, 512, 533, 534
SUMMARY BY 3-DIGIT ZIP field (REPORT), 194
Summary by 3-Digit ZIP Report, 194
Summary by List Code
REPORT parameter record, 194
SUMMARY BY LIST CODE field (REPORT), 194
Summary by List Code Report, 194
Summary by State
REPORT parameter record, 194
SUMMARY BY STATE field (REPORT), 194
Summary by State Report, 194
Support website, 353, 518
Syntax
checking with TESTIT parameter record, 213
Working With CODE-1 Plus
Syntax, checking with TESTIT, 390
T
Tape Reel Handling
FILEDF parameter record, 163
Target
MOVE I parameter record, 184
MOVE O parameter record, 185
Temporary work area, 183, 185
TESTIT parameter record
defined, 210, 213
TESTIT parameter record (for G1G001)
defined, 390
field-by-field, 390
U
UAA, 339
UFTxx parameter record
defined, 214
FOOTER TEXT, 214
LINE NUMBER, 214
LINE SIDE, 214
UFTxx parameter record (for G1G001)
defined, 381
field-by-field, 381
FOOTER TEXT, 381
LINE NUMBER, 381
LINE SIDE, 381
UHDxx parameter record
defined, 215
HEADER TEXT, 215
LINE NUMBER, 215
LINE SIDE, 215
UHDxx parameter record (for G1G001)
defined, 382
field-by-field, 382
HEADER TEXT, 382
LINE NUMBER, 382
LINE SIDE, 382
Uncoded records
correcting in Interactive environment, 307
undeliverable-as-addressed, 339
Unique Zip and Small Town, 340
Unique ZIP Handling, 126
Z5 OUT parameter record, 224
UNIX shell script
for G1G001 (report generator), 395
for Z4CHANGE (C1P430) reports, 319
UNPK parameter record (for G1G001)
defined, 391
field-by-field, 391
557
IX
Index
UR command
for correcting uncoded records, 308
User exit routines
for correcting uncoded records Interactive, 311
User ID
finding, 353, 518
USER-SPECIFIED CONFIG. field (CONFIG), 125
USPS
RDI processing, 355
USPS FIPS COUNTY CODE field, 168
USPS Form 3553, 123, 192
define list ID (LISTID), 178
define list name (LISTNM), 179
define mailer information (MAILER), 182
overriding certification data (CASSA1), 117
separate print file, 196
USPS Form 3553 Separate Print File
REPORT parameter record, 196
USPS-preferred
city name, defined, 276
USPS rules and exception
for Z4CHANGE processing, 314
UW command
for correcting uncoded records, 309
V
Vanity city names, returned, 128
W
Walk Sequence Codes
not the same as Line of Travel, 180
Website
support, 353, 518
What is a Multiple Match?, 340
What is Auxiliary File Processing?, 366
What is Delivery Point Validation?, 339
What is EWS?, 366
What is Line of Travel?, 322
What is Residential Delivery File processing?, 355
What is the Early Warning System?, 366
Why Use Line of Travel?, 322
Windows NT batch file
for G1G001 (report generator), 396
for Z4CHANGE (C1P430) reports, 319
Z
z/OS JCL
for G1G001 (report generator), 394
558
Z4CHANGE
overriding certification data (CASSA4), 119
Z4CHANGE processing
activating, 315
calling from your own driver, 317
database requirements, 314
defined, 314
parameter records, 315
reports generated, 318
using, 315
USPS rules and exception, 314
Z4CHANGE reports
UNIX environment, 319
Windows NT environment, 319
Z4 OUT parameter record
defined, 216
DELIVERY POINT BARCODE, 217
DISPOSITION INDICATOR, 220
DPBC WITH CHECK DIGIT, 217
MASTER FILE VINTAGE DATE, 217
MAXIMUM ADDRESS CORRECTNESS, 218
MAXIMUM OVERALL CORRECTNESS, 218
Storage conditions INFORMATION DROPPED, 218
Storage conditions MULTIPLE ZIP+4, 219
Storage conditions MULTIPLE ZIP CODE, 219, 224
Storage conditions ZIP+4 (DPBC) suppressed for R777
records, 218
ZIP+4 CODE, 216, 217
ZIP+4 RETURN CODE, 216
Z5 OUT parameter record
defined, 221
DISPOSITION INDICATOR, 224
location for SOURCE OF FINAL ZIP CODE, 223
MAXIMUM ADDRESS CORRECTNESS, 223
MAXIMUM OVERALL CORRECTNESS, 223
PO BOX-ONLY ZIP CODE, 223
Storage conditions INFORMATION DROPPED, 223
UNIQUE ZIP HANDLING, 224
Valid ZIP Code flag, 223
ZIP CODE, 222
ZIP CODE RETURN CODE, 222
ZIP+4 Code
Z4 OUT parameter record, 216
ZIP+4 Coding by 3-Digit ZIP Code
REPORT parameter record, 194
ZIP+4 CODING BY 3-DIGIT ZIP field (REPORT), 194
ZIP+4 Coding by 3-Digit ZIP Report, 194
ZIP+4 Coding by List Code
REPORT parameter record, 193
ZIP+4 CODING BY LIST CODE field (REPORT), 193
ZIP+4 Coding by List Code Report, 193
ZIP+4 Coding by State
REPORT parameter record, 192
ZIP+4 CODING BY STATE field (REPORT), 192
ZIP+4 Coding by State Report, 192
ZIP+4 Return Code
Z4 OUT parameter record, 216
ZIP Code
Software Release 4.0.0/March 2015
IX
handling of unique, 224
Valid ZIP Code flag, 223
where to store on the output record, 221
Z5 OUT parameter record, 222
ZIP Code Return Code
Z5 OUT parameter record, 222
ZIP Codes, confirming special, 130
Working With CODE-1 Plus
559
IX
560
Index
Software Release 4.0.0/March 2015
Feedback
Document Title:
Working with CODE-1 Plus Guide
Document Date:
March 2015
Software Version: 4.0.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

advertising