# Presentation: 708537

**NCOA****Link®**** ****Changes****Corresponding to CASSTM Cycle M****JULY 31, 2008**

## NCOALink® Changes

**Summary of Changes**
- Query prefix name
- Check Middle Name/Initials
- Significant Leading Zeros
- Certification/Audit Output header record
- Automate naming of Certification/Audit Output
- Update hard coded values
- Reporting and CSL changes

## NCOALink® Changes

**Query prefix Name - display the Query Prefix name (MR/MRS/MS) when Query prefix gender is different from the COA GENDER**
- CALVIN = MALE GENDER
-          Input           Individual COAs        Query Name	       Return Code
-      MS CALVIN OLINGER   CALVIN OLINGER(m)     MS CALVIN OLINGER       13
-      MR CALVIN OLINGER   CALVIN OLINGER(m)     CALVIN OLINGER          A
-      CALVIN OLINGER	     MRS CALVIN OLINGER(f) CALVIN OLINGER          13
-      MRS CALVIN OLINGER  MRS CALVIN OLINGER(f) CALVIN OLINGER          A
-      MR CALVIN OLINGER   MRS CALVIN OLINGER(f) MR CALVIN OLINGER       13
- CALLIE – FEMALE GENDER
-      MS CALLIE OLINGER   CALLIE OLINGER(f)     CALLIE OLINGER          A
-      MR CALLIE OLINGER   CALLIE OLINGER(f)     MR CALLIE OLINGER       13
-      CALLIE OLINGER	     MRS CALLIE OLINGER(f) CALLIE OLINGER          A
-      MRS CALLIE OLINGER  MRS CALLIE OLINGER(f) CALLIE OLINGER          A
-      MR CALLIE OLINGER   MRS CALLIE OLINGER(f) MR CALLIE OLINGER       13
-      MR CALLIE OLINGER   MR CALLIE OLINGER(m)  CALLIE OLINGER          A
- ZOOLUE – UNDEFINED GENDER
-      MS ZOOLUE OLINGER   ZOOLUE OLINGER(u)     ZOOLUE OLINGER          A
-      MR ZOOLUE OLINGER   ZOOLUE OLINGER(u)     ZOOLUE OLINGER          A
-      ZOOLUE OLINGER	     MRS ZOOLUE OLINGER(f) ZOOLUE OLINGER          A
-      MRS ZOOLUE OLINGER  MRS ZOOLUE OLINGER(f) ZOOLUE OLINGER          A
-      MR ZOOLUE OLINGER   MRS ZOOLUE OLINGER(f) MR ZOOLUE OLINGER       13
-      MR ZOOLUE OLINGER   MR ZOOLUE OLINGER(m)  MR ZOOLUE OLINGER       A

## NCOALink® Changes

- CHECK MIDDLE NAME/INITIALS
- Must Check Against ALL Returns Containing Middle Name/Initials.
- Validate Middle Name/Initials For ANY NCOALink Response

**Notes:**
CHECK MIDDLE NAME/INITIALS – Please review your logic to make sure it is checking the input middle name/initials against all returns that contain a middle name/initials.
If you have an input middle name/initial and you have obtained a response FROM NCOALink regardless if it is a software or data defined return code make sure the software is validating the middle name/initals.

## NCOALink® Changes

- FIRST NOTIFICATION – SEPTEMBER 2005

**Sent:** Friday, September 30, 2005 5:19 PM**Subject:** NCOALink - Potential IssueIt has come to our attention that there may be an issue regarding NCOALink returned addresses (return code A, 91, 92) in which the address being returned contains a significant leading zero in the primary number. The following PRODUCTION record will obtain a return code A with a leading significant zero.
- KARL ROCK  4128 WEST BELLA VISTA ST   LAKELAND  FL338105906
- If you are handling it correctly the output will be:
- 04200 44TH ST  BLOOMINGDALE   MI490269608006R002200504IM
- If you are **NOT** handling it correctly the output will be:
- -4200 44TH ST  BLOOMINGDALE   MI490269608006R002200504IM
- If the (-) ‘dash’ is the first character in the PRIMARY number or SECONDARY number it must be converted to a zero.
- Please review the sample program .......

**Notes:**
From: Ncsc, NCOALink - Memphis, TN [mailto:NCOALINK@usps.gov] Sent: Friday, September 30, 2005 5:19 PMTo: Ncsc, NCOALink - Memphis, TNSubject: NCOALink - Potential IssueAll Developers,
It has come to our attention that there may be an issue regarding NCOALink returned addresses (return code A, 91, 92) in which the address being returned contains a significant leading zero in the primary number. The following PRODUCTION record will obtain a return code A with a leading significant zero.
KARL ROCK  4128 WEST BELLA VISTA ST   LAKELAND  FL338105906
If you are handling it correctly the output will be:
04200 44TH ST  BLOOMINGDALE   MI490269608006R002200504IM
If you are NOT handling it correctly the output will be:
-4200 44TH ST  BLOOMINGDALE   MI490269608006R002200504IM
If the (-) ‘dash’ is the first character in the PRIMARY number or SECONDARY number it must be converted to a zero.
Please review the sample program utas18.cbl paragraph 3000-build-output.
If you are not handling this correctly, a patch is required for immediate dissemination ASAP. A recertification is not required for this change. Please notify us if you have this issue and when it is expected to be rectified.
Thanks
 Charles Arnette
National Customer Support Center
800-589-5766

## NCOALink® Changes

- LEADING SIGNIFICANT ZERO
- Use Dash As Place Holder
- Also Occurs in ZIP + 4® Software
- Update Documentation for Customer
- Some Still Receiving Dash In Output
- USPS Will Update Software Developers Guide and Source Code

**Notes:**
Leading significant ZERO
The dash is a place holder indicating that Zero is significant for the address. This was used so programs could recognize a significant zero and not automatically strip out all preceding zeros. This issue also occurs in your ZIP + 4® software.
Update your technical documentation for your customers so they will understand how to handle records with a leading ZERO. Some customers are/were still receiving the dash in their output.
We will update our Software Developers Guide and source code.  

## NCOALink® Changes

- CERTIFICATION/AUDIT OUTPUT HEADER RECORD
- Existing DPVTM Date Field Redefined to reflect the DPV product date used by the alternate process for Full Service Providers
- Fields Will Be Added to output data file header record
- NCOALink Software Name
- NCOALink Software Version
- DSF2TM Date
- LACSLinkTM Date
- SuiteLinkTM Date
- Fields Must Be Populated When Product Is Used
- If Product Not Used - Dates Zero Filled

**Notes:**
Certification/Audit Output header record

The existing DPVTM date field in the Certification/Audit output data file header record will be redefined as the DPV date which is utilized by the NCOALink Full Service Providers. If the product is not used then the dates will be zero filled.

The LACSLink, SUITELink, DPV, DSF2 product dates directly associated with ZIP + 4® directories will be added to the Certification/Audit output data file header record. These fields must be populated with the appropriate product date when that product is being used. If the product is not used then the dates will be zero filled. 

## NCOALink® Changes

- CERTIFICATION/AUDIT OUTPUT HEADER RECORD - Continued
- Matching Logic Applied Added - Corresponds To Same Field In CSL
- S = Standard (Business, Individual and Family matches allowed)
- I = Individual only
- B = Business only
- C = Individual and Business only
- R = Individual and Family only (Residential)
- NCOALink Product Version Added
- A = 48 HASH
- B = 48 FLAT
- C = 18 HASH
- D = 18 FLAT
- E = ANK HASH
- F = ANK FLAT

**Notes:**
Certification/Audit Output header record – continued

The field Matching Logic Applied will be added to the Certification/Audit output data file header record. The contents will correspond to the exact same field defined in the Customer Service Log (CSL). The field will consist of the following values:
	S = Standard (Business, Individual and Family matches allowed), 
	I  = Individual only,  B = Business only,   C = Individual and Business only,
	R = Individual and Family only (Residential)

The NCOALink Product version will be added to the Certification/Audit output data file header record. A = 48 HASH,  B = 48 FLAT, C = 18 HASH, 
	 D = 18 FLAT,  E = ANK HASH, F = ANK FLAT 

## NCOALink® Changes

- CERTIFICATION/AUDIT OUTPUT HEADER RECORD – AFTER CHANGES

| TEST CLIENT OUTPUT FILE HEADER RECORD |  |  |  |  |
| --- | --- | --- | --- | --- |
| RECORD
FROM | POSITION
TO | FIELD NAME | LENGTH | COBOL |
| 1 | 328 | PREVIOUS FIELDS REMAIN UN CHANGED | 328 | X(328) |
| 329 | 336 | PROCESSED AGAINST  DPV RELEASE DATE (DATA DATE) (Alternate
PROCESS FOR FULL SERVICE) | 8 | 9(08) |
| 337 | 340 | PROCESSED ON PLATFORM ID (platform ID assigned by USPS) | 4 | X(04) |
| *341 | 370 | NCOALink Software Name | 30 | X(30) |
| *371 | 382 | NCOALink Software Version | 12 | X(12) |
| *383 | 390 | DSF2 RELEASE DATE (STAND ALONE  FOR FULL SERVICE) | 8 | 9(08) |
| *391 | 398 | SuiteLink RELEASE DATE (ALTERNATE  FOR FULL SERVICE) | 8 | 9(08) |
| *399 | 406 | CASS DPV RELEASE DATE | 8 | 9(08) |
| *407 | 414 | CASS LACSLink RELEASE DATE | 8 | 9(08) |
| *415 | 422 | CASS SuiteLink RELEASE DATE | 8 | 9(08) |
| *423 | 430 | CASS DSF2 RELEASE DATE | 8 | 9(08) |
| *431 | 431 | Matching Logic Applied | 1 | X(01) |
| *432 | 432 | NCOALink Product Version (A = 48 HASH,  B = 48 FLAT, C = 18 HASH,  D = 18 FLAT, 
E = ANK HASH, F = ANK FLAT)  | 1 | X(01) |
| 433 | 997 | FILLER | 565 | X(566) |
| 998 | 998 | RECORD TYPE (Header/Detail) (H,D) | 1 | X(01) |
| 999 | 1000 | CARRIAGE RETURN LINE FEED | 2 | X(02) |
|  |  |  = FIELDS ADDED |  |  |

## NCOALink® Changes

- AUTOMATE NAMING OF CERTIFICATION/AUDIT AND REPORTING
- Software Required To Automate/Format Name
- Certification / Audit Results
- Monthly Reports
- Certification/Audit Output File Name - ####$$$$&.TXT
- #### = License number  $$$$ = Platform    & = NCOALink Product Version
- Example= 0101LBBGA.TXT
- Report File Name - #$$$$&YY.TXT
- # = C, or P, or B   $$$$ = Platform & = Month(1 – 9, A,B,C)  YY=2 byte year
- Example= CLBBGA07.TXT
- Certification/Audit Zip File Name  - ####$$$$&.ZIP
- #### = License number 	    $$$$ = Platform	    & = NCOALink Product Version
- Example= 0101LBBGA.ZIP

**Notes:**
Automate naming of Certification/Audit and Reporting

The software will be required to automate/format the name of the certification and audit result files and the monthly reports.

The Certification/Audit output file will be named in the following manner:
####$$$$&.TXT
#### = License number  $$$$ = Platform    & = NCOALink Product Version
Example= 0101LBBGA.TXT

The report files will be named in the following manner:
#$$$$&YY.TXT
# = C, or P, or B   $$$$ = Platform & = Month(1 – 9, A,B,C)  YY=2 byte year
Example= CLBBGA07.TXT

Certification/Audit file & reports must be ZIPPED into a single file named:
####$$$$&.ZIP
#### = License number 	    $$$$ = Platform	    & = NCOALink Product Version
Example= 0101LBBGA.ZIP

## NCOALink® Changes

- AUTOMATE NAMING OF CERTIFICATION/AUDIT AND REPORTING
- The Production Monthly Report Name - #$$$$&YY.DAT
- # = C, or P, or B   $$$$ = Platform	& = Month (1 – 9, A,B,C)   YY=2 byte year
- Example= CLBBGA07.DAT
- Monthly Reports Zip File Name  - $$$$&YY.ZIP
- $$$$ = Platform         & = Month (1 – 9, A,B,C)   YY=2 byte year
- Example= LBBGA07.ZIP
- Separate Zip File For Each Platform When There Are Multiple Platforms

**Notes:**
Automate naming of Certification/Audit and Reporting

The production monthly reports must be named:
#$$$$&YY.DAT
# = C, or P, or B   $$$$ = Platform	 & = Month (1 – 9, A,B,C)   YY=2 byte year
Example= CLBBGA07.DAT

All monthly reports must be ZIPPED into a single file named: 
$$$$&YY.ZIP
$$$$ = Platform         & = Month (1 – 9, A,B,C)   YY=2 byte year
Example= LBBGA07.ZIP

If there are multiple platforms then each platform will have a separate ZIP file.

## NCOALink® Changes

- Update hard coded values

| Variable Name  | Current Value | New Value   |
| --- | --- | --- |
| PNO-MAX | 420,000 | 480,000  |
| DSC-MAX | 25 | 30  |
| SUF-MAX | 210 | 250  |
| NAM-MAX | 760,000 | 900,000  |
| CRD-MAX | 2,000 | 2,200  |
| LLN-MAX | 35,000 | 42,000 |

**Notes:**
The following fields defined in our software development programs have hard coded values.  The following reflects the variable names and the respective sizes:

## NCOALink® Changes

- REPORTING AND CSL CHANGES
- Reporting Functions Must Produce Output When ANY Values are Zero
- Numeric Fields Zero Filled
- Must Consist Of:
- Header Records
- Appropriate Counts Indicated In File Layouts
- Must Be Able To Regenerate All Reports By Date
- CSL Modifications:
- Six Fields Redefined
- Sixteen Fields Added Using Filler Space

**Notes:**
REPORTING AND CSL CHANGES

All reporting functions must be able to produce the necessary reports when the values are ZERO during the months of no processing. The numeric fields must be zero filled. The report must consist of header records only and appropriate counts as indicated in the file layouts. 

The software must be able to regenerate all reports by date. 

CSL changes:
	1.	The contents/meaning of six fields will be redefined.
	2.	Sixteen fields will be added utilizing the filler space.
	3.	The record size/length will remain the same.

## NCOALink® Changes

- CSL – After Change

| LACSLinkTM Product Information |  |  |  |  |
| --- | --- | --- | --- | --- |
| 1717 | 1737 | LACSLink Software Name (External LACSLink Product) | 30 | X(30) |
| 1747 | 1758 | LACSLink Software Version (External LACSLink Product) | 12 | X(12) |
| 1759 | 1766 | LACSLink Data Release Date Numeric. (External LACSLink Product) | 8 | 9(8) |

| From | To | FIELD NAME & DESCRIPTION | Length | COBOL |
| --- | --- | --- | --- | --- |

| 237 | 266 | DPV Software Name (Full Service DPV Product) | 30 | X(30) |
| --- | --- | --- | --- | --- |
| 267 | 278 | DPV Software Version (Full Service DPV Product) | 12 | X(12) |
| 279 | 286 | DPV Data Release Date (Full Service DPV Product) | 8 | 9(8) |

| DPVTM Product Information |
| --- |

**The above fields ****redefined ****to reflect DPV alternate process for Full Service Providers****.**

**The above fields**** redefined ****to reflect LACS****Link**** Stand alone statistics.**

## NCOALink® Changes

- CSL – After Change

| From | To | FIELD NAME & DESCRIPTION | Length | COBOL |
| --- | --- | --- | --- | --- |

| DPVTM Product Information |  |  |  |  |   |
| --- | --- | --- | --- | --- | --- |
| 2435 | 2464 | DPV Software Name (Internal CASS Product) | 30 | X(30) |  |
| 2465 | 2476 | DPV Software Version (Internal CASS Product) | 12 | X(12) |  |
| 2477 | 2484 | DPV Data Release Date (Internal CASS Product) | 8 | 9(8) |  |

**The above fields ****were added**** to reflect DPV internal CASS results.**

| LACSLinkTM Product Information |  |  |  |  |
| --- | --- | --- | --- | --- |
| 2485 | 2514 | LACSLink Software Name (Internal CASS Product) | 30 | X(30) |
| 2515 | 2526 | LACSLink Software Version (Internal CASS Product) | 12 | X(12) |
| 2527 | 2534 | LACSLink Data Release Date Numeric.  | 8 | 9(8) |

**The above fields ****were added**** to reflect LACS****Link**** internal CASS results.**

## NCOALink® Changes

- CSL – After Change

| From | To | FIELD NAME & DESCRIPTION | Length | COBOL |
| --- | --- | --- | --- | --- |

| DSF2TM Product Information |  |  |  |  |
| --- | --- | --- | --- | --- |
| 2535 | 2564 | DSF2 Software Name (Internal CASS Product) | 30 | X(30) |
| 2565 | 2576 | DSF2 Software Version (Internal CASS Product) | 12 | X(12) |
| 2577 | 2584 | DSF2 Data Release Date (Internal CASS Product) | 8 | 9(8) |

| DSF2 Product Information` |  |  |  |  |
| --- | --- | --- | --- | --- |
| 2585 | 2614 | DSF2 Software Name (External CASS Product) | 30 | X(30) |
| 2615 | 2626 | DSF2 Software Version (External CASS Product) | 12 | X(12) |
| 2627 | 2634 | DSF2 Data Release Date (External CASS Product) | 8 | 9(8) |

**The above fields ****were added**** to reflect DSF****2**** internal CASS results.**

**The above fields ****were added**** to reflect DSF****2**** external CASS results.**

## NCOALink® Changes

- CSL – After Change

| From | To | FIELD NAME & DESCRIPTION | Length | COBOL |
| --- | --- | --- | --- | --- |

| 2635 | 2635 | DPVTM Results to Customer | 1 | X(1) |
| --- | --- | --- | --- | --- |
| 2636 | 2636 | DSF2TM Results to Customer | 1 | X(1) |
| 2637 | 2637 | LACSLInkTM Results to Customer | 1 | X(1) |
| 2638 | 2638 | SuiteLinkTM Results to Customer | 1 | X(1) |

| 2639 | 2999 | FILLER | 361 | X(361) |
| --- | --- | --- | --- | --- |
| 3000 | 3000 | Record Type – H = Header/ D = Detail | 1 | X(1) |

| CR/LF -Carriage Return/Line Feed required at end of the record. |
| --- |

**The above fields ****were added**** to reflect if the results were returned to customer.**

## Thank You