Introduction - · Web viewAppendix A - Synonym and Word Classes 65. Appendix B - Glossary 66. Appendix C - Corrected Records Report 68. Appendix D - Uncorrected Records Report

Chapter 1 Introduction_________________________________________________1Program Overview____________________________________________________________1

Technical Overview___________________________________________________________2

Chapter 2 Installation__________________________________________________3Installation Requirements______________________________________________________3

Installation Steps_____________________________________________________________3

The Directory System__________________________________________________________4

Directory Updates_____________________________________________________________4

Chapter 3 System Overview______________________________________________5The Input File and its Formats__________________________________________________5

Parameter File_______________________________________________________________5

Canadian Addressing Overview_________________________________________________5Types of Canadian Addresses_________________________________________________________5Addressing Issues___________________________________________________________________7

Output Files_________________________________________________________________9In REGULAR Mode:________________________________________________________________9

Reports____________________________________________________________________10Record Reports____________________________________________________________________10Summary Reports__________________________________________________________________11

Dr. Q JCL__________________________________________________________________13

Chapter 4 Running Dr. Q______________________________________________15Analyzing Your Output Needs_________________________________________________15

Extraneous Information_____________________________________________________________15Changing File Layouts______________________________________________________________15Bar Coding (4 State Solomon Reed Bar Code)___________________________________________15Eliminating Duplicate Addresses_____________________________________________________16Updating a Master File_____________________________________________________________16Upper Case Translation_____________________________________________________________17Printing from the Returned Information________________________________________________17

Navigating the Parameter File_________________________________________________18Overview of Parameters_____________________________________________________________18Parameter Syntax__________________________________________________________________18Report Information_________________________________________________________________20Input File Description______________________________________________________________22Output Areas_____________________________________________________________________24Run Conditions___________________________________________________________________32Determining Output Area Record Layout_______________________________________________34Calculating the LRECL of other Files__________________________________________________37Parameter Table___________________________________________________________________39

Chapter 5 Synonyms__________________________________________________45Synonyms Overview__________________________________________________________45

Adding New Synonyms_______________________________________________________45

Page -1-

Chapter Chapter 1 , Introduction

Chapter 6 Technical Overview__________________________________________46Provided Source Module______________________________________________________46

Setup of FT06 (without using parameter edit)____________________________________55

Intercepting at I/O Exit Points_________________________________________________62

Tools, Samples and JCL Provided______________________________________________63

Chapter 7 Appendices_________________________________________________65Appendix A - Synonym and Word Classes_______________________________________65

Appendix B - Glossary________________________________________________________66

Appendix C - Corrected Records Report_________________________________________68

Appendix D - Uncorrected Records Report_______________________________________69

Appendix E - Correction Summary Report______________________________________70

Appendix F - Statement Of Accuracy___________________________________________71

Appendix G - Release History__________________________________________________72September 2001 Release 2.7_________________________________________________________72March 2001 Release 2.6_____________________________________________________________72Sept 2000 Release 2.5______________________________________________________________72June 1999 Release 2.4______________________________________________________________72April 1998 Release 2.2(5)___________________________________________________________72January 1998 Release 2.2(4)_________________________________________________________73May 1997 Release 2.2(0)____________________________________________________________73

Appendix H - “Fixed CPC buffer” Description___________________________________75

Appendix I - Error Codes on UNCOR file at LRECL+1____________________________76

Page -2-

Chapter 1 Introduction

Program OverviewDr. Q provides a single pass process for address correction, standardization and validation. PRISM Data Services has combined both the logistics of our proven address management products and the complexities of Canadian addressing components into a single pass, comprehensive address management system.

PRISM has a long history of address correction and postal code verification and has provided a full range of products to users for over 15 years. With its solid history of address management solutions, we introduce Dr. Q as a product built entirely for the user.

Dr. Q is tested on millions of addresses with a variety of our own service bureau customers. Because PRISM’s service bureau is a user of Dr. Q, we can promise timely, accurate software updates at prices covered in your maintenance agreement.

Dr. Q provides users with an assortment of techniques to help you make your address maintenance tasks more personalized. You will quickly learn that Dr. Q provides easy to use parameters to control the validation and correction methods needed for your address database. With parameters users control:

the description of the input address file the address management areas which are to be returned on your records the mode of operation you require for your address file the format and contents of all the output records

Dr. Q provides users with the capability of providing synonyms for Canada Post elements that are found on the master database. Running the easy to use User Synonym program can help Dr. Q acquire the same local knowledge that your operators had when they originally entered the address.

Dr. Q produces an assortment of comprehensive reports. The software produces a certified Statement of Accuracy Report to present to Canada Post, a summary of the correction run, a report of the corrections performed on your address file and a bi-directional report on the rejected records. The report on the rejected records indicates the errors that were produced from the postal code and what errors were generated by using the incoming address. This gives you a comprehensive overview of the addressing problems with each record and provides clues about how to correct the record.

Without modifying the default parameters or synonym files, a single pass of Dr. Q can change an accuracy rating from 60% to upwards of 95%. Rejected files are fully compatible with PRISM ‘s On-Line Correction product. Used together, you can obtain accuracy ratings well beyond Canada Post’s expectations.

Page -1-

Dr. Q is a powerful tool designed specially for large volume mailers who need help in managing their addressing problems. Remember, Dr. Q’s primary intention is to provide the highest CPC accuracy rating for the address presented to it. It makes no attempt to change the address of your client records, only to optimize your mail.

Technical Overview Dr. Q is written in Assembler. PRISM supplies the entry to Dr. Q as both a COBOL II program and an Assembler H program, which can be used as a sample to help you incorporate Dr. Q into an existing system. The program calls two programs, the main Dr. Q module, and a generic file read program. Also included with Dr. Q is the source code to all of the exit points whenever I-O is going to occur. In modifying these exit points you can include a complete address maintenance system as part of your existing system.

Because of it’s dynamic design, our product instantly compliments your current maintenance systems and allows your system staff to become quickly involved in ensuring your addresses are accurate and your addressing issues are solved.

For systems staff who are interested in modifying our source programs, see Chapter Chapter 6 for information about Dr. Q’s calling conventions and Dr. Q’s I-O interfaces.

Page -2-

Chapter 2 Installation

Installation RequirementsDr. Q runs on MVS/XA, MVS/ESA, LE370 or OS390 with approximately 120 cylinders of 3380 or 3390 DASD space.

Precaution must be taken for systems with both 3380 and 3390 DASD units and DFHSM to ensure when datasets are restored from tape, they are restored to the same unit type as they resided on when the directory was built.

Installation StepsInstallation of Dr. Q involves:

1. Upload the JCL file from the system tape. As with all PRISM system tapes this will be a Fixed Block, LRECL 80 dataset always on the first label of an IBM standard labeled tape or 3380 cartridge. A sample of download JCL is found in Figure Chapter 2 -1 Example JCL for Uploading the Install JCL.

2. Make the required changes to the JCL. The comments in the JCL stream will describe each of the changes, which you must make. For example, the comment may ask you to change all !LIB! to your preferred library prefix. If you are using SPF, you might type in “CHANGE ALL !LIB! PRISM.DRQ.LIB”.

3. Submit the JCL stream.4. Build the directories by inserting your JOBCARD in the JCL found in

yourlib.name.DIR.JCL(DRQDIRLD), and submitting the JCL. For more information about the directories, see Directory Updates on page 4.

You may be required to add block sizes to the PDS

//JOBCARD//**//** EXAMPLE COPY OF THE INSTALL JCL TO DASD//**//** CHANGE PRISMC TO PRISMT IF YOUR SYSTEM WAS PROVIDED ON REEL TAPE (6250 BPI TAPES)//** CHANGE UNIT TO THE APPROPRIATE UNIT NAME FOR THE MEDIA OF THE SYSTEM TAPE//** CHANGE THE VOLSER TO MATCH THE VOL SER OF THE SYSTEM TAPE PROVIDED//** CHANGE “MYLIB” TO A PDS WHERE YOU WANT TO COPY THE INSTALL JCL TO//**//IEBGENR EXEC PGM=IEBGENR//SYSUT1 DD DISP=(OLD,KEEP),DSN=PRISMC.DRQMA.INSTALL,// UNIT=TAPE,VOL=SER=??????,LABEL=(1,SL)//SYSUT2 DD DISP=SHR,DSN=MYLIB(DRQINST)//SYSIN DD DUMMY//SYSOUT DD *

Figure Chapter 2 -1 Example JCL for Uploading the Install JCL

Page -3-

Chapter Chapter 2 , Installation

The Directory SystemDr. Q’s directory system contains 4 files. The four files contain all of the information we receive from Canada Post about the Canadian Mailing system. Each file has been optimized for both space and ease of access by Dr. Q’s internal file handling routines.

DSNAME ending qualifier Purpose

VBDIR Sequential Variable Blocked file containing Memory Images loaded every Dr. Q run. Some of the tables within the VBDIR are used to point to areas within the other files to allow Dr. Q to access data in an efficient manner.

RNG00120 Contains the postal station Information which is used to construct postal station type directory entries.

RNG00020 Contains Street entries used to construct street type directory entries.

PCRNG Contains information which is used to construct directory entries using the postal code as a key.

Figure Chapter 2 -2 Dr. Q Directory Files

In order to permit our users to access the information provided to us by Canada Post, Dr. Q provides a “toolkit” program called “DRQT0105”. To find more information about how the new toolkit member works, see DRQT0105 in Chapter Chapter 6 Technical Overview on page 59.

Directory UpdatesThe directory updates, shipped on 3480 cartridge are sent to each client either monthly or bi-monthly as requested. In order to upload and create the new directory files, run the JCL library member called DRQDIRLD in the DIR.JCL PDS (library). Each time you update the new directories, you will be required to change the tape number as supplied by PRISM and re-run this entire JCL. This JCL is required to create the entire set of 4 directory files and rebuild the directory cross references found in VBDIR.

Page -4-

Chapter 3 System Overview

The Input File and its FormatsThe input file to Dr. Q must be a “sequential flat file” i.e. “DSORG=PS,RECFM=FB” and have one mailing address per record in a fixed position on each record. The maximum record length depends on the requested layout of the output files. A 32K byte area is supplied for Dr. Q to manage all of the returned areas. Dr. Q also uses 332 bytes of the 32K area as a working storage area before the returned information is constructed.

The maximum record length (nearly 32,000 bytes) therefore can only be determined after your output requirements have been determined.

For more information about determining the maximum size of the output file see page 32.

The input file may be:

a member of a partitioned dataset a temporary file defined instream in the JCL a regular sequential dataset

If the input file is to be allocated through Dr. Q’s dynamic allocation routines (through the parameter DSNAME), the input file must be a regular catalogued QSAM dataset which is available for use as “shared”.

Parameter FileThe parameter file contains information about each particular Dr. Q run broken down into four categories. The parameter file can be between 80 and 132 bytes in length, must be of a format FB and may or may not contain SPF standard numbering. The flexibility to control all of the functions available in Dr. Q is controlled with the single parameter file.

Canadian Addressing Overview

Types of Canadian Addresses

Street Addresses (type 11)A street address is our typical Canadian mailing address. In most cases, a street address contains the following components:

Street Number Street Name

Page -5-

Chapter Chapter 3 , System Overview

Street Type (usually present, but not always) Street Direction (not always present)

A street address can also contain more specific information about the delivery point. In Canadian street addresses, one might also find:

A suite number and keyword A street suffix Essential delivery information, which is not required for validity (2nd Floor,

Accounting Department, U of T Science Wing, etc.)

Street Served by Route Service (type 21)Street served by route service addresses are addresses, which contain all pertinent street information and may contain the extra component of a route keyword and number. Street served by route records may or may not have the route keyword. Some of these addresses may also not have a street number. An example of a street served by route might be one of the following:

Mr. Smith10 ELWOOD PL SS 10 BELLEVILLE ON K8N 4Z3

Mr. Smith2135 BAINES RDCOBBLE HILL BC V0R 1L0

Mr. SmithBENCH RD RR 3COBBLE HILL BC V0R 1L0

There are special rules concerning street served by route addresses.

Street served by route addresses do not need the route information (SS 10, RR 5, etc.), providing that the postal code has a zero in the second digit, and a street number is present on the address.

A street number is required if the “street number to” field is not 999999. If an address is given with the route information or the street number, it must be retained even if it is not required.

Postal Office Box Addresses (type 32)This form of addressing is popular throughout both urban and rural Canada. There are two types of box type addresses though they are not presented differently. In metropolitan areas, companies or individuals can rent Post Office boxes at a local post office. In rural areas, the population of a small town is sometimes assigned boxes at the local post office. Post Box addresses must contain:

The PO BOX keyword and number The station name (if different from the city name) The station type (if the station qualifier is not blank or there is more than one

station in the community) The station qualifier (if it is not blank)

Page -6-


Route Service Delivery Addresses (type 42)

These addresses are more common to rural areas. The mail is not delivered to the actual door. Delivery points vary within these record types. For some, mail is retrieved at a community mail box, and for others, mail is delivered to mail boxes along the route. There are three basic types or service within this category, Rural Route, Suburban Service and Mobile Route Service. These addresses require the following components:

The Route Class keyword (RR, MR, or SS) and number The station name (if different from the city name) The station type (if the station qualifier is not blank or there is more than one

station in the community) The station qualifier (if it is not blank) Any delivery information which may be required to ensure accurate delivery

(such as SITE 3, COMP 2 etc. see Valid yet Undeliverable on page 9)

General Delivery (type 52)

General Delivery mail is sorted to the station and then by name at the postal station. Although this class is more common in rural areas, there is general delivery type addressing at some urban postal stations. These addresses require the following components:

The General Delivery keyword (GD) The station name (if different from the city name) The station type (if the station qualifier is not blank or there is more than one

station in the community) The station qualifier (if it is not blank) Any delivery information which may be required to ensure accurate delivery

(such as C/O Janus Boil, 817 Main Street etc. see Valid yet Undeliverable on page 9)

Addressing Issues

Rural and LVR (large volume receiver) AddressesCanada Post counts all records with a zero in the second digit of the postal code, and which is on the Canada Post directory as automatically being valid, regardless of the data in the address record. As well, all records with postal codes that are identified as being valid large volume receiver postal codes are also considered valid regardless of the information in the address lines. Dr. Q is designed to be used as an address management tool and as a means to obtain a statement of accuracy users should fully understand the complexities of this issue.

Page -7-


For all other addresses, a thorough examination of the address elements takes place and all information in the addresses is crossed checked against Canada Post data. When user information matches that which supplied by Canada Post, the chances are good that the address is correct and the mail-piece will reach the intended recipient. When the address data isn’t verified, there is a chance that the mail will not reach the intended recipient, or that the mail will reach the recipient with significant delays.

Canada Post however, does not assure users that the information on the directory for rural addresses is complete or accurate. Which leads to the possibility, that a software package, using the rural address data for address correction, could improperly change the address information to match Canada Post’s inaccurate data.

All resolves to this issue lie at Canada Post. The software has been designed to give users the flexibility of choosing whether or not to correct rural and LVR addresses.

When creating an address accuracy report for Canada Post, it is important that you do not remove rural addresses from the input file as they help improve your final accuracy.

Suite KeywordsOn the Canada Post database are a number of records where they postal code points to an exact suite or suite range. When the address requires you have a suite number on your database, you are required to mark that suite number by using a suite keyword or by putting the suite number before the suite number followed by a dash “-”.

e.g. 2-425 HORNER AVE

Canada Post maintains a list of recognized suite keywords. As of May 1, 1997, these are the only valid suite keywords:

Apartment APT Apartment APP Suite Bureau Unit PH Penthouse RM Room Piece Salle TH Townhouse TNWHSE

If there is no suite range on the database, any suite number, and any suite keyword is valid. A number sign “#” is never considered valid anywhere in any address.

Page -8-


Urbanization and 911Canada Post has been changing rural addressing into urban addressing over the past few years. The overall objective of Canada Post is to Urbanize all of Canada by assigning a street address to every household. 911 projects are also taking place in many municipalities to make sure every household in a 911 emergency area has a street number. If a fire or other emergency occurs, you can’t very well tell the 911 operator that you live at PO Box 118 STN MAIN.

Canada Post is cooperating with the municipalities during these transition phases to ensure proper maintenance of their directory files. To a user of Canada Post services, the biggest difficulty is that the only link between the customers old address (RR 5 STN MAIN) and the new (187 KING ST) is the customers name, which is not stored on the Canada Post Directories.

Some provinces have decided to assign urban addressing themselves. Canada Post works with the province to populate their directories at the same time. Currently Canada Post offers a free conversion facility (you send them your records) for all affected postal codes.

Valid yet UndeliverableSome information that is required for the timely delivery of a mail piece may not retained by Canada Post on their database. Above we discussed the type of addressing "Route Service". Because of the number of people who can be serviced on one delivery route, it is sometimes necessary to include more information than the name of the recipient.

A record that Dr. Q considered to be valid or is corrected to optimal Canada Post standards, can therefore be returned marked "unknown address". This is because the letter carrier or sorter could not identify they physical site of where to put the mail by the name alone.

Output FilesDr. Q will create up to 5 output files, depending on the Run Class and your JCL statements. The total number of records contained in all of the output files always total the number of records contained in the original file. The five files, which can be created, are UNCOR, CORRECT, ACCEPT, RURFILE and OSZFILE.

In REGULAR Mode:The following table indicates what files can be use in Regular mode (column headings), the format of the file, and the records, which you can expect to find on them. When the format = U, the file layout will match the layout requested in the “OUTPUT DESCRIPTION” parameters.

Page -9-


VALID (Format = U)

CORRECT(Format = U)

OSZFile(Format = O)

UNCOR(Format = U or Format = O)

RURFILE(Format = U or Format = O)

Reformat = Yes, Rural Correction = Yes

Valid Address Data and matching postal code

Corrected address data with matching postal code

All oversized Records (must be specified)

Uncorrectable urban data (Format = U)

Uncorrectable address data/rural records (Format = U)

Reformat = No, Rural Correction = Yes

Valid Address Data and matching postal code

Corrected address data with matching postal code

Valid and Corrected Oversized records

Uncorrectable urban data (Format = O)

Uncorrectable rural data (Format = O)

Reformat = No, Rural Correction = No

Valid URBAN records

Corrected Urban (on input) records

Valid and Corrected Oversized records

Uncorrectable urban data (Format = O)

ALL rural Addresses (Format = O)

Reformat = Yes, Rural Correction = No

Valid URBAN Records

Corrected Urban (on input) records

All oversized Records (must be specified)

Uncorrectable urban Data (Format = U)

All Rural addresses (Format = U)

Figure Chapter 3 -1 Dr. Q Directory Files

* Format=U, is the user defined layout as specified in the Output Description parameters.** Format = O is returned in the original format.

The files “CORRECT”, “RURFILE” and “OSZFILE” are optional. If the “Correct” file is not specified, records which would be placed in the Correct file are placed into the “Valid” file. If the “Rurfile” is not specified, records which would be normally placed in the “Rurfile” are put in the uncorrectable file. The OSZFile must be specified if the “REFORMAT ALL RECORDS” is set to yes. If the “REFORMAT ALL RECORDS” parameter is set to no, and the OSZFile does not exist, oversized records are placed on the UNCOR file.

ReportsDr Q produces two classes of reports. For the purpose of this manual we describe the two classes of the reports as Summary Reports and Record Reports. All reports are 132 character wide with a maximum of 55 lines on a page.

Record ReportsWith correction runs, two reports are produced. Each time Dr. Q evaluates a record as correctable, the record is listed on the Corrected Records Report. Records which are not correctable, are listed on the Uncorrectable Records Report. Valid records are not listed on any report. When run in “Verify” mode, no Record Reports are produced.

Page -10-


UCR8000Uncorrected Records Report This report lists each uncorrectable address, any user

specified fields for the record, the major category of the error (irresolvable address or ambiguous address), and error messages for the most likely addresses. Most addresses on the Uncorrected Records Report are undeliverable.

CRR8000Corrected Records Report This report lists the original address fields, any user

specified fields, the output fields, and messages about the corrections performed. The messages tell what error was corrected and how the error was identified.

Summary ReportsSummary Reports are reports that are produced at the end of every run of Dr. Q. There are two summary reports, the Statement of Accuracy Report and the Correction Summary Report.

CPCREPStatement of Accuracy This report is submitted to CPC either with every

Statement of Mailing (SOM), or once annually, depending on the amount of change within your address file and your mailing needs. To further clarify when this report is to be submitted, talk to your Canada Post Representative. Run in Regular mode, this report is two pages in length. The first page indicates what the file looked like before address correction, and the second indicates what the file looks like after address correction. Run in verify mode, the report will produce a one page report indicating the accuracy of the file, without correction.

CORSUMCorrection Summary Report This report is for your own use. The report summarizes:

The number of urban, rural and total records valid on input, corrected throughout the Dr. Q run, and were uncorrectable.

A summary of the oversized records and the line numbers which caused the oversized errors to occur.

Page -11-


Special note for Lettermail (First Class) Mailings

Prism strongly recommends customers who are correcting address for Lettermail mailings, set the following RUN parameters to “NO”

OPTIMIZE PROVINCE (NO) OPTIMIZE COMMUNITY (NO) OPTIMIZE OTHER COMPONENTS (NO)

Coding these parameters “YES” will cause client addresses to be modified to the official Canada Post Corporation (CPC) code/name standards. In many cases the input data has language formatted and/or valid alternate data that the mail recipient has requested and does not want this data to be modified or changed.

Examples of these cases is where the input data may be:- French formatted or accented data and would be modified to English terminology

in a predominately French populated area or visa versa. - Valid alternate municipal name that would be changed to the CPC directory

name, which may not be the locally colloquial name.

In applications that call DRQ via the FT06COB copy book, move “N” to the following fields:

DRQRC-OPTIMIZE-PROVINCE DRQRC-OPTIMIZE-COMMUNITY DRQRC-OPTIMIZE-OTHER

In applications that call DRQ via the FT06 copy book, move “N” to the following fields:

FT6OPPRFT6OPCM

FT6OPCO

Page -12-


Dr. Q JCLThe JCL required to run Dr. Q depends directly on how much information you want to define in the parameter files. In Figure Chapter 3 -2 and Figure Chapter 3 -3 the minimum JCL/ maximum parameter file, and the maximum JCL/minimum parameter file JCL is shown.

//PRS0001 JOB (PRISM),'** DRQ (MAX)**',CLASS=C,MSGCLASS=X,// NOTIFY=PRS0001,TIME=1440//*//* MAXIMUM JCL, MINIMIMUM PARAMETER FILE JCL//*//JOBLIB DD DISP=SHR,DSN=PRISM.DRQ.LIB.LOAD//*//* DELETE DATASETS//*//IE EXEC PGM=IEFBR14//DD1 DD DISP=(MOD,DELETE,DELETE),DSN=PRISM.DRQ.SEQ.ACCEPT,// UNIT=PERMDA,SPACE=(TRK,(1,1),RLSE)//DD2 DD DISP=(MOD,DELETE,DELETE),DSN=PRISM.DRQ.SEQ.REJECT,// UNIT=PERMDA,SPACE=(TRK,(1,1),RLSE)//DD3 DD DISP=(MOD,DELETE,DELETE),DSN=PRISM.DRQ.SEQ.CORRECT,// UNIT=PERMDA,SPACE=(TRK,(1,1),RLSE)//DD3 DD DISP=(MOD,DELETE,DELETE),DSN=PRISM.DRQ.SEQ.OSZFILE,// UNIT=PERMDA,SPACE=(TRK,(1,1),RLSE)//*//* RUN DOCTOR Q//*//STEP01 EXEC PGM=DRQV21,REGION=0M//SYSOUT DD SYSOUT=*//*//* SUMMARY REPORTS//*//CORSUM DD SYSOUT=*//CPCREP DD SYSOUT=*//*//* INDIVIDUAL RECORD REPORTS//*//UCR8000 DD SYSOUT=*//CRR8000 DD SYSOUT=*//*//* CONTROL PARAMETERS//*//CNTLPARM DD DISP=SHR,DSN=PRISM.DRQV20.LIB.CNTLPARM(MINPARM)//*//* INPUT AND OUTPUT FILES//*//MYINPUT DD DISP=SHR,DSN=PRISM.DRQ.SEQ.INPUT.FILE//OSZFILE DD DISP=(,CATLG),DSN=PRISM.DRQ.SEQ.OSZFILE,// UNIT=DASD,SPACE=(TRK,(10,10),RLSE),LRECL=695//ACCEPT DD DISP=(,CATLG),DSN=PRISM.DRQ.SEQ.ACCEPT,// UNIT=DASD,SPACE=(TRK,(10,10),RLSE),LRECL=695//CORRECT DD DISP=(,CATLG),DSN=PRISM.DRQ.SEQ.CORRECT,// UNIT=DASD,SPACE=(TRK,(10,10),RLSE),LRECL=695//UNCOR DD DISP=(,CATLG),DSN=PRISM.DRQ.SEQ.REJECT,// UNIT=DASD,SPACE=(TRK,(10,10),RLSE),LRECL=695//*//* DIRECTORY FILES//*//VBDIR DD DISP=SHR,DSN=PRISM.DRQ.SEQ.VBDIR//PCR1 DD DISP=SHR,DSN=PRISM.DRQ.SEQ.PCRNG1//RNG4 DD DISP=SHR,DSN=PRISM.DRQ.SEQ.RNG00020//RNG4 DD DISP=SHR,DSN=PRISM.DRQ.SEQ.RNG00120

Figure Chapter 3 -2 DRQ JCL, Maximum JCL/Minimum Parameter

Page -13-


//PRS0001 JOB (PRISM),'** DRQ (MIN)**',CLASS=C,MSGCLASS=X,// NOTIFY=PRS0001,TIME=1440//*//* MINIMUM JCL, MAXIMUM PARAMETER FILE//*//JOBLIB DD DISP=SHR,DSN=PRISM.DRQ.LIB.LOAD//*//* DELETE DATASETS//*//IE EXEC PGM=IEFBR14//DD1 DD DISP=(MOD,DELETE,DELETE),DSN=PRISM.DRQ.SEQ.ACCEPT,// UNIT=PERMDA,SPACE=(TRK,(1,1),RLSE)//DD2 DD DISP=(MOD,DELETE,DELETE),DSN=PRISM.DRQ.SEQ.REJECT,// UNIT=PERMDA,SPACE=(TRK,(1,1),RLSE)//DD3 DD DISP=(MOD,DELETE,DELETE),DSN=PRISM.DRQ.SEQ.CORRECT,// UNIT=PERMDA,SPACE=(TRK,(1,1),RLSE)//*//* RUN DOCTOR Q//*//STEP01 EXEC PGM=DRQV21,REGION=0M//SYSOUT DD SYSOUT=*//*//* SUMMARY REPORTS//*//CPCREP DD SYSOUT=*//CORSUM DD SYSOUT=*//*//* INDIVIDUAL RECORD REPORTS//*//UCR8000 DD SYSOUT=*//CRR8000 DD SYSOUT=*//*//* CONTROL PARAMETERS//*//CNTLPARM DD DISP=SHR,DSN=PRISM.DRQ20.LIB.CNTLPARM(MAXPARM)//*//* OUTPUT FILES//*//ACCEPT DD DISP=(,CATLG),DSN=PRISM.DRQV20.SEQ.ACCEPT,// UNIT=DASD,SPACE=(TRK,(10,10),RLSE),LRECL=695//UNCOR DD DISP=(,CATLG),DSN=PRISM.DRQV20.SEQ.REJECT,// UNIT=DASD,SPACE=(TRK,(10,10),RLSE),LRECL=695

Figure Chapter 3 -3 DRQ JCL, Minimum JCL, Maximum Parameter

Page -14-

Chapter 4 Running Dr. Q

Analyzing Your Output Needs

Extraneous InformationAlthough all extraneous information is grouped into one category in Dr. Q, in the correction process and within your address records, users can find up to three categories. The three categories of extraneous information which Dr. Q cannot differentiate are; essential delivery information such as SITE 3, COMP 2, Non-Address customer information such as ACCT # 71001, and non-essential unidentifiable address misspellings such as CLEM instead of CRESCENT or AC instead of AVE. One of the understandably difficult areas associated with the address correction process, is deciding which information is required to keep, and where should it be kept. Dr. Q allows users to move extraneous information to a separate line. If the address database is for Lettermail or contains extremely sensitive data, users are encouraged to manually search records which contain extraneous data.

Changing File LayoutsAs well as providing an area which helps you identify duplicate address records, Dr. Q comes with the flexibility of reorganizing two address files and reformatting your address components to match. By using the same Output Areas parameter, two files with different input structures look identical on output.

This greatly simplifies merging databases with one or more structures. For a multi-file mailing application, mailers now have the ability to combine databases for printing quickly and easily through parameters.

Bar Coding (4 State Solomon Reed Bar Code)Dr. Q allows users to place barcode information directly into their file. A user can combine this output area with details about the sort and pass the area into Canada Posts PEM modules to apply the actual barcode to each address. In order to generate the information used by Canada Post’s PEM, users code the POCI output area. Users can then easily pass the POCI onto the PEM module to obtain the actual POSTBAR digits.

Page -15-

Chapter Chapter 4 , Running Dr. Q

Eliminating Duplicate AddressesDr. Q has a powerful return area entitled the “Merge Purge Code”. A unique merge purge code is assigned to every address in Canada. Although the merge purge code is unique for every address in Canada, caution must be taken when the address itself is not unique to individual recipients. The merge purge code for the unique address RR 1 STN MAIN, BURLINGTON ON will contain more than one recipient. The same is likely true for those living in areas serviced by General Delivery. Canada Posts' thrust is to eliminate these address types over the next several years through its urbanization program.

A field with the merge purge code has been assigned to indicate a unique or multi delivery point address. The format of the merge purge code can be found on page 25.

Updating a Master FileIf you are updating a master file, several questions must be asked before the JOB starts. Updating address records is always a sensitive issue. Users are encouraged to understand what potential problems may exist in updating their customers address records.

Specific decisions need to be made to ensure that records are corrected. Areas for consideration include existing address data format, sensitivity of customers’ address data, upper and lower case data, and desired accuracy level. Dr. Q’s optimization techniques range from aggressive to passive. There are four areas which users can control whether or not you want Dr. Q to return the original valid record, or to return the Canada Post Optimal. These four areas are province, community name, street type/street direction and route keywords.

Consider the following examples of what might be valid records:

Example 1:

425 HORNER AVENUETORONTO ONT M8W 4W3

Optimize Other ComponentsAVENUE can be standardized to AVE by setting the OPTIMIZE OTHER COMPONENTS to Yes. If the OPTIMIZE OTHER COMPONENTS is set to No, Dr. Q will leave it as AVENUE because it is valid.

Optimize CommunityTORONTO (assuming it is a valid alternate of ETOBICOKE) can be standardized to ETOBICOKE by setting the OPTIMIZE COMMUNITY to Yes. If it is set to No, the community will remain as the valid alternate, TORONTO.

Optimize Province

Page -16-


ONT can be standardized to ON by using the OPTIMIZE PROVINCE switch. When off ONT will remain as it is an acceptable alternate of ON as a province.

Example 2:

P.O. BOX 4125 STATION MTORONTO ONT M8Z 9Z3

Optimize Route KeywordsOptimizing “P.O. BOX” to PO BOX is controlled by the OPTIMIZE ROUTE KEYWORDS parameter. If this parameter is set to Yes, the word “P.O. BOX” will become PO BOX. If the parameter is No, because P.O. BOX is valid, Dr. Q will return “P.O. BOX”.

Optimize Other ComponentsYou can use the OPTIMIZE OTHER COMPONENTS parameter to control whether or not you want the station type to be optimized. In this case, setting this parameter to yes, will cause Dr. Q to optimize STATION to the optimal abbreviation STN.

In cases where Dr. Q must correct anything other than punctuation, Dr. Q will choose the Alternate. If the word AVENUE had appeared as “AVENUED” in example one, Dr. Q would have changed it to AVE, regardless of the OPTIMIZE OTHER COMPONENTS flag.

Upper Case TranslationUsers can also control whether or not Dr. Q is to return the addresses in upper case or lower case. Usually for more sensitive mailings, you can control this by setting the LOWER CASE TRANSLATION parameter to ON.

Because Dr. Q understands the addressing requirements, it is very accurate at assigning the proper case translation for most words. For example, a more simplistic program might otherwise make the word “NWT” “Nwt”, Dr Q. will retain the proper case as NWT. Similarly, “PO BOX 300” might be changed to “Po Box 300”, Dr Q properly changes it to “PO Box 300”.

Printing from the Returned InformationSome users would prefer to never update their address records. When information is returned on records, the information can be used to directly print the actual mailing labels. Because the statement of accuracy returned is an indication of your address file on the corrected output, you can use this area for printing addresses on the letterpiece and never update your master file.

Page -17-


Navigating the Parameter File

Overview of ParametersDr. Q has is very flexible and comprehensive by including a range of parameters which help you obtain all of address management requirements. The parameters are broken into four easy to understand areas which you tell Dr. Q:

The description of the input file Information necessary for the reports What corrected and valid records should look like when the run is complete What internal processing options you want Dr. Q to use

The parameter statements are English and are quite simple to follow. The parameter structure is similar in nature to some IBM utilities including IDCAMS. Examples are provided throughout this documentation and with the system.

Parameter SyntaxThe parameters are divided into four keyword groups:

REPORT INFORMATION INPUT FILE DESCRIPTION OUTPUT AREAS RUN CONDITIONS

The parameter must reside in a file of between 40 and 132 characters and may or may not have SPF standard numbers in the rightmost 8 bytes. These numbers are ignored by the parameter syntax editor.

Blank lines are permitted and ignored by the parameter syntax editor.

Lines within each of the four categories (except for comment and blank lines), must be continued with the dash character (-). Any line proceeding a line without a dash character will be considered a new category, regardless of the number of ending brackets.

Comment lines are identified by an asterisk (*) in column 1. There is no need to place a continuation character on blank lines or comment lines.

When proper punctuation and case is required, enclose the item in quotation marks within the brackets. YOU MUST USE PAIRED QUOTATION (apostrophe) CHARACTERS, therefore apostrophes are not allowed anywhere in text.

Dr. Q comes with a number of sample parameter files. Users are encouraged to use these samples as a guide to setting their own parameters. Each keyword group and the associated parameters will be discussed on the proceeding pages.

Page -18-


Report Information

CompanyThe company information appears in unedited format on the Statements of Address Accuracy (SOA). If you are a US company mailing into Canada, you can put your Zip code in the Postal code field.

Non Address Data n (where n is either 1 or 2 The Non Address Data lines one (1) and two (2) extract information from the file and print it on the corrected and uncorrected records reports. These items will be copied directly from your input record from the position you specify with the length you specify. The maximum length for these fields is 50. Dr. Q does not convert hex characters or non-printable characters.

Page -19-

REPORT INFORMATION ( -[Company ( -

[Name (‘a’) -][Address (‘a’) -][City (‘a’) -][Province (‘a’) -][Postal Code (‘a’) -]

)] -

[Non Address Data 1 ( -Start (nnn) -Length (nnn) -

)]

[Non Address Data 2 ( -Start (nnn) -Length (nnn) -

)]

[Report break ( -Start (nnn) -Length (nnn) -

)]

[Print 1 of nnnnn -]

[Maximum Pages (nnnnn) -]

[Log Notify Interval (nnnnn) |(nnnnK))


Log Notify IntervalFor long runs you can have Dr. Q place messages in the JESLOG at intervals of input records. If you have a run of 100,000 pieces, you can use the log notify interval to tell you how many records it’s gone through. You can use the K suffix for the number which will multiply the number by 1000. If you asked for a Log Notify Interval of 20K, five messages will be written to the JESLOG, once at 20,000 records, once at 40,000 records and so on.

Maximum PagesCode the maximum pages if you want to restrict Dr. Q from producing more than a given number of pages on the Corrected Records Report and Uncorrected Records Report. Both reports will stop printing at the specified number of pages.

Print 1 of nnnnnThis parameter is used for “sampling” the corrected and uncorrected reports. On each report only records nnnnn, nnnnn*2, nnnnn*3 etc. will be printed. For example “Print 1 of 10” means that only the 10th, 20th, 30th, 40th etc. corrected record will appear on the Corrected Records Report and the 10th, 20th, 30th, 40th etc. uncorrected record will be printed on the Uncorrected Records Report.

Report breakThis parameter is used for printing out separate Correction Summary Reports and Statements of Accuracy based on a change in a field on the input data. Suppose for example that you had a department number in your file at position 2 for a length of 3. Providing the file is sorted by the department, if you request a report break as follows:

Report break (Start (2) Length (3))

will result in the following:

1. A separate Correction Summary Report will be printed for each department. Each Report will contain the department field in it’s title (for example: REPORT BREAK: 001)

2. A separate Statement of Accuracy will be printed for each department. Each Report will contain the department field in it’s title (for example: REPORT BREAK: 001)

3. A Page break will occur on Corrected Records & Uncorrected Records reports each time there is a change in the Report break field. Each page will contain a header describing current report break (for example: REPORT BREAK: 005).

4. A Statement of Accuracy and a Correction Summary report will be printed on the entire file.

Page -20-


Input File Description

The input file description tells Dr. Q what the input file looks like. It also gives Dr. Q information about the file such as the record length, a brief description of the contents of the file and where or how Dr. Q is to pickup information about the file.

DDNameYou can use the DDNAME to tell Dr. Q what DDNAME to use for the input file. If you use the DDNAME parameter without using the DSNAME parameter, Dr. Q will look to the JCL for this DDNAME (i.e. if your DDNAME parameter is ‘FILE01’, Dr. Q will expect you to have a //FILE01 DD DISP=???,DSN=?????, in your JCL)

DSNameIf you code a DSName, Dr. Q will dynamically allocate this file as share and use it as the input file. If you use the DSName parameter, you do not have to include this file in the JCL. The dataset name that you code in this description, must be:

1. Cataloged2. PS, FB3. Must not be a PDS dataset or a member of a PDS4. Must not be a GDG entry

Page -21-

Input File Description ( -[DDName (‘aaaaaaa’) -][DSName (‘aaaaaaaaaa’) -][LRECL (nnnn) -][File Description (‘aaaaaaaaaa’) -][French Indicator ( -

[Start (nnnn) - Length (nnnn) -[Value (‘aaaaaaa’) | -Not Value (aaaaaa)] - ] |[All Accents] -

[Address Line n -Start (nnnn) -Length (nnn) -Contains ( -

[Address -][City -][Province -][Postal Code -]

) -]

)


LRECLThe LRECL of the input file is coded in this parameter. The LRECL of your input file must be less than 32K.

The LRECL parameter is used as an offset to tell Dr. Q what part of the address record it can use. It is important to ensure that the LRECL specified is at least the same size as the input files record length.

File DescriptionThe file description is a brief description about the contents of the input file. This description will be placed on most of the reports that Dr. Q produces.

French Indicator This area describes when to allow Dr. Q to utilize the accented database as provided by Canada Post. There are two uses for this parameter. Specifying a Start, Length & Value (or “Not Value”) allows you to control when Dr. Q is to use the accented database, on a record by record bases. Alternatively, if you specify “All Accents”, Dr. Q will always use the accented database when Canada Post has supplied the accents.

Specifying a Value parameter indicates that Dr. Q is to check in the start position for the length specified and search for the text. If the text is found at that location, accents will be allowed. Conversely, using the “Not Value” parameter, Dr. Q will check in the start position indicated, for the length specified, and unless the value is found there it will use the accented database when a Canada Post accent is valid.

If there is no French Indicator parameter entered, Dr. Q will not accent the label buffer.

Address Line nThe address lines tell Dr. Q where to find the addressing information within the input address lines, and what information is in those lines. If you are keeping suites or box numbers in a separate field, describe these fields separately and use the Address contains clause, which assumes that in can be any information other than city, province or postal code.

If box numbers or route numbers are in a separate field, they MUST have a route or box keyword attached within the same field. (ie: PO BOX, RR, OR SS)

Output Areas

Page -22-


Page -23-

Output Areas ( -[Input record -

[(Start (nnnn) -)]][Fixed CPC Buffer -

[(Start (nnnn) -)]][Location Matrix -

[(Start (nnnn) -)]][Identification Matrix -

[(Start (nnnn) -)]][Merge Purge Code -

[(Start (nnnn) -)]][Address Category -

[(Start (nnnn) -)]][Messages -

[(Start (nnnn) -)]] [POCI -

[(Start (nnnn) -)]][Label -

[Start (nnnn) -][Suite Default Keyword

(‘aaaaaaaaaaaa’) -][Lower Case Translation (y | n) -][Accent Translations (N1, n1, -

N2, n2 -

N3, n3 -

N4, n4 -

N5, n5 -

N6, n6 -

N7, n7 -

N8, n8 -

N9, n9 -

N10, n10 -

N11, n11 -

N12, n12 -

N13, n13 -][Address Line n(n is number from 1 to 8) -

[Start (nnnn) -]Length (nnn) -Contains ( -

[Address -][City -][Province -][Postal Code -][Extraneous ( -

[11 -][21 -][32 -][42 -][52 -][Truncate | NoTruncate]) -

]]

]


Input recordThe input record is coded in most output areas to copy the original record into the corrected and valid files. Like all output areas, you can explicitly specify a starting column for the input record by coding the start parameter, or you may leave it to take on the default position. If you do not request an input record as one of your output areas, Dr. Q will not place it in any of the files and you will not be able to retain non-address data on your output records.

The input record parameter is included as an output area parameter mostly to allow you to position it within your output records.

Fixed CPC BufferThe Fixed CPC buffer is an area, which contains the actual data as provided on the CPC address on magnetic tape, data file. The ranges for suites, street number and Post Office Boxes have been converted to the actual number, which was provided on the input record.

Users can use this information to extract information from individual data components. This area might be requested if a user wishes to sequence or extract data from the file by a particular element. Because elements in this area are always CPC optimal (unlike the label buffer which may use a 13 character abbreviation or a CPC approved alternate), it is more convenient to use this area if you wish to extract or sort records based on a particular address component (e.g. community name or street name).

The Fixed CPC Buffer is 152 bytes long and it’s contents are described in Appendix H - “Fixed CPC buffer” Description on page 71.

Location MatrixProgrammer can use the Location Matrix to determine how Dr. Q parsed the input address information. Used in conjunction with the Identification Matrix, the Location Matrix tells a program where each word was found and how it was used to validate or correct the information.

The location matrix format is:

30 entries, one for each word2 byte binary line number 2 byte binary line offset1 byte binary line length

Each entry is 5 bytes in length for a total length of 150

Page -24-


The most common use for the Location Matrix and the Identification Matrix, is to help in the processing of standardizing or “fixing” free-floating address labels. In cases where address labels can contain recipient names, company names and departments, programmers can use these two areas to identify where the address information comes from and exclude these lines from address processing.

Identification MatrixUsed in conjunction with the Location Matrix programmers can use this area to identify the types of words found in the input address lines. For more details see the Location Matrix on page 24.

Each byte in the Identification Matrix identifies the word type. The word types which are returned are the same types as the synonym classes and are found in Appendix A - Synonym and Word Classes, on page 61.

Merge Purge CodeThe merge purge code is a 15 byte hexadecimal field designed by Prism to uniquely identify all addresses in Canada. This code can have many uses especially in the indexing and cross-reference of two or more files, or for eliminating duplicates in one or many files.

Because this code is unique for every address, programmers can spend time determining what to do when one or more records have the same address, rather than matching by names and determining if the addresses are the same.

A hexadecimal code has been added to determine if the address is a multi family delivery point. Multi-family delivery points include addresses with RR, MR, SS and GD type services. If this bit is not set, the address is a multi-family delivery point and you may want to put more emphasis on the name matching criteria.

The merge purge code changes with every directory. One byte in the merge purge code has been set aside to determine the directory that the file was run on. Aside from the multi-family bit flag, and the one byte directory code, the remainder of the merge purge code is set aside for address information

The layout of the merge purge code is as follows:

Byte Bits Purpose1 1 Multi family indicator 0 = multi family 1 = single family1 2-8 Address Information

2-14 1-8 Address Information15 1-8 Numeric Directory Month code indicator

Page -25-


Address CategoryThe address category is a two byte code indicating whether the address was considered Rural, Urban, LVR or Foreign and whether the address was corrected, valid or uncorrectable. You can use the address category to determine where to focus your efforts to obtain the highest CPC accuracy percentage.

Unlike all of the other output areas, the address category is always placed on all output files, not just the correct and accepts files. If you request a start position for the address category, the address category will be placed at that position on all of the output files. If you do not specify a start position, it will default to the LRECL parameter of the Input File Description + 1 byte.

MessagesThe Messages is an 800 byte field (10x80 byte) area which contains only the message(s) as listed in the UCR8000/CRR8000 (UNCORRECTED/CORRECTED) reports.

POCIThe P.O.C.I. (Point of Call Identifier) is a requirement of the Postbar Encoding module (PEM) supplied by Canada Post. Dr. Q supports the use of the PEM module by providing you with the actual data required to call the PEM module for each address. The length of the POCI area is 15 bytes and is formatted as follows:

6 Bytes Postal Code4 Bytes AL15 Bytes AL2

For a description of the contents of AL1 and AL2, please refer to the Canada Post’s PEM Users Guide.

LabelThe label is probably the most important address management area to understand. The Label parameters control the output address information and allows you to correct records easily through the parameters.

Accent TranslationsCanada Post supplies an accented directory on the Canada Post tape. As EBCDIC does not have a standard French character set, Dr. Q allows you to translate the character set into your own character set for use by your printers and other equipment. You can combine the Accent translations and the Lower Case Translation to give you upper/lower proper case with accents to make your mail stream all the more personal.

Page -26-


The codes used in here are the hexadecimal code that is used to generate the accented character you require. The numbers here rely on position. The following table shows you the sequence of the character replacements as they must appear in the field:

Position 1 & 2: Â, âPosition 3 & 4: À, àPosition 5 & 6: Ç, çPosition 7 & 8: Ê, êPosition 9 & 10: É, éPosition 11 & 12: È, èPosition 13 & 14: Ë, ëPosition 15 & 16: Î, îPosition 17 & 18: Ï, ïPosition 19 & 20: Û, ûPosition 21 & 22: Ü, üPosition 23 & 24: Ô, ôPosition 25 & 26: Ù, ù

Lower Case TranslationWithin the label buffer, you can set a switch to indicate that you would like Dr. Q to return addresses in Proper upper lower case translation. When Dr. Q is outputting the address, community or province information, it will translate them to upper and lower case characters. The translator does not translate extraneous data, postal codes or information which should logically appear in upper case e.g. PO, RR, NWT, PEI, any province symbols (ON, QC etc.).

The default for Lower Case Translation is OFF or NO, which means it will always return upper case address information.

If the Lower Case Translation keyword is not specified, the default is NO. Some address information may still appear in lower case if the optimize parameter for the area is set to NO and the input record contained lower case characters.

Suite Default KeywordThe Suite Default Keyword is used to determine what to correct a suite keyword to when the incoming suite keyword is invalid. A dash “-” used as a suite keyword indicates that Dr. Q will prefix the street number with the suite number followed by a dash character and place all of the information into the address field. The dash character is the default suite keyword. Dr. Q follows these rules:

1. If no address lines have a contains clause of SUITE KEYWORD, Dr. Q will always make any suite keyword (even valid ones), ‘-’. All suites will prefix the street number with the suite number and the dash character. The suite information then becomes part of the Address contains clause.

- otherwise -

Page -27-


2. If a SUITE KEYWORD contains clause is found, Dr. Q will put out the original suite keyword into the address line when the original suite keyword was valid by CPC standards. When the original suite keyword was invalid by CPC standards and is required, the system will correct it to be the Suite Default Keyword parameter value.

Where Possible, we recommend users to continue using suite keywords. Because CPC accepts PH as a keyword, the system could change 425 HORNER AVE PH 1, to 1-425 HORNER AVE

Address Line n (where n is a number between 1 and 8)

Each address line parameter must include a contains clause and a length parameter. The contains clause tells Dr. Q what information is to be strung together into this particular output area. The positioning of the stringing of the information depends on the contains parameter position. For example, if address line 1 had a contains clause of “SUITE, SUITE KEYWORD, ADDRESS”, Unit 2, 425 Horner Ave would be returned into address line 1 as 2 Unit 425 Horner Ave, probably not the desired result. If the contains clause read “ADDRESS, SUITE KEYWORD, SUITE” address 1 would be returned as 425 Horner Ave Unit 2, a preferred result.

When a start value is issued within an area, the address information will be placed at the column specified as the start parameter number. You can overwrite your existing address lines by explicitly giving a start parameter within the input record.

Others Parameters Effecting the Label LinesThe following parameters may have an effect on how information is returned into the address label:

Parameter Effects See Page

LOWER CASE TRANSLATION This parameter may have an effect on any address line except extraneous data and the postal code itself

26

SUITE DEFAULT KEYWORD This parameter has an effect on street type records with suite information when the suite keyword was invalid by CPC rules.

26

ALLOW ALTERNATES In address lines where a community is specified in the contains clause, this parameter may have an effect on the community name being returned.

31

OPTIMIZE COMMUNITY In address lines where a community is specified in the contains clause, the optimize community

30

Page -28-


Parameter Effects See Page

parameter controls what community name is to be returned in that address line.

OPTIMIZE PROVINCE In address lines where a province is specified in the contains clause, this parameter controls the information returned

29

OPTIMAL QUEBEC CODE If the optimal quebec code is set to ‘PQ’ (QC is default) then the word PQ will appear in address lines with the PROVINCE contains clause.

29

OPTIMIZE OTHER COMPONENTS

In address lines where an address contains clause exist, this parameter controls what information is placed into the address line.

30

OPTIMIZE ROUTE KEYWORDS In address lines where an address contains clause exist, this parameter controls how the route keywords will appear in the address line

30

Figure Chapter 4 -1 Parameters Effecting Label Lines

Run Conditions

Optimize ProvinceSetting the optimize province switch to YES, tells Dr. Q to change all province codes, even valid ones to the CPC optimal province code. In Quebec, the code will be changed to the “Optimal Quebec Code” value. With the optimize province code set to YES, province codes which are permitted by Canada Post such as ONT, or ONTARIO, will be changed to ON. With it turned to NO, the label buffer will contain the original province code only when the original province code was valid.

Page -29-

Run Conditions ( -[Optimize Province (Y | N | yes | no) ]-[Optimize Community (Y | N | yes | no) ]-[Optimize Route Keywords (Y | N | yes | no) ]-[Optimize Other Components (Y | N | yes | no | LI) ]-[Optimal Quebec Code (PQ | QC) -[Missing Street Numbers (Y | N | yes | no) ]-[Rural and LVR Correction (Y | N | yes | no) ]-[Reformat All Records (Y | N | yes | no) ]-[Aggressive Data Elimination (Y | N | yes | no) ]-[Insert GD (Y | N | yes | no) ]-[Directory Prefix (‘aaaaaaaaaa’) ]-[Incore RNG4 (Y | N | yes | no) ]-[Allow Alternates (Y | N | yes | no) ]-[Run Type (REGULAR |

VERIFY)


None of the Optimize parameters effect the validity of the address and all of them operate only on the LABEL Output areas.

Optimize CommunitySetting the optimize community switch to YES tells Dr. Q to always optimize the community name in the label to the one provided by Canada Post for that particular code.

Optimize Route KeywordsSetting the optimize route keywords switch to YES tells Dr. Q to always optimize route keywords to the optimal provided by Canada Post. Even though Canada Post may permit R.R., if this switch is YES, the route keyword will be changed to RR.

Optimize Other ComponentsOther components include Street Type and Street Direction. Spelling a street type out in full is acceptable by Canada Post standards. Setting this flag to YES, tells Dr. Q to change the street type and direction to the CPC approved optimal arrangement. LI is similar to YES but the formatted street type and direction will be replaced in the original input arrangement..

Optimal Quebec CodeThe optimal Quebec code tells Dr. Q what code to used when the province code of an address in Quebec is being optimized, which code to used.

Values permitted are QC and PQ, and the default is QC.

Rural and LVR CorrectionDetermines if Dr. Q is to attempt to correct records, which meet the guidelines of automatically being considered Valid because of the postal code. If this parameter is set to YES, (the default), Dr. Q will attempt to correct the information (including the postal code), even though the record will always be counted as Valid for the statement of accuracy. As an unlikely example, this address is considered valid on input “1-435 HORNER AVE, ETOBICOKE ON T0M 1WO”. If this parameter is set to yes, the postal code will be changed to M8W 4W3.

If the parameter is set to “no”, records which are automatically accepted without validation of the address information is placed on the uncorrected file. It is placed on the uncorrected file because there is a significant difference in the information, which can be returned when the address information has not been matched against the Canada Post Directory.

Page -30-


Reformat All RecordsThis parameter specifies whether or not to alter Rural and Non-Correctable records by putting them in the same format as the Corrected and Valid Records. If the Reformat All Records parameter is set to yes, Dr. Q will attempt to standardize all Rural and uncorrectable records based on the input record information. Some standardization occurs but the information is not matched against Canada Post for accuracy.

Aggressive Data EliminationThis parameter specifies whether or not to take a more aggressive approach to eliminate extraneous information found in the input address line.

CAUTION : When this indicator is turn ON it may eliminate data that is required by the delivery Mail Person but is not in the Canada Post directory data i.e. site, box information.

Insert GDThis parameter specifies whether or not in a small rural community with only 1 postal code, to insert the key word GD if not present in input address data.

Directory PrefixDr. Q can dynamically allocate the directory files provided that they are cataloged and the suffixes (last qualifier) have not been changed. For the directory prefix, use the full qualifier of the VBDIR file up until the last node (e.g.: your VBDIR dataset is cataloged as MF001.PRISM.DRQ.VBDIR, use MF001.PRISM.DRQ as your directory prefix.

If you chose not to use this parameter, you must allocate all four directory files in your JCL.

Incore RNG4This parameter can be used to reduce the amount of DASD access even further. The disadvantage to loading the Incore RNG4 is only found with smaller files where is spends more time in the initialization phases than it does performing the Dr. Q address maintenance.

The default value is NO.

Allow AlternatesThis parameter tells Dr. Q whether, when it’s constructing an output label and it is too large to fit, it is permitted to use the Canada Post approved abbreviations for the community. If this flag is set to ON or YES, it will find the largest abbreviation that fits. The default value is “Yes” or “On”.

Page -31-


Run TypeThe run type effects how Dr. Q will process the file. The two allowed values are REGULAR and VERIFY.

Running Dr. Q in Verify mode permits it only to determine which addresses are not currently at Canada Posts Accuracy Requirements. It will not do any corrections.

Determining Output Area Record LayoutThe output areas describe the format to return the corrected and valid address information. The Output areas parameter set is what makes Dr. Q so flexible and easily integrated into your environment. All “Output Areas” parameters effect the layout of corrected (CORRECT) and valid (ACCEPT) files. The Address Category also affects the layout of the OSZFILE and the UNCOR files.

Unlike the other parameters, the order in which you present the information can have an effect on the operation of Dr. Q. The default starting positions for each output area is determined by the location within the output area parameters.

For example:

Output Areas (Input record, Fixed CPC Buffer)

will result in the following record layout for the corrected and accepted files:

Output AreaPosition in Output File Length

Input record 1 LRECL (Input Description Parameter)Fixed CPC Buffer LRECL + 1 152

whereas:

Output Areas(Fixed CPC Buffer, Input record)

will result in the following record layout for the corrected and accepted files:

Output AreaPosition in Output File Length

Fixed CPC Buffer 1 152Input record 153 LRECL of input parameter

The length of the output areas is:

Output Area LengthInput record LRECL (input

Page -32-


parameter)Label Total length of all of the

label address lines (excluding those with specific start locations)

Address Category 2Fixed CPC Buffer 152Location Matrix 150Identification Matrix 30Merge Purge Code 15

15

In order to determine the default starting position for any of the areas, begin at one and accumulate the length of each area in the order in which it described in the output areas. You must ignore any area, which explicitly uses a start position.

For example:

If an original file had a input LRECL of 155 and the output areas were described as follows:

OUTPUT AREAS ( -INPUT RECORD -FIXED CPC BUFFER -POCI (START (1) -MERGE PURGE CODE -LOCATION MATRIX ( -

START (408) -LABEL ( -

ADDRESS LINE 1 ( -CONTAINS (CITY,PROVINCE,POSTAL CODE) -LENGTH (30) -

) -ADDRESS LINE 2 ( -

CONTAINS (ADDRESS) -LENGTH (25) -

) -IDENTIFICATION MATRIX -)

The output layout would be:

Output Area Start Column LengthInput record 1 155Fixed CPC Buffer 156 152Merge Purge Code 308 15Label 323 55Identification Matrix 378 30Location Matrix ** 408 150

Page -33-


* The POCI will overwrite the first fifteen bytes of the Input record as it specifies a start position of 1 and has a length of 15.

** Because the location matrix explicitly asked to start in column 408 and has a length of 150, the total length of the Corrected and Accepted files would be 558.

The order in which the output area is filled is important if you intend to overlay some of the areas with other areas using a start positions. An example of this might be “updating in place” where the input address has names, account numbers as well as address information. Because the order in which the output area is constructed, with the label information being last, you can “overlay “ components of the input record which you want replaced with corrected information. Assume an input record looked as follows:

Account Number

(8)Postal Code

(6)Name(40)

Address Line 1(35)

City(25)

Province(4)

Running Dr. Q with these parameters would return the identical file layout with all address information updated, yet leave the account number and name unchanged, because the label areas are the last areas to be placed on the file.

OUTPUT AREAS ( -INPUT RECORD -LABEL ( -

ADDRESS LINE 1 ( -CONTAINS (POSTAL CODE) -START (9) -LENGTH (6) -

) -ADDRESS LINE 2 ( -

CONTAINS (ADDRESS) -START (55) -LENGTH (35) -

) -)

Order of Output Area Construction

1. Input record (if present) 2. Fixed CPC Buffer (if present)3. Location Matrix (if present)4. Identification Matrix (if present)5. Merge Purge Code (if present)6. POCI (if present)7. Label Area (if present) 8. Address Category (if present)

Page -34-


Calculating the LRECL of other Files

UNCOR (Uncorrected Records File)The uncorrected records file can be coded as:

(no information required) code:LRECL of input file

error code:LRECL of input file + 2

(address category required but start value not specified in parameter) code:LRECL of input file + 4

(address category required and start value is specified in parameter) code:The greater of

LRECL of input file + 3 andThe Start sub-parameter of the address category if it is specified

OSZFILE (Oversized Records File)The oversized file can be coded as:

(no information required) code:LRECL of input file

(address category required but start value not specified in parameter) code:LRECL of input file + 3

(address category required and start value is specified in parameter) code:The greater of

LRECL of input file + 2 andThe Start sub-parameter of the address category if it is specified

Page -35-

Parameter Table

Variable Description and Uses TypeMaximum

Size Example

REPORT INFORMATION Report Information to be printed Category - Not required n/a REPORT INFORMATION ( -Company Record your company information

on reportsCategory - Required n/a Company ( -

Name Your company name Text - Not required 45 Name(‘Prism Data Ltd.’) -Address 1 Your company address Text - Not required 45 Address 1(‘2-425 Horner Ave’) -City Your company city Text - Not required 30 City(Etobicoke) -Province Your company province Text - Not required 2 Province(ON) -Postal Code Your company Postal Code/Zip Code Text - Required 6 Postal Code(M8W4W3) ) -

Non Address Data 1 Data area in record to be put on corrected and uncorrected reports

Category - Not required n/a Non Address Data 1 ( -

Start Start column of data area numeric - maximum value is 4096

n/a Start (100) -

Length Length of data area numeric - maximum value is 4096 - start value

n/a Length(20) -

Non Address Data 2 See above Non Address Data 2 ( -Start Start(10) -Length Length(8) -

Report break Data area in record which contains a “breaking field”. Each time this area changes in the Dr. Q process, Separate reports are printed

Category - Not required Report break ( -

Start Start column of data area numeric - maximum value is 4096

4 Start (10) -

Length Length of data area numeric - maximum value is 4096 - start value

4 Length(5)) -

Maximum Pages Maximum number of pages for the Corrected Records & Uncorrected Records Reports

numeric - maximum value is 99999

5 Maximum Pages (100) -

Print 1 of nnnnn To “Sample” the records on the report rather than printing every record.

Nnnnn parameter is numeric - maximum value is 99999

5 Print 1 of 100 -

Log Notify Interval Number of records before a message is displayed on the queue.

numeric or numeric with a K suffix. If K suffix is used number is multiplied by 1000

5 Log Notify Interval ( 10K ) )

Parameter Table


Size Example

INPUT FILE DESCRIPTION Description of input fields Category - required n/a INPUT FILE DESCRIPTION ( -DSName To identify the DSN of the input file Text 44 DSName (‘DRQ.DATA.SAMPLE’) -French Indicator To identify whether to use the French

accented characters setCategory - not required (default never use accents)

n/a French Indicator

Start Starting position of language text from input file

Numeric LRECL Start (22) -

Length Length of language code field Numeric Length (3) -Value Value found which tells to use accent

translationsCharacter - only one of “All Accents”, “Not Value” or “Value” permitted.

30 Value (‘FRE’) -

Not Value Value which, when found in this field, tells Dr. Q not to use French Character Set

Character - only one of “All Accents”, “Not Value” or “Value” permitted.

30 Not Value (‘ENG’) -

All Accents tells Dr. Q to always use the CPC approved French accent when available

no parameters - only one of “All Accents”, “Not Value” or “Value” permitted.

All Accents -

DDName To identify the DDName of the input file

Text 8 DDName (MYDSN) -

LRECL To identify the LRECL of the input file

numeric - required, maximum value 3900

4 LRECL (350) -

File Description Describes the contents of this input file

text - not required 45 File Description (‘My Sample Dr. Q file’) -

Address Line n Each address line is described where n is any value from 1 to 8

Category - (at least one) required

n/a Address Line 1 ( -

Start Identifies the starting column on the input file

numeric - required for each address line. Maximum value = LRECL - START

4 Start (80) -

Length Identifies the length of each address line

numeric - required for each address line

4 Length(50) )-

Contains Tells Dr. Q what information is in this address line

Category - Required for each address line

n/a Contains ( -

Address Tells Dr. Q address information is in address line (e.g.: 2-425 HORNER)

n/a n/a Address -

City Tells Dr. Q city information is in this address line

n/a n/a City -

Province Tells Dr. Q province is in this address line

n/a n/a Province -

Postal Code Tells Dr. Q the Postal code in this address Line

n/a n/a Postal Code)

Parameter Table


Size Example

OUTPUT AREAS Describe the Valid and Corrected Records Formats

Category - required n/a OUTPUT AREAS ( -

Input record Indicates the entire record from the input is to be copied to this location

Category - not required n/a Input record -

Start optional starting column to manually position the original record into the output records

numeric - not required 4 ( Start (1) )-

Fixed CPC Buffer The 152 byte Canada Post Record is to be placed on the file. The description of this area is found on page 24.

Category - not required n/a Fixed CPC Buffer -

Start optional starting column to manually position the original record into the output records

numeric - not required 4 ( Start (184) )-

Location Matrix Indicates the 150 byte location matrix generated by Dr. Q is to be copied to this location. page 24 for details about the location matrix

Category - not required n/a Location Matrix -

Start optional starting column to manually position the Location matrix into the output records

numeric - not required 4 (Start (500) ) -

Identification Matrix Indicates the 30 character location matrix is to be placed into the output records

Category - not required n/a Identification Matrix -

Start optional starting column to manually position the identification buffer into the output records

numeric - not required 4 (Start (300) )-

POCI Indicates the 15 character Point of Call Identifier as required by the CPC PEM module is to be copied to the output files

Category - not required n/a POCI -

Start optional starting column to manually position the POCI into the output records

numeric - not required 4 (Start (231)) -

Merge Purge Code Indicates the 15 character merge purge code is to be copied to the output files

Category - not required n/a Merge Purge Code -

Start optional starting column to manually position the merge purge code into the output records


Address Category Indicates a one byte character indicating whether the output address is Rural (R), Urban, (U), LVR (L) or Foreign (F), is to be copied to the output files

Category - not required n/a Address Category -

Parameter Table


Size Example

Start optional starting column to manually position the address category into the output records


Label To describe output address lines after correction or standardization

Category - required n/a Label (-

Start Manually tells Dr. Q where to begin placing the address lines

numeric - not required 4 Start (10) -

Suite Default Keyword Identifies the suite keyword to use if a valid suite keyword is not found

Can be any of the following values:‘-’, APT, UNIT, SUITE, APPARTMENTdefault is ‘-’

12 Suite Default Keyword (APT) -

Accent Translations To tell Dr. Q what translation codes to use for French accented characters

Values are 2 Digit Hexi-decimal Numbers which rely on placement. Each number represents the hex character replacemtn of the following :Â, â, À, à, Ç, ç, Ê, ê, É, é, È, è, Ë, ë, Î, î, Ï, ï, Û, û, Ü, ü, Ô, ô, Ù, ù

3 Accent Translations (4c, 5f, 2c, 6f, 8c, 12, 0d, 0c, fe, -f1, 2f, 4f, 6f, 4f, 4d, 4e, 4f, 4c, 5f, -8c, 8d, 9f, 6c, 7f, 7c, 6B) -

Address Line n Tell Dr. Q that you would like to place an output address line on the output file. n is a value from 1 to 8

Category - Required when label is specified

n/a Address Line 1 ( -

Start Manually tells Dr. Q where this specific address line starts

numeric - not required 4 Start (45) -

Length Tells Dr. Q the length of this address line

numeric - required for each address line (max. 255)

3 Length(58) -

Contains Tells Dr. Q what information to include in this address line

Category - Required for each address line

n/a Contains ( -

Address Tells Dr. Q to put address information into this address line (e.g.: 2-425 HORNER)

n/a n/a Address -

City Tells Dr. Q to put city information in this address line

n/a n/a City -

Province Tells Dr. Q to put the province in this address line

n/a n/a Province -

Postal Code Tells Dr. Q to put the Postal code in this address Line

n/a n/a Postal Code -

Extraneous Tells Dr. Q to put the Extraneous data in this address line

possible values for extraneous are combinations of:truncate, notruncate, 11, 21, 32, 42, and 52.

n/a Extraneous(42,52,Truncate) -

RUN CONDITIONS Describe run information to Dr. Q Category - required n/a RUN CONDITIONS ( -

Parameter Table


Size Example

Optimize Province Tells Dr. Q whether it should always return the optimal province code in the label buffer or if a province is valid, to return the original

Text - Required, valid responses are Y, N, Yes, No

3 Optimize Province (Yes) -

Optimize Community Tells Dr. Q whether it should always return the optimal community or if it can return the input community if it was valid

Text - Required, valid responses are Y, N, Yes, No

3 Optimize Community (NO) -

Optimize Route Keywords Tells Dr. Q whether or not to optimize route keywords or whether to take the original if it was valid. For example R.R. 6 might be valid, but it is not in optimal format

Text - Required, valid entries are Y, N, Yes, No

3 Optimize Route Keywords (N) -

Optimize Other Components Other components include street direction, street name and station types and you can tell Dr. Q to always optimize or to use the input if it was valid

Text - Required, valid entries are Y, N, Yes or No

3 Optimize Other Components (Y) -

Optimal Quebec Code Tells Dr. Q what code to use as the optimal code for Quebec. Both QC and PQ are considered optimal by CPC standards

Text - Not required, default is QC. Possible entries are QC and PQ

2 Optimal Quebec Code (PQ) -

Run Type Tells Dr. Q what type of run this will be, REGULAR or VERIFY

Text - Required, valid entries are VERIFY, or REGULAR

12 Run Type (REGULAR) -

Rural and LVR Correction Indicates whether Dr. Q should attempt to standardize and correct Rural and LVR matched records to meet the Canada Post Database

Text - Not Required, Default is Y, valid entries are Y, N, Yes, No

3 Rural and LVR Correction (Y) -

Reformat All Records Determines if Dr. Q is to attempt to reformat Rural and Uncorrectable records to the output specifications

Text - Not Required, Default is N, valid entries are Y, N, Yes, No

3 Reformat All Records (Y) -

Missing Street Numbers Controls whether or not Dr. Q accepts records as street serviced by route records if the address does not have a street number


3 Missing Street Numbers (N) -

Aggressive Data Elimination Tells Dr. Q to remove information between two valid components (e.g. 435 HORNER HORNER AVE, the second HORNER will be eliminated)


3 Aggressive Data Elimination (Y) -

Directory Prefix Permits Dr. Q to dynamically allocate the four directory files that it needs using this prefix. The prefix must be the all nodes for all of the files up until the last node

Text - Not required 44 Directory Prefix (OMCC.DRQ.DIR) -

Parameter Table


Size Example

Incore RNG4 Allows Dr. Q to read the Range 3 file incore

Text - Not required, valid entries are Y, N, Yes, No

3 Incore RNG4 (Yes) -

Return Alternates Allows Dr. Q to use the valid alternate community file if a label address line containing the city goes over the output length

Text - Not required, valid entries are Y, N Yes and No, default is Yes

3 Return Alternates (NO)-

Chapter 5 Synonyms

Synonyms OverviewUser synonyms are used to tell Dr. Q how to correct addressing areas which may be common to your users. When a user adds user synonyms to Dr. Q, the program can quickly assess whether an address has enough components to identify possible corrections. Dr. Q will use the knowledge of a user synonym to identify elements while creating new postal codes and while deciding on the best possible correction.

Dr. Q has many user synonyms, which are shipped with the system. These synonyms have been accumulated through PRISM’s service bureau over a number of years.

Adding New SynonymsInternally, Dr. Q is supplied with a number of synonyms all of which are contained in the VBDIR file. The USRSYNS program can be used to create new synonyms to help Dr. Q better understand your addressing style. You can use Dr. Q to add new synonyms to create a complete new VBDIR file.

The program USRSYNS, set up in the DIR.JCL library, contains a sample JCL stream to run the USRSYNS program. Users set up a user synonym file and allow the program USRSYNS to update or create a new VBDIR to be used by your Dr. Q JCL. The input file must contain the following information:

Start Position Length Contents Example

1 30 User Synonym STEELTOWN31 1 Synonym Class F32 1 Synonym Part (Filler) (NOT USED)33 30 Directory Word HAMILTON

Figure Chapter 5 -1 Format of the Input Synonym File

The input file to the USRSYNS program must be of fixed length and can be a length of 80 through 256. All characters, which lay past the 62nd character, are ignored. In practice, users may even issue user synonyms as a SYSIN statement (i.e. USRSYNS DD *).

See Appendix A - Synonym and Word Classes for a list of Synonym Classes on page 61. Only classes, which are logically associated with synonyms, are valid. As an example, the “Street Number” Class “X” cannot be used for synonym lookups and will be rejected by the program.

Chapter 6 Technical Overview

Provided Source ModuleDr. Q is provided with a sample program, DRQV21, which is normally called through JCL. We provide the source for DRQV21, which can be used as a stand alone product or be used as an example of how to call Dr. Q from your own application. The flow chart "Figure Chapter 6 -1 DRQ Module Program Flow" on page 44 shows how the module DRQV21 operates. The complete COBOL source listing for Dr. Q can be found on page 47.

Quite simply, in order to make successive calls to Dr. Q for address correction:

1. Create the passing structure found in copybook FT06 or FT06COB. You may hard code this structure or use the parameter file edit program supplied with Dr. Q.

2. Pass the 4096 byte address record, the function type "R" and the FT06 copybook area created in step 1, to Dr. Q.

3. At the end of the file, call Dr. Q with a function code "C", which terminates the system and creates the summary reports.

Chapter Chapter 6 - Technical Overview

Done

Pass Record, FT06onto Dr. Q for

validation/correction

Create Dr. Qsummation reports

Read and EditParameter File:

Update FT06copybook

Did Paremeter Editreturn OK?

Read First/Next recordinto 4096 area

End of File?

Figure Chapter 6 -1 DRQ Module Program Flow

The following modules are called in DRQv21:

Module Name Description Areas PassedDRQI0105 Parameter File Edit/Setup FT06

areaFT06

DRQI0135 Read QSAM file into 4096 area (LRECL unknown)

FT064096 Byte User AreaEnd of File Switch

DRQM0105 Dr. Q main module. Sets up 4096 area to specifications contained in FT06. Sets Return arguments in FT06 copybook member.

FT064096 Byte User Area Function Code ('R' to process records, 'C' to complete processing).


The FT06 area contains all of the fields necessary for Dr. Q to interpret your addressing requirements. Inside FT06 are areas, which a calling program can examine to determine information about the address passed to Dr. Q. The FT06COB copybook contains a detailed listing of the areas, which are set up by DRQI0105 and the codes, which are returned from a call to DRQM0105. The FT06COB copybook can be found on page 47.


IDENTIFICATION DIVISION. PROGRAM-ID. DRQV21. AUTHOR. D. QUINN. DATE-WRITTEN. DEC 01,1995. REMARKS.

* ============================================================= * * * * DRQV21 THIS IS A SAMPLE ENTRY POINT TO A SIMPLE DR Q * * CALLING SEQUENCE. THE PROGRAM FIRST CALLS * * DRQI0105 TO INITIALIZE AN AREA WITH THE PARAMETER * * FILES. IT THEN CONTINUALLY CALLS DRQM0105 UNTIL * * THE END OF THE FILE IS REACHED. DRQM0105 IS * * CALLED ONCE MORE TO CLOSE FILES AND TERMINATE * * PROCESSING. * * * * ============================================================= *

ENVIRONMENT DIVISION. INPUT-OUTPUT SECTION. FILE-CONTROL. DATA DIVISION.

WORKING-STORAGE SECTION.

* RECORD AREA (MUST ALWAYS BE AT LEAST 4096 IN LENGTH)

01 FILEIN-REC. 05 FILLER PIC X(4096).

* DR. Q COBOL INTERFACE AREA

COPY FT06COB SUPPRESS.

01 MISC-WORK-AREA.

* CALLABLE PROGRAMS FOR DYNAMIC LOAD AND CALL

05 DRQ-MODULE PIC X(8) VALUE 'DRQM0105'. 05 DRQ-PARAMETER-EDIT PIC X(8) VALUE 'DRQI0105'. 05 GET-RECORD PIC X(8) VALUE 'DRQI0135'.

* WORK AREAS FOR CALLING ROUTINES AND CHECKING RETURN CODES

05 WK-FUNCTION PIC X(1). 05 END-OF-FILE-SW PIC 9(1) VALUE 0. 88 END-OF-FILE VALUE 1.

PROCEDURE DIVISION.

100-MAIN-ROUTINE.

* INITIALIZE CALL AREA THROUGH USER PARAMETER FILE(S)

MOVE SPACES TO DRQ-DESCRIPTION-TABLE. CALL DRQ-PARAMETER-EDIT USING DRQ-DESCRIPTION-TABLE.

* CHECK RETURN FROM PARAMETER READ, IF NOT LOW VALUES STOP

IF DRQCC-RETURN-CODE NOT = LOW-VALUES MOVE 8 TO RETURN-CODE STOP RUN.

* READ AND PROCESS THE INPUT FILES UNTIL AT END OF FILE

PERFORM 200-PROCESS THRU 200-EXIT UNTIL END-OF-FILE.

GOBACK.

100-EXIT.


STOP RUN.

200-PROCESS.

* OBTAIN THE NEXT RECORD FROM THE INPUT FILE

CALL GET-RECORD USING FILEIN-REC DRQ-DESCRIPTION-TABLE END-OF-FILE-SW.

* IF WE AREN'T PAST THE END, PASS RECORD ON TO DR Q * OTHERWISE CLOSE DR. Q AND LEAVE.

IF NOT END-OF-FILE MOVE 'R' TO WK-FUNCTION CALL DRQ-MODULE USING DRQ-DESCRIPTION-TABLE FILEIN-REC WK-FUNCTION ELSE MOVE 'C' TO WK-FUNCTION CALL DRQ-MODULE USING DRQ-DESCRIPTION-TABLE FILEIN-REC WK-FUNCTION.

200-EXIT. EXIT.

Figure Chapter 6 -2 DRQV21 Source

When Dr. Q returns to the calling program, the FILEIN-REC area will be arranged as you have requested in the parameters or in the FT06 area. It is in this way, that a user can access the information returned and reformat the output into a manner that is required by the calling routine.

To determine your FILEIN-REC length, code a value that gives Dr. Q enough room to return your output request plus a minimum of 332 bytes for a maximum of 32k bytes. Minimum length is 4096 bytes.

While most Dr. Q customers do not have the need to make modifications to the source programs, some have taken advantage of the flexible calling structure by calling Dr. Q directly from their own Address/Record management systems.

COBOL Description Initialize To For further info page

05 DRQ-INPUT-FILE-DESC. 52 10 DRQIF-FILE-LENGTH PIC 9(4) COMP SYNC. Total length of the address lines

within the input record53

10 DRQIF-FILE-DDNAME PIC X(8). Spaces 10 DRQIF-FILE-DSNAME PIC X(44). A DSName which is printed on

reports 10 DRQIF-FILE-DESCRIPTION PIC X(40). A Description of the file which

is included on all reports 10 DRQIF-ADDRESS-LINES OCCURS 8 TIMES 53 INDEXED BY DRQADR. 15 DRQIF-ADDRESS-START PIC 9(4) COMP SYNC. Position of address line within

User Record or 053

15 DRQIF-ADDRESS-LENGTH PIC 9(4) COMP. Length of address line within User Record or 0

15 DRQIF-ADDRESS-CONTENTS PIC X(40). Contents of address line or spaces

54

10 DRQIF-LANGUAGE-START PIC 9(4) COMP SYNC. Position of language field or 0 54



10 DRQIF-LANGUAGE-LENGTH PIC 9(4) COMP SYNC. Length of language field or 0 10 DRQIF-FRENCH-CODE-VALUE PIC X(30). Value of Language indicator to

find at (position, length) within User Record

54

10 DRQIF-INTERNAL-USE PIC X(1). Spaces 10 DRQIF-LANGUAGE-FLAG PIC X(1). N - if value in french-code-value

is found at language-start, language-length then do not accent addressV - if value in french-code-value is found at language-start, language-length then accent addressA - Always accent where possibleSpace - Never Accent

55

10 FILLER PIC X(98).05 DRQ-REPORT-INFORMATION. 10 DRQRD-COMPANY-NAME PIC X(40). Your Company Name 10 DRQRD-ADDRESS PIC X(40). Your Company Address 10 DRQRD-CITY PIC X(30). Your Company City 10 DRQRD-PROVINCE PIC X(2). Your Company Province 10 DRQRD-PC PIC X(6). Your Company Postal Code 10 DRQRD-NON-ADDR-DATA OCCURS 2 TIMES INDEXED BY DRQNON. 15 DRQRD-ADDR-START PIC 9(4) COMP SYNC. Position of non-address data

within address line or 0 15 DRQRD-ADDR-LENGTH PIC 9(4) COMP SYNC. Length of non-address data

within address line or 0 10 DRQRD-BREAK-START PIC 9(4) COMP SYNC. Location of a Section Break area 10 DRQRD-BREAK-LEN PIC 9(4) COMP SYNC. Length of a Section Break area 10 DRQRD-OPR-INTERVAL PIC 9(8) COMP SYNC. Number or records to process

before displaying on the console 10 DRQRD-REPORT-DIVIDEND PIC 9(8) COMP SYNC. Nth record to print on the

Corrected records Report and the Uncorrected Records Report

10 DRQRD-MAX-PAGES PIC 9(8) COMP SYNC. Maximum number of Corrected and Uncorrected Record Report Pages to Print

10 FILLER PIC X(92).05 DRQ-OUTPUT-DESCRIPTION. 55 10 DRQOD-MP-CODE-START PIC 9(4) COMP SYNC. Position within the User Record

to return the Merge Purge code or 0

55

10 DRQOD-CPC-BUFFER-START PIC 9(4) COMP SYNC. Position within the User Record to return the CPC buffer or 0

55

10 DRQOD-ID-MATRIX-START PIC 9(4) COMP SYNC. Position within the User Record to return the ID Matrix or 0

55

10 DRQOD-LOC-MATRIX-START PIC 9(4) COMP SYNC. Position within the User Record to return the Location Matrix or 0

56

10 DRQOD-INPUT-REC-START PIC 9(4) COMP SYNC. Position within the User Record to return the Input Address ID Matrix or 0.

56

10 DRQOD-LABEL-LINE-START PIC 9(4) COMP SYNC. Position within the User Record to return the Label Lines or 0

56

10 DRQOD-POCI-START PIC 9(4) COMP SYNC. Position within the User Record to return the Point of Call Identifier or 0

56

10 DRQOD-ADDRESS-CAT PIC 9(4) COMP SYNC. Location to place the address category on the output records

10 DRQOD-LABEL-LINES OCCURS 8 TIMES INDEXED BY DRQLBL. 15 DRQOD-ADDR-START PIC 9(4) COMP SYNC. The position within the label line

of the “output label lines” or the position within the User Address record (with the high order bit set) or 0 if it is not used.

56



15 DRQOD-ADDR-LENGTH PIC 9(4) COMP SYNC. The length of the label line or 0 15 DRQOD-ADDR-CONTAINS PIC X(8). All of the content codes of the

label line or Spaces if not used. The order of the codes is the order in which the information will be strung into the label line.

57

10 DRQOD-EXTRANEOUS-HANDLES. 57 15 DRQOD-KEEP-11 PIC X(1). Y - to keep the extraneous

information on street type recordsN - to remove extraneous information on street type records

15 DRQOD-KEEP-21 PIC X(1). Y - to keep the extraneous information on street served by route type recordsN - to remove extraneous information on street served by route type records

15 DRQOD-KEEP-32 PIC X(1). Y - to keep the extraneous information on PO box type recordsN - to remove extraneous information on PO box type records

15 DRQOD-KEEP-42 PIC X(1). Y - to keep the extraneous information on route type recordsN - to remove extraneous information on route type records

15 DRQOD-KEEP-52 PIC X(1). Y - to keep the extraneous information on general delivery type recordsN - to remove extraneous information on general delivery type records

15 DRQOD-TRUNCATE PIC X(1). Y - to truncate extraneous information to prevent oversized conditionsN - to not allow information in the extraneous field to be truncated on output

57

10 DRQOD-DSNAMES. 15 DRQOD-VALID-DSN PIC X(44). DS Name of Valid File (spaces

are acceptable) 15 DRQOD-CORRECED-DSN PIC X(44). DS Name of Corrected file

(spaces indicates valid file was used)

15 DRQOD-UNCORRECED-DSN PIC X(44). DS Name of Uncorrected file (spaces are acceptable)

15 DRQOD-NN-COMPLIANT-DSN PIC X(44). DS Name of Oversized file (spaces indicate Uncorrected file was used)

10 DRQOD-DDNAMES. 15 DRQOD-VALID-DDN PIC X(8). DDName used for the valid

records (set to CORRECT for default)

15 DRQOD-CORRECTED-DDN PIC X(8). DDName used for the corrected records (set to CORRECT for default)

15 DRQOD-UNCORRECTED-DDN PIC X(8). DDName used for the uncorrected records file (Set to UNCOR for default)

15 DRQOD-NN-COMPLIANT-DDN PIC X(8). DDName used for the oversized file (set to OSZFILE for default)

10 DRQOD-SUITE-DEFAULT-KW PIC X(12). A keyword to replace invalid suite keywords with if the

58



Canada Post rules require a valid keyword to be used.

10 DRQOD-CASE-TRANSLATION PIC X(1). Y - Translate to proper addressing upper & lower caseN - Leave all address elements in upper case

88 DRQOD-NO-TRANSLATION VALUE 'N'. 88 DRQOD-TRANSLATE VALUE 'Y'. 10 DRQOD-OPTIMIZE-QC-CODE PIC X(2). QC - to return QC as a province

when the optimal code for Quebec is to be usedPQ - to return PQ as a province when the optimal Quebec code is to b e used

10 DRQOD-TRANSLATIONS OCCURS 15 TIMES 58 15 DRQOD-UPPER-CASE-ACCENT PIC X(1). Positional translation character

or spaces if no accent translations have been requested

15 DRQOD-LOWER-CASE-ACCENT PIC X(1).INDEXED BY DRQLBL.

Positional translation character or spaces if no accent translations have been requested

10 DRQOD-RURAL-FILE. 15 DRQOD-RURAL-DDN PIC X(8). DDName of Rural and LVR

records (spaces are acceptable and indicate file not used)

15 DRQOD-RURAL-DSN PIC X(44). Dataset Name of Rural File (spaces are acceptable and indicate file not used)

10 FILLER PIC X(18).05 DRQ-RUN-CONDITIONS. 59 10 DRQRC-DIR-PREFIX PIC X(44). Spaces - Dynamic allocation is

not possible as it happens at parameter edit time.

10 DRQRC-OPTIMIZE-PROVINCE PIC X(1). Y - to optimize all provinces in returning label informationN - to leave original province code when it is valid to begin with

10 DRQRC-OPTIMIZE-COMMUNITY PIC X(1). Y - to return the optimal community name when it fits in the output recordN - to use the input community name when the input community name is valid and fits

10 DRQRC-OPTIMIZE-PS-NAMES PIC X(1). Y - to optimize the route keywords and postal station informationN - to use the route keywords and postal station information from the User’s Address Lines when it is valid

10 DRQRC-OPTIMIZE-OTHER PIC X(1). Y - to optimize the street directions and street typesN - to use the street direction and street types from the User’s Address Lines when it is valid

10 DRQRC-SPELLING-TOL-1 PIC 9(4) COMP SYNC. 5 10 DRQRC-SPELLING-TOL-2 PIC 9(4) COMP SYNC. 3 10 DRQRC-SPELLING-TOL-3 PIC 9(4) COMP SYNC. 4 10 DRQRC-RUN-TYPE PIC X(1). Usually set to R to perform

Regular correction.59

88 DRQRC-VALIDATION VALUE 'V'. 88 DRQRC-REGULAR VALUE 'R'. 10 DRQRC-COUNT-SWITCH PIC X(1). ‘2’ (‘5’ can be used if no reports

are requested) 88 DRQRC-COUNT-NEVER VALUE '1'. Not currently available 88 DRQRC-COUNT-ALLWAYS VALUE '2'. Count all records, display all

reports



88 DRQRC-COUNT-CORRECTS VALUE '3'. Not currently available 88 DRQRC-COUNT-NR-NEVER VALUE '4'. Not currently available 88 DRQRC-COUNT-NR-ALLWAYS VALUE '5'. No reports 88 DRQRC-COUNT-NR-CORRECTS VALUE '6'. Not currently available 10 DRQRC-INCORE-RNG4 PIC X(1). N 10 DRQRC-PERMIT-ALTERNATES PIC X(1). Y - to allow Dr. Q to use the 13

and 18 character abbreviations for communities if community names used do not fit in the label line space.N - to call the record oversized (non-complied) if the community name does not fit the output requirements

10 DRQRC-MISSING-STREET-NO PIC X(1). Y - to allow Dr. Q to validate input records which do not have street numbers (when CPC approves of missing street numbers)N - to tell Dr. Q to reject street type records without street numbers

10 DRQRC-PERMIT-RURAL-COR PIC X(1). Y - tells Dr. Q to correct Rural and LVR recordsN - tells Dr. Q to call Rural and LVR records Valid immediately and not to correct any address data

10 DRQRC-REFORMAT-ALL-RECS PIC X(1). Y - tells Dr. Q to attempt to standardize all records to the output specifications requested, regardless of the classification of the record (uncorrectable, corrected, valid)N - tells Dr. Q to standardize only the records which are Valid or Corrected.

10 DRQRC-AGGRESSIVE-EXTRA PIC X(1). Y - tells Dr. Q to use an aggressive algorithm to eliminate extraneous data between components.N - tells Dr. Q to use the standard algorithm to eliminate extraneous data from input addresses.

10 FILLER PIC X(46).05 DRQ-CALLBACK-CODES. Spaces 10 DRQCC-RETURN-CODE PIC X(1). 88 DRQCC-VAL-COMPLIED VALUE 'V'. 88 DRQCC-VAL-NON-COMPLIED VALUE 'O'. 88 DRQCC-COR-COMPLIED VALUE 'C'. 88 DRQCC-COR-NON-COMPLIED VALUE 'N'. 88 DRQCC-UNCORRECTABLE VALUE 'I'. 88 DRQCC-US VALUE 'F'. 10 DRQCC-NON-COMPLIANT-LINE PIC 9(1) COMP-3. 10 DRQCC-LANGUAGE-CODE PIC X(1). 88 DRQCC-ENGLISH VALUE 'E'. 88 DRQCC-FRENCH VALUE 'F'. 88 DRQCC-UNKNOWN VALUE 'U'. 10 DRQCC-RECORD-CLASS-OUT PIC X(1). 88 DRQCC-URBAN VALUE 'U'. 88 DRQCC-RURAL VALUE 'R'. 10 DRQCC-DEBUGGING-AREA PIC X(20). 10 DRQCC-IN-CATEGORY PIC X(1). 88 DRQCC-IN-URBAN VALUE 'U'. 88 DRQCC-IN-RURAL VALUE 'R'. 88 DRQCC-IN-LVR VALUE 'L'.



88 DRQCC-IN-FORIEGN VALUE 'F'. 10 DRQCC-IN-CLASS PIC X(1). 88 DRQCC-IN-VALID VALUE 'V'. 88 DRQCC-IN-INVALID VALUE 'I'. 10 DRQCC-OUT-CATEGORY PIC X(1). 88 DRQCC-OUT-URBAN VALUE 'U'. 88 DRQCC-OUT-RURAL VALUE 'R'. 88 DRQCC-OUT-LVR VALUE 'L'. 88 DRQCC-OUT-FORIEGN VALUE 'F'. 10 DRQCC-OUT-CLASS PIC X(1). 88 DRQCC-OUT-VALID VALUE 'V'. 88 DRQCC-OUT-CORRECTED VALUE 'C'. 88 DRQCC-OUT-UNCORRECTED VALUE 'I'. 88 DRQCC-OUT-U-OVERSZD VALUE 'B'. 88 DRQCC-OUT-C-OVERSZD VALUE 'N'. 88 DRQCC-OUT-V-OVERSZD VALUE 'O'. 10 FILLER PIC X(46).

Figure Chapter 6 -3 FT06COB copy Member (Descriptions)

Setup of FT06 (without using parameter edit)There are two methods of setting up the FT06/FT06COB area. You may choose to create a parameter file and allow the program to fill in an FT06 structure, or you may choose to fill in the structure within your mainline program.

Before setting up the FT06 or FT06COB area, the programmer must make the same decisions about the input, output and file setup as someone setting up a parameter table. Dr. Q was designed for flexibility which complicates the decision making process in setting up the control information.

The control information is divided into five sections. The five sections (which are equivalent to the CNTLPARM statements) are:

Input File Description Describes the input address lines and their contents Report Information What information is to be put on report files Output Description Describes what and where the information returned from Dr. Q will

be placed within the 4096 byte user area. Run Conditions Describes what actions Dr. Q will perform (type of

correction/validation) Return Codes Output Codes for the calling programs analysis

Initializing the control information involves setting up the input, output, report information and run condition areas to define how Dr. Q will interpret the input user address, the format of the input user address on return, and how Dr. Q should process the record. In order to understand how to set up Dr. Q, each area in the FT06COB copybook will be discussed. Please note that in some situations the area does not have to be initialized. If an area need not be initialized, or is not used in Dr. Q, it has been omitted from the documentation.

DRQ-INPUT-FILE-DESC.


The input file description parameters describe the “User Record” that you have set up. The areas describe the structure of the 4096 byte area, where to find address information, and what types of information to find in those areas.

DRQIF-FILE-LENGTHThe file length parameter is important in two respects. The input file length is used internally by Dr. Q to tell it what part of the user record is reserved as the input area. Dr. Q uses the remaining parts of the user record for working storage and for returning the information requested in the output parameters. Secondly, Dr. Q uses the area to determine the length of the input record to move (or to retain) to the DRQOD-INPUT-REC-START position within the user record on return from the program.

DRQIF-FILE-DDNAMEThis field is used by IO module DRQI0135 to locate the input file coded in the JCL and read records from this file. If you are modifying the input file read process, you may initialize this field to spaces

DRQIF-FILE-DESCRIPTION This field is a used defined description of the input record.

The DRQIF-FILE-DESCRIPTION and DRQIF-FILE-DSNAME are optional and used for report purposes only. Any valued coded in these fields will overlay the coded control parameter values. On all reports the DRQIF-FILE-DSNAME is “strung” together with DRQIF-FILE-DESCRIPTION in brackets and centred within the heading.

DRQIF-ADDRESS-LINES

The 8 DRQIF-ADDRESS-LINES are to tell Dr. Q where to look in the 32K byte input area for addressing information and what types of information is contained in each line. It is better practice to define the address lines in the order in which they would normally be presented to Canada Post on an address label. Address lines must be defined sequentially. Address lines which are not used must be set to length = 0, start = 0, contains = all spaces.

DRQIF-ADDRESS-STARTThis field’s value is the starting column of the address line. The starting column is found with the assumption that the first position in the user record is column 1. If the address line is not used at all, the start is set to zero. All address lines that are used, must be ordered sequentially. Do not define a start value for address lines 1, 2, initialize 3 to 0, and give a start value for address line 4.


DRQIF-ADDRESS-LENGTHThis field’s value is the length of the address line.

DRQIF-ADDRESS-CONTENTS This field describes what types of information can be found in the address line. This 40-byte area tells Dr. Q what address information can be found in the user address line. You can limit Dr. Q to search for specific address components within any address line. For example, if you have allowed for users to enter information into a municipality field on the screen, you could take that field, place it into the user address record, and tell Dr. Q that this address line contains only municipalities. In the other address line descriptions, you can tell Dr. Q not to look for municipality information. The codes which are valid in the DRQIF-ADDRESS-CONTENTS are all considered “synonym classes” and can be found on page 61, in Appendix A - Synonym and Word Classes. Some common values for this 40-byte field are:

Address Line Contents

Value of DRQIF-ADDRESS-CONTENTS

All Values CDHLMWXYZ123FAN@

No Postal Code CDHLMWXYZ123FAN

Postal Code Only @

Municipality & Province

FAN

Province Only A

Address Information Only

CDHLMWXYZ123

Suite Information Only

LX

Table Chapter 6 -1 Common Values for Input Address Line Contents

DRQIF-LANGUAGE-START

The language start value is set to indicate the position in the user record where Dr. Q can find an indicator as to whether or not to use the French accented data on return. If you are not using the accented information or you intend to use it all the time, or you intend to set the use flag yourself, you should initialize this value to 0.

DRQIF-FRENCH-CODE-VALUE


This is a left justified value which Dr. Q is to look for starting in the column obtained from the language-start for a length of the language length to indicate whether the record is to use the accents or not. If you are not using the accented information or you intend to use it all the time, or you intend to set the use flag yourself, you should initialize this value to spaces.

DRQIF-LANGUAGE-FLAG

This is an indicator used to tell Dr. Q when to use the accented database. The valid values for this flag are:

‘N’ – Do not accent if a value is found in French-Code-Value at language-start, language-length.

‘V’ – Accent if a value is found in French-Code-Value at language-start, language-length.

‘A’ - Always accent where possible

Space - Never Accent

DRQ-OUTPUT-DESCRIPTIONThe output description parameters tell Dr. Q what you want the user record area to look like after a call to Dr. Q returns either a Valid or a Corrected address.

DRQOD-MP-CODE-START

A 15 byte area which returns a unique value for every address in Canada. If you use the fixed Merge Purge Code, place the location of where you want it returned in the DRQOD-MP-CODE-START field, otherwise initialize the value to 0.

DRQOD-CPC-BUFFER-START

A 152 byte area, which is a fully fielded representation of the CPC optimal information for the input address. For further details see page 71. If you use the fixed CPC Buffer, place the location of where you want it returned in the DRQOD-CPC-BUFFER-START field otherwise initialize the area to 0.

DRQOD-ID-MATRIX-START

A 30 byte area which identifies the synonym class identified for each of the words Dr. Q parsed. This class can be used in conjunction with the location matrix in order to identify address and non-address words found in the User Record address lines. If you want to return the identification matrix, place the position within the User Address Record into the DRQOD-ID-MATRIX-START field. If you do not require this field, initialize the start position to 0.


For a list of the synonym values that can be returned, see Appendix A - Synonym and Word Classes on page 61.

DRQOD-LOC-MATRIX-START

A 150 byte area which identifies the size and location of each user word. Used in conjunction with the Identification Matrix, the Location Matrix has the format 30 times, (1 byte binary - Word length, 2 bytes binary - word line number, 2 bytes binary - Word Offset). If you want to return the location matrix, place the position within the User Address Record into the DRQOD-LOC-MATRIX-START field. If you do not require this field, initialize the start position to 0.

DRQOD-INPUT-REC-START

You can request that Dr. Q shuffles your input record into any position when returning. For example, suppose on return you wished to access the User Address area by POCI in the first 9 bytes, and the user input record in the bytes proceeding. If you wish to retain the Input Information, which is recommended, store the position of where you want it to be retained in the DRQOD-INPUT-REC-START field. Normally, the input record start position is set to 1.

DRQOD-LABEL-LINE-START

The label is the most frequently used output area. There are up to 8 different output label lines that you can use. Decide where you would like to position the label lines for corrected and uncorrected label lines and store that value in the start location. Alternately, you can store any number other than zero, and use absolute positioning of the individual address lines. For details on absolute positioning of the label lines, see the DRQOD-LABEL-LINES START parameter.

DRQOD-POCI-START

The Point of Call Identifier is the information area that is used to generate 4 state Solomon Reed bar codes using CPC’s PEM module. To request a POCI to be stored on the User Address Record, place the location value in the DRQOD-POCI-START field. If you do not require a POCI, place a 0 in this field.

DRQOD-ADDR-START

The DRQOD-ADDR-START value indicates where to put each of the corrected and valid records standardized and corrected information. If the high order bit of the start position is not set, the start position placed in this area is relative to the start position specified in the DRQOD-LABEL-START. If the high order bit of this start position is set, the start position of this address line is the “absolute position” within the user record.


If an address line is not used or not required, initialize the start value to 0. When filling out the 8 label areas, you must fill each out sequentially without having any positions of zero between them.

DRQOD-ADDR-CONTAINS

Unlike the input description, the DRQOD-ADDR-CONTAINS parameter is set to contain more generic information about what is expected in each address line. When Dr. Q finds 2 or more codes, each area will be strung together into the address line separated by a space. For example, if a code of “CP” is placed in the DRQOD-ADDR-CONTAINS field, this address line will contain the city and province separated by a space on output. If Dr. Q sees that the line contains the value of “CPO”, it will string together city and province separated by 1 space, and will attempt to separate province from postal code with two spaces, the optimal format of Canadian Addressing Standards.

The valid codes for the DRQOD-ADDR-CONTAINS fields are:

Code Address Information Returned

C City

P Province

A Address

M Extraneous Data

O Postal Code

L Suite Keyword

X Suite Number

Table Chapter 6 -2 - Valid Output Address Line Contents

DRQOD-EXTANEOUS-HANDLES

DRQOD-KEEP-11, DRQOD-KEEP-21, DRQOD-KEEP-32, DRQOD-KEEP-42, DRQOD-KEEP-52

A value of Y indicates that when the respected address type is passed to Dr. Q, then the extraneous data (non-address data) will be placed in the address label line for all label lines with ‘M’ in the contains field (see Table Chapter 6 -2 - Valid Output Address Line Contents). A value of ‘N’ sets the extraneous data to spaces if the record is determined to be that particular address type.

DRQOD-TRUNCATE


The truncate flag tells Dr. Q what do with records which have extraneous data, but don’t have enough room to put them out in a label line. If the flag is set to ‘Y’, Dr. Q will attempt to truncate the extraneous data from the right (without regard to the position of other address areas within the address line). If the indicator is set to ‘N’, Dr. Q will reject records as ‘non-compliant’ or oversized when extraneous information does not meet labels requirements.

DRQOD-SUITE-DEFAULT-KW

To tell Dr. Q what to use in the case that it must insert a suite keyword. This may not be the only keyword returned on different records, it is a keyword to use when an input suite keyword was required by Canada Post but no accurate suite keyword was found on the record. If the dash (-) character being used, rather than return the suite keyword being returned in a suite keyword field, the suite number and the dash character, will be returned in an address field (if CPC required the keyword to be added).

DRQOD-TRANSLATIONS

These parameters are to allow you to tell Dr. Q how to represent the accented data on your files and screens. There is no standard EBCDIC equivalent for accented characters.

The translation table is filled with character representations for translation within Dr. Q to characters that you want to use to represent the accents. For example, suppose you wished to translate the accented Ê character into a hexadecimal code of 2A. At position 7 in the translation table, you word store X’2A’. Whenever the CPC directories are to return the Ê character, it would be represented on the output label as a X’2A’ character.

Position Upper Case

character

Lower Case

character1 & 2: Â â3 & 4: À à5 & 6: Ç ç7 & 8: Ê ê9 & 10: É é11 & 12: È è13 & 14: Ë ë15 & 16: Î î17 & 18: Ï ï19 & 20: Û û21 & 22: Ü ü23 & 24: Ô ô25 & 26: Ù ùOthers (initialize to spaces) N/A N/A

Table Chapter 6 -3 Representations of Upper and Lower Case Accents


DRQ-RUN-CONDITIONSRun conditions tell Dr. Q what functions you expect it to perform. The major run condition that affects the way in which Dr. Q operates is the Run Type. This controls how Dr. Q is going to correct (or whether it is going to correct) the addresses.

DRQRC-RUN-TYPE

For normal operation of address correction on line, this value will remain at ‘R’ for regular. In the off chance that you wish to validate only, i.e. determine if the address is correct in the first place, you use the run type of ‘V’ for validate only.

Intercepting at I/O Exit PointsIn order to provide users with a full product interface, user exit points are provided with Dr. Q. Each time Dr. Q is going to perform an IO operation, the source code has been provided. Making modifications to these exit points allows users to control all aspects of the operations before any record is written to DASD or reports are written.

Users are encouraged to call PRISM regarding changes to any report programs supplied as part of the Dr. Q package.

The following programs are the provided exit points and can be changed to meet your own needs. For your own convenience, we have also estimated the chance of the modules changing from release to release (not including required recompilations which will be stated at release time).

Module Purpose Chance of Release ChangeDRQI0100 Write record to Corrected File 1%DRQI0125 Write record to Uncorrected

File1%

DRQI0130 Write record to Oversized File 1%DRQI0135 Read Input record 1%DRQI0140 Write record to Valid File 1%DRQR0110 Write Corrected Records

Report15%

DRQR0115 Write Uncorrected Records Report

15%

DRQR0800 Create Report break Title 1%

Figure Chapter 6 -4 Supplied Source Modules

All IO exits are written in High Level Assembler and are provided with the copybook and macros required to run. If you wish more specific information about a particular program and information about how to change it, please call customer service at PRISM.


Tools, Samples and JCL ProvidedBecause of it's dynamic directory structure, Dr. Q provides some helpful tools in order to help users quickly satisfy all of their addressing concerns. This section discusses a few simple utilities that we have included with Dr. Q. It is expected that this section will continue to grow as we release new versions of Dr. Q and develop more utilities with our powerful software.

At present we have included the source and JCL for three simple utilities which might be of help to our customers. These five programs are included with Dr. Q.

DRQT0200 A program that issues a call to the PEM module provided by Canada Post to obtain a barcode for corrected and valid records which Dr. Q has returned a POCI on.

DRQT0105 A program that communicates with the directory files and generates fixed formatted postal code records (closely simulating the records we receive from CPC) based on a file of incoming postal codes.

DRQT0300 A program that simply sets the high order bit to 0 (zero) of a passed halfword. Some users use this to display the DRQOD-ADDR-START and DRQOD-INPUT-REC-START returned from a call to the parameter list edit as this set of programs may set the high order bit to 1 under certain circumstances. It is important that you do not actually edit the DRQOD-ADDR-START location itself before calling Dr. Q as the high order bit is set for use within the Dr. Q modules.

DRQT0400 A program that recreates the directory distributed to PRISM by Canada Post. Some users are used to accessing this file using other software so they can create their own utilities. Some users may recognize this structure by our old ddname FD03600 or NATIONAL.

DRQT0500 A program to return the alternate municipality file from the VBDIR.

Please feel free to try out these programs and make modifications or enhancements to them as you see necessary.

Chapter 7 Appendices

Appendix A - Synonym and Word Classes

Class Description Permitted as Synonym

# Word Deleted / Extraneous information on Community Line

N

? Street Suffix N@ Postal Code N1 Station Name Y2 Station Type Y3 Station Qualifier YA Province YC Street Type YD Street Direction YF Community YH Street Name YL Apartment Keyword YM Route or Box Keyword YN Foreign Record Keyword YW Street Number NX Apartment Number NY Box Number NZ Route Number N

Appendices

Appendix B - Glossary

Address Accuracy

The address accuracy of a particular file is the percentage of the files urban address records that meet Canada Post accuracy requirements plus all of the file’s rural records.

Addressed Admail

Addressed Admail is often referred to as Bulk Mail or Third Class Mail. Mail in this category must meet specific sorting requirements, accuracy requirements, and content restrictions.

Correctable Mail pieces are considered correctable by Dr. Q when there is enough information to accurately identify the unique address components of a record and correctly identify which components of an address can be corrected in order to make the piece CPC valid and still retain its deliverability.

Deliverable The deliverability of a mail piece is the ability of CPC to actually deliver the piece. Deliverability of mail is very independent of the Validity of mail. In some instances there is information which might be required on a piece of mail which is required for delivery but not checked for accuracy by Canada Post. One easy way to remember the difference, is to assume a piece of mail was sent out without a name. For General Delivery type addresses, the address could very well be perfectly valid, however the piece would be considered undeliverable.

Lettermail Known to many as 1st Class mail, this is mail that does not meet CPC requirements for bulk mail. There are several different discount packages for large volume Lettermail users. All discount mailers must meet CPC address accuracy standards.

LVR LVR is an acronym for “Large Volume Receiver”. Tables within Dr. Q determine if a record is a large volume receiver.

Optimal Address

An Optimal Address is an address that is considered to follow Canada Posts guidelines for optimal addresses. Optimal addresses are a subset of addresses that meet CPC address accuracy requirements. For optimal address specifications, see Canada Posts publication “The Canadian Addressing Standard Handbook”, obtainable through your Canada Post Representative.

Postage Discounts

Canada Post offers a number of postage discounts. In order to qualify for postage discounts the mail must meet address accuracy requirements and sortation guidelines.

Rural Route Address

Rural addresses are not identifiable by the inclusion of RR in an address. An address is considered rural only if the postal code has a zero in the second digit and the postal code is on the Canada Post Database.

Appendices

SERP The “Software Evaluation and Recognition Program” is a program offered by Canada Post to help ensure that validation and correction software vendors can help users meet Canada Posts Accuracy requirements. SERP certifies each software vendor annually and has quarterly meetings. Prism also sits on a sub-committee of SERP users which discusses the potential impact of particular rules presented by Canada and by vendors.

Statement of Mailing (SOM)

When a sorted mailing is delivered to Canada Post, A SOM must be submitted with the mailing to notify CPC of the breakdown of the mailing.

Undeliverable Mail

Mail that cannot be delivered to the intended recipient. A Lettermail user receives these mail pieces as returned mail. Addressed Admail users do not receive undeliverable mail. Canada Post delivers this mail to recycling factories and waste disposal sites.

Valid Mail pieces are considered to be valid when the following conditions are met1:

1. All required address components are present.2. No required component that is found on CPC’s Postal Code Data Files (e.g.

“Address Look Up File”, “Municipality Cross-Reference File”, “Street Cross-Reference File”) is missing from the address.

3. The address provides a match for one and only one address on CPC’s Postal Code Data Files.

Urban An urban address, by CPC standards, is any record that does not meet the criteria for being a Rural Address.

1Taken from the SERP handbook Version 3.2, May 1995

Appendices

Appendix C - Corrected Records Report

96/01/12 DOCTOR Q. VERSION 2.2(0) PAGE :2 13:25:03 PRISM DATA SERVICES CRR8000 C O R R E C T E D R E C O R D S R E P O R T ANALYSIS OF DAVEQ.DRQMA.TESTFL ( DESCRIPTION )

POSTAL INPUT OUTPUT CODE ADDRESS ADDRES

M8W 4W3 2 425 HORNER TORONTO ON APT 2 425 HORNER AVE TORONTO ON M8W 4W3

* STREET TYPE AVE INSERTED * APT KEYWORD STANDARDIZED FROM TO APT

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - M8W 4M3 425 HORNER AVE UNIT 2 UNIT 2 425 HORNER AVE ETOBICOKE ON ETOBICOKE ON M8W 4W3

* POSTAL CODE CHANGED FROM M8W4M3 TO M8W4W3

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - PO BOX 6000 STN A PO BOX 6000 STN A FREDERICTON NB FREDERICTON NB E3B 5H1

* POSTAL CODE E3B5H1 INSERTED

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 200-10216 124 ST 200-10216 124 ST NW EDMONTON AB EDMONTON AB T5N 4A4

* STREET DIR NW INSERTED * POSTAL CODE T5N4A4 INSERTED

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20 10216 124 ST APT 20 10216 124 ST NW EDMONTON AB EDMONTON AB T5N 4A3

* STREET DIR NW INSERTED * APT KEYWORD STANDARDIZED FROM TO APT * POSTAL CODE T5N4A3 INSERTED

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - N9A 6K3 PO BOX 129 STN A PO BOX 129 STN A WINDSOR ON WINDSOR ON N9A 6K1

* POSTAL CODE CHANGED FROM N9A6K3 TO N9A6K1

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - G7H 1X8 12 JACQUES CARTIER EST 12 RUE JACQUES CARTIER EST CHICOUTIMI PQ CHICOUTIMI PQ G7H 1X8

* STREET TYPE RUE INSERTED

Appendices

Appendix D - Uncorrected Records Report

96/01/12 DOCTOR Q. VERSION 2.2(0) PAGE :4 13:25:06 PRISM DATA SERVICES UCR8000 U N C O R R E C T E D R E C O R D S R E P O R T ANALYSIS OF DAVEQ.DRQMA.TESTFL ( DESCRIPTION )

POSTAL INPUT ERROR CODE ADDRESS CATAGORY

L7R 3X4 0 INVALID ADDRESS 395C RR 8 BURLINGTON ON

52 DELVRY NUMBER NOT FOUND RR 1 STN LCD 1, BURLINGTON ON L7R3X4 POSTAL CODE CHANGES UNAVAILABLE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A1C 1B5 235-245 WATER ST. INVALID ADDRESS ST. JOHN'S NF

99 STREET NUMBER RANGE ERROR 235-245 WATER ST , ST. JOHN'S NF A1C1B5 106 STREET NUMBER RANGE ERROR 235-245 WATER ST , ST. JOHN'S NF A1C1B6

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A1C 6H5 JACK BADCOCK ADMIN SRV % INVALID ADDRESS 1ST FLR FT WILLIAM B NF

211 STREET NAME NOT FOUND 1 FACTORY LANE , ST. JOHN'S NF A1C6H5 POSTAL CODE CHANGES UNAVAILABLE

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A1C 6H5 JACK BADCOCK ADMIN SRV % INVALID ADDRESS 1ST FLR FT WILLIAM B NF

211 STREET NAME NOT FOUND 1 FACTORY LANE , ST. JOHN'S NF A1C6H5 POSTAL CODE CHANGES UNAVAILABLE

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A1C 5J2 CORNWALL HAMILTON INVALID ADDRESS ST. JOHN'S NF

151 DELVRY KEYWORD NOT FOUND PO BOX 5J2 STN C, ST. JOHN'S NF A1C5J2 POSTAL CODE CHANGES UNAVAILABLE

Appendices

Appendix E - Correction Summary Report

2001/09/06 DOCTOR Q. VERSION 2.6(1) PAGE : 1 14:43:03 PRISM DATA SERVICES CORSUM C O R R E C T I O N S U M M A R Y R E P O R T ANALYSIS OF SYS01249.T144236.RA000.PRS0031M.SORT.H01 ( SAMPLE REPORT )

U.S. RECORDS EXTRACTED TO INVALID FILE: 0

------ URBAN ------ ------ RURAL ------ ------- LVR ------- ------ TOTAL ------ % OF % OF % OF % OF NUMBER INPUT NUMBER INPUT NUMBER INPUT NUMBER INPUT

RECORDS BEFORE CORRECTION 644 100.00 351 100.00 5 100.00 1,000 100.00 VALID RECORDS ......... 293 45.49 117 33.33 1 20.00 411 41.10 INVALID RECORDS ....... 351 54.50 234 66.66 4 80.00 589 58.90

TOTAL OUTPUT RECORDS .... 644 100.00 354 100.00 2 100.00 1,000 100.00 VALID ................. 292 45.34 117 33.05 0 0.00 409 40.90 CORRECTED ............. 239 37.11 147 41.52 0 0.00 386 38.60 VALID AFTER CORRECTION 531 82.45 264 74.57 0 0.00 795 79.50

UNCORRECTABLE ......... 109 16.92 89 25.14 1 50.00 199 19.90 OVERSIZED VALID ....... 1 0.15 0 0.00 1 50.00 2 0.20 OVERSIZED CORRECTED ... 3 0.46 1 0.28 0 0.00 4 0.40 OVERSIZED INVALID ..... 0 0.00 0 0.00 0 0.00 0 0.00 INVALID AFTER CORRECTION 113 17.54 90 25.42 2 100.00 205 20.50

VALID FILE DSN ........... NULLFILE 409 RECORDS CORRECTED FILE DSN ....... NULLFILE 386 RECORDS UNCORRECTED FILE DSN ..... NULLFILE 109 RECORDS RURAL FILE DSN ........... NULLFILE 90 RECORDS OVERSIZED FILE DSN ....... ** USED UNCORRECTED ** 6 RECORDS

OVERSIZED RECORDS URBAN RURAL TOTAL LENGTH CONTAINS ADDRESS LINE 0 0 1 30 EXTRA ADDRESS LINE 4 1 5 30 APT KW, SUITE, ADDR ADDRESS LINE 0 0 0 40 CITY, PROV, PC

Appendices

Appendix F - Statement Of Accuracy

96/01/15 A D D R E S S A C C U R A C Y S T A T E M E N T PAGE : 1 10:54:22 CPCREP

PRISM DATA SERVICES LTD. 2-425 HORNER AVE ETOBICOKE ON M8W 4W3 PH: (416) 255-5556 FAX: (416) 255-1466

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DR Q VERSION 2.2(0) CPC LICENCE EXPIRES : 98/05/01 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

CPC TAPE USED: 1995/10/16

prism data services ltd. 425 horner avenue etobicoke on m8w4w3

NUMBER OF URBAN RECORDS PROCESSED : 302 TOTAL RECORDS PROCESSED : 321 PROCESSING DATE : 1996/01/15

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - U R B A N A C C U R A C Y L E V E L : 74.17% - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

* THIS STATEMENT REFLECTS THE ACCURACY OF THE FILE AFTER CORRECTION

Appendices

Appendix G - Release History

September 2001 Release 2.7This release has been re-certified by Canada Post and the CPC License Expiry date was extended to Sept 30 2003. Coinciding with the re-certification, minor enhancements were made to the Corrected Records Report.

March 2001 Release 2.6The major enhancement in Release 2.6 was to recognize the new territory of Nunavut and the related directory format changes. This release was also enhanced to enable processing of over 500 delivery address records within one postal code.

Sept 2000 Release 2.5Release 2.5 coincides with Canada Posts SERP certification extension to September 30, 2001. Only minor enhancements were made to this release, the principal one being better identification of French street names.

June 1999 Release 2.4Release 2.4(0) coincides with Canada Posts SERP certification through to September 30, 2000. Major enhancements include an overhaul to the CORSUM report, significant changes in the identification of valid addresses.

Three new parameters were added for this release, the “Rural and LVR Correction”, “Reformat All Records” and the “Aggressive Data Elimination” parameters were all added to the Run Description category. Specific details about these new parameters can be found in the RUN CONDITIONS section on page 29. The Run Type (SERP) was eliminated as certification is performed with Run Type (Regular).

The output files changed considerably based on the new parameters. The table on page 10 contains information about the how the new parameters effect the output destination of records under different conditions.

A new file DDNAME was added, the RURFILE. The chart on page 10 shows it’s uses in more detail.

April 1998 Release 2.2(5)Release 2.2(5) adds the additional functionality of returning the French accented characters as provided by Canada Post. Together with the lower case translation, this enhancement gives the flexibility of returning upper & lower case translations with the proper French accent.

For Details on returning French accents see “French Indicator” on page 22 and “Accent Translations” on page 26.

Appendices

January 1998 Release 2.2(4)Release 2.2(4) is released as an upgrade so our customers can take advantage of several enhancements to the Dr. Q system. Most of the enhancement are a result of several customers’ feedback throughout the year.

Major changes for release 2.2(4) are:

There are additions to the parameter files. The “Maximum Pages” parameter has been added to the Report Category to allow you to limit

the number of pages printed off on the Corrected Records Report and the Uncorrected Records Report for any particular run

The “Print 1 of nnnnn” parameter has been added to the Report Category to allow you to select only a limited amount of records to be printed on the Corrected Records Report and the Uncorrected Records Report for any particular run. This gives you the ability to print random samples of the reports

The “Report break” parameter has been added to allow you to print off summary reports for individual sections within a file. This gives you the ability to run Dr. Q on an entire file, yet keep the reports for individual departments within the organization.

The throughput and CPU times have been improved. Generally a CPU improvement of 40% for all files. Even greater improvements (up to 6 times as fast) for larger files (100,000+, depending on the

machine and the address types).

IO routines modificatied. All files are closed and their DCB’s are freed by Dr. Q to ensure compatibility with different

operating systems. The IO routines have been modified so that even when a file is not used, it is opened and closed

to allow the MVS system to initialize the file properly, even if it contains no records. The ability to not put in a DD statement for the Correct file has been added. If the DD statement

is not in the JCL, Dr. Q will put corrected records into the Valid file.

May 1997 Release 2.2(0)Version 2.2 is being released as an upgrade to be compatible with changes in CPC requirements for address management software. Along with these changes, we are pleased to incorporate many changes and additions which have been requested by our customers. That’s why we say “Dr. Q is designed by our customers for our customers”.

Some of the changes for release 2.2 are:

The manual updated The parameters are described in a table as well as in individual sections The technical setup requirements of the FT06 copybook are documented so users do not have to

call our parameter edit. The IO modules are documented.

Appendices

There are additions to the parameter files. The LOG NOTIFY INTERVAL allows you to track the progress of a Dr. Q run by sending

messages to a running Dr. Q into the JESMSGS Dataset. The parameter allows you to control how many records to process before sending the message.

The LOWER CASE TRANSLATION allows you to create a label buffer with Proper upper/lower case address translation.

The INCORE RNG4 parameter has been added to allow you to control whether Dr. Q can load up a small Directory file into core storage to increase response speed

The OPTIMAL QUEBEC CODE allows users to continue to use PQ as the optimal Quebec code.

The ADDRESS CATEGORY output area has been added to allow you to place an indicator on all of the output files which tells you if the record was urban, rural or foreign.

Appendices

Appendix H - “Fixed CPC buffer” Description

Field Name Length DescriptionRecord Type 2 11 - Street Addresses

21 - Street Service by Route32 - Post Office Box42 - RR/MR/SS Addresses52 - General Delivery

Province Code 2 Optimal Province CodeCommunity 30 Optimal Municipality NameSuite Number 6 Users Suite NumberStreet Number 6 Users Street NumberStreet Suffix 1 Alpha Code or:

1 - 1/22 - 1/43 - 3/4

Street Name 30 Optimal Street NameStreet Type 6 Optimal Street TypeStreet Direction 2 Optimal Street DirectionPostal Station Name 30 CPC Postal Station Name

(for 32, 42 52 record types)Postal Station Type 5 CPC Postal Station Type

(for 32, 42 and 52 type records)

Postal Station Qualifier 15 CPC Postal Station Qualifier (for 32, 42 and 52 type records)

PO Box Number 5 Users PO Box numberRoute Service Class 2 Route Class (RR, MR or

SS)Route Service Number 4 Users Service numberPostal Code 6

Appendices

Appendix I - Error Codes on UNCOR file at LRECL+1

This two byte error code is found at the end of the input record on the UNCOR file. The file obtains the positioning by using the LRECL parameter of the “Input File Description” parameters. This code will give a general description of the error, which occurred. It is only intended to give you the first problem Dr. Q had in correcting the address.

A

Accuracy.....................................................................64Address

Accuracy.................................................................19General Delievery

Defined..................................................................7PO Box

Defined..................................................................6

Route Service AddressDefined..................................................................7

StreetDefined..................................................................5

Street Served By RouteDefined..................................................................6

Address XE "Address Accuracy" XE "Accuracy" Accuracy.................................................................64

Address Accuracy........................................................64

Code Description/Meaning01 Postal Code not on CPC Directory02 Province not found03 Community not found04 Street Name not found05 Street Type not found or invalid06 Street Direction not found or invalid07 Street Direction not found or invalid08 Street Suffix range error09 Non numeric street number10 Street number exceeds 6 characters11 Street number not found12 Street number range error13 Address on wrong side of street14 Apt/Suite keyword/number invalid15 Apt/Suite number range error/exceeds 6 characters16 Route keyword not found17 Route service not found/range error18 Box keyword not found19 Box number not found20 Box number range error21 Delivery installation name not found22 Delivery installation keyword not found23 Delivery installation qualifier not found24 General Delivery keyword not found25 More than 30 words in this address99 Other/unknown

Appendices

Apartment Keywords.....................................................8Assembler................................................................2, 61

B

Bar Code...............................................................14, 62Point of Call Identifier (P.O.C.I) 14, 27, 34, 35, 36, 39,

50, 58, 62Postbar Encoding Module.................14, 27, 39, 58, 62

Blank Lines.................................................................17

C

Canada Post. 2, 11, 25, 27, 28, 29, 30, 31, 33, 34, 35, 36, 38, 39, 41, 49, 52, 57, 58, 60, 62, 64, 65, 69, 71, 73, 74

COBOL.......................................................2, 44, 47, 48Contains...............................................21, 34, 35, 38, 40Corrected Records..........................20, 37, 39, 61, 66, 71Corrected Records Report............................................11Correction Summary Report........................................11CORSUM....................................................................11

D

DASD................................................................3, 32, 61DDNAME.............................................................21, 48DDNAME DDNAMEParameters

Input File DescriptionDDName.............................................................38

Deliverable....................................................................9DESCRIPTION. 10, 25, 27, 37, 38, 45, 48, 54, 63, 73, 74DFHSM.........................................................................3Directory Files...............................................................4discount.......................................................................64DSNAME..........................................................4, 21, 48

Parameter..................................................................5

E

Extraneous Data.........................................14, 41, 59, 63

I

Identification Matrix....................................................57Input File.........................................................27, 54, 74

Requirements.............................................................5Installation....................................................................3

Requirements.............................................................3

J

JCL...........................................13, 32, 43, 44, 61, 62, 71Directory...................................................................4Dr. Q JCL................................................................12Dr. Q JCL......................................................9, 12, 13Installation.................................................................3

K

keyword................................6, 28, 29, 31, 40, 51, 60, 74

L

listing....................................................................44, 46Location Matrix........................26, 34, 35, 36, 39, 49, 57LRECL.........................13, 22, 27, 33, 34, 36, 38, 45, 74

Input File...................................................................3LVR............................7, 8, 30, 31, 41, 51, 52, 53, 64, 70

M

mailing..................................................................19, 65merge....................................................................26, 39Merge/Purge................................................................15

N

names..............................................................26, 35, 52

O

Oversized...................................................10, 36, 51, 61Oversized Records.......................................................36

P

Parameters....................33, 35, 38, 48, 54, 57, 60, 71, 74Defined......................................................................1Input File Description........................................17, 21

Address Line..................................................21, 22DDName..................................................21, 38, 51DSName...................................................21, 38, 48File Description..............................................21, 22French Indicator.......................................21, 22, 38LRECL...............................................21, 22, 27, 38

Output Areas......................................................17, 24Address Category....................24, 27, 33, 34, 36, 40Fixed CPC Buffer.....................................24, 25, 57Identification Matrix....24, 25, 26, 34, 35, 36, 39, 57Input record............................24, 25, 34, 35, 36, 39Label...........................24, 25, 27, 29, 34, 35, 36, 40Location Matrix...........24, 25, 26, 34, 35, 36, 39, 57Merge Purge Code..................24, 26, 34, 35, 36, 39POCI............................................24, 27, 34, 36, 39

Report Information.............................................17, 19Company Information...............................19, 37, 49Log Notify Interval...................................19, 20, 37Maximum Pages.................................19, 20, 37, 71Non Address Data..........................................19, 37Print 1 of n.........................................19, 20, 37, 71Report break.................................19, 20, 37, 61, 71

Run Conditions..................................................17, 30Allow Alternates............................................30, 33Directory Prefix.............................................30, 32Incore RNG4..................................................30, 32Missing Street Numbers.......................................30Optimal Quebec Code....................................30, 31Optimize Community.....................................30, 31Optimize Other Components..........................30, 31Optimize Province...............................................30Optimize Route Kewwords..................................30

Appendices

Optimize Route Keywords...................................31Reformat all Records...........................................30Run Type.......................................................30, 33Rural and LVR Correction.............................30, 31

Syntax.....................................................................17Penthouses.....................................................................8

R

Reports................1, 10, 19, 20, 22, 37, 44, 48, 52, 61, 71CORSUM................................................................11CRR8000.................................................................11Statement of Accuracy.............................................11Statement of Mailing...............................................11Summary.................................................................11UCR8000.................................................................11

rural.............................................................................64Rural......................................................6, 10, 11, 64, 72

S

Canada Post.....................................................33, 41, 65SOM......................................................................11, 65source code..............................................................2, 61standardization........................................................1, 40Statement of Accuracy.......................................1, 11, 20Suite Keywords.............................................................8suites................................................................22, 25, 28synonyms.................................................................1, 43

U

UCR8000....................................................................11Uncorrected Records Report........................................11urban............................................6, 9, 10, 11, 64, 65, 72Urban............................................................................9user exit points............................................................61

V

validation.....................................................1, 31, 54, 65

Appendices

Appendices

Documents

Introduction - · Web viewAppendix A - Synonym and Word Classes 65. Appendix B - Glossary 66. Appendix C - Corrected Records Report 68. Appendix D - Uncorrected Records Report