Incrementing Year Fields in Flat Files to Test Year 2000 Compliance Brian Bouvier, Fireman's Fund Insurance Company, Novato, CA.

Transcription

1 Incrementing Year Fields in Flat Files to Test Year 2000 Compliance Brian Bouvier, Fireman's Fund Insurance Company, Novato, CA ABSTRACT One critical task to ensure correct handling of dates.in the 21" century is to parallel test SAS" programs that read flat files. In an environment with hundreds of user-written SAS programs each reading a different extract of a master file, ensuring proper parallel testing is a daunting task. This MVSutility allows end-users to "age" their own data whhout requiring knowledge of JCL or the SAS system and is customizable for use with any flat file. Once the year fields have been identified in the flat file, the utilhy increments all the year fields by a user-supplied amount and produces a new fde. This enables the end-user to produce as many versions of the extract as required to completely test their programs for years 1997,1999,2000,2001, and beyond. INTRODUCTION One of the requirements imposed on insurance companies by the various regulatory bodies is to provide various detailed reports showing premium and loss information. Each regulatory body has H's own data requirements that are independent from all of the others. To support these statutory reporting requirements, a collection of several hundred independent reporting programs have been developed using the SAS system. Each of these programs has a first step that selects specific data from the Corporate Master Files using FileAid and a second step that uses the SAS system to creates the actual report. The main test of the ability of these programs to handle dates after 1999 is to "age" or increment the input data as though the current year is 1999, 2000, 2001 or beyond. Many of these programs read the same Input files, but each select and compute with date fields slightly differently. We quickly discovered that it was impractical to create "generic" test data that could sufficiently demonstrate whether each of these programs was compliant with dates later than Also, since many of these programs are maintained by beginning and intermediate SAS users, ft also became clear that any method to create specific test data for each of the programs had to be user-friendly. Our solution was to develop a utllfty written in base SAS that is called by a CUST that prompts for the required information. Requirements We identified the following requirements for this utilfty: Rl The execution of the utility would introduce no change to the original file or record layout. R2 Does not require programming skill to invoke the utility. R3 The utilfty is easily customizable for a variety of fixed record layouts R4 The user will supply number of years to "age" or increment the data when the utility is invoked. R5 The utilhy will produce several "aged" files with different increments easily. R6 Any years in the data not successfully aged should not be changed. R7 The utilhy will provide a summary of unsuccessfully "aged" fields Requirement R5 allows the creation of several "aged" files so that many different future years can be created to completely test the program. Requirements R6 and R7 allow for fields that have missing values or have alphabetic values (such as NONE). DeSign The CLiST that invokes the utilfty and the SAS program statements are included in Figures 1 and 2. Each of the requirements is addressed in the design statements below. For each design statement, the specific requirement(s) being addressed is identified. Special techniques using the SAS system or SAS macros are also shown. 01 The utllfty reads the entire record as 200 byte blocks of character fields, then goes back and reads the year fields for that record. After incrementing the year fields, output the entire record as character fields, then overwrite the positions with the aged years (Rl) INPUT D2 //SAS Notice that the INPUT statement reads the entire record, then specifically, the year BLOCK.!. BL0CK2 PEFFYR PEXPYR TEFFYR DEFFYR DEXPYR ENTYR INCPYR CYCYR $1. A CLiST (see Figure 1) prompts you for Input Data Set Name and Number of Years to increment the date fields. The CLiST invokes the utility. CLiST passes information to the JCL, which passes tt to the SAS system using the SYSPARM option. (R2, R4) The EXEC statement in the JCL invokes the SAS System: The symbolic variable &AGE is obtained by the CLiST. EXEC SASV6, OPTIONS=SYSPARM=&AGE 03 Specify the locations of the year fields in as few places as possible. Use arrays and macro variables when possible. (R3) All of the year fields are specified using SAS Macro variables. Corresponding variables to hold the error counters are also defined. Each year field also appears in the INPUT statement and the OUTPUT statement. D4 Create output files with the same name as input files whh the extension: Y2K##, where ## is the number of years the dates have been incremented. Delete and overwrhe existing output files Irthey exist. (R5) 65

2 D5 The first step of the batch job submitted by the CLiST uses the IBM"' utility IDCAMS to delete the previous output data set if H exists. The symbolic variables passed from the CLiST are used in the output file name in the JCL. //PDAOTJT DD DSN=&INDSN.. Y2K&AGE, Check each position of each year field. If any position Is not numeric, do not change the field. (R6) The function INDEXC Is used to compare each position of each year field with the numbers 0 through 9. If it is not on the list, then flag the error. IF INDEXC(SUBSTR(YR VARS(I),J,1),' B9') = 0 THEN ERRVARS(I) = 1; The next SAS Macro-statements actually perform the Incrementatlon: "LET KODYEAR = KOD(YR_VlIRS( + &AGE,10**LBNGTE(YR ~(I»);*** LEADING ZERO FOR YBlIRS 01, 02, 03, ETC. ***; "LET PADYEAR = COMPRESS (, O' I I &MODYEAR); u* PUT THE YEAR BACK IN THE ORIGINAL FIELD *; YR_VARS(= SUBSTR (&PADYBAR, LENGTE(&PADYEARI-LBNGTB(YR_VlIRS(I+l, LENGTE(YR_VARS(; 06 For each field whh an invalid year, increment an error counter for that field. Provide counts of each invalid field In an error summary report. (R7) After the DATA Step that increments the year fields, the error file is summarized using the SUMMARY procedure and the results are ready to be reviewed. Instructions for use We created a simple procedure to help Insure that each program was tested appropriately: 8. Record time for conversion and completion date in the Y2K project database. DISCLAIMER The "Incrementing Year Fields in Flat Files to Test Year 2000 Compliance" software ("Software") is provided by Fireman's Fund Insurance Company to you on an "AS IS" basis. IN NO WAY SHALL FIREMAN'S FUND INSURANCE COMPANY BE LIABLE TO YOU FOR DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE FURNISHING, PERFORMANCE OR USE OF THE SOFTWARE PROVIDED BY FIREMAN'S FUND INSURANCE COMPANY TO YOU HEREUNDER. You agree to Indemnify and hold Fireman's Fund Insurance Company, Its parent, their subsidiary and affiliated companies, harmless from and against any and all fiabilities, losses, damages, costs and expenses (including reasonable atturneys' fees) associated with any claim or action arising from your possession or use of the Software. SAS is a registered trademark or trademark of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies. Brian K. Bouvier Fireman's Fund Insurance Company m San Marin Drive Novato, CA (415) BBouvier@ffic.com BBouyjer@oacbell.ne! 1. Record the life cycle phase as "in progress" in Y2K project database 2. Complete the reports as normal for the customers. Y2K compliance should not impact customer deadlines. 3. Test the unmodified reporting program with test data generated whh the utility using several time periods; e.g. age to 1999, 2000, 2001, If the program generates the same results with each of the test data files, no modifications are required. Mark In the program comments that the unit is Y2K compliant with no changes necessary 5. If the program generates different results with any of the test data sets, program modifications are required. Make required changes in program according to corporate standards. Our standard Is the "rule of 30". If a two-digit year is 30 or less, assign the century to be 20. If a two-digit year is 31 or greater, assign the century to be Test the modified program with the same "aged" data sets used with the unmodified program. Follow steps 4 and 5 until the test is successful. 7. Mark in comments that unit is Y2K compliant with "rule of 30" modifications as the method of compliance. 66

3 PROC 0 I*CONTROL MaG CONLIST LIST NOFLUSB THIS JOB WILL INCREMENT ALL THE YEAR FIELDS IN A PDA FILE ON DISK. USE ONLY THE 320 BYTE POAE.K102.A COMPATIBLE FILES WITH THIS UTILITY. SETIO: + WRITE WRITENR ENTER THE INPUT DATA SET NAME (FULLY QUALIFIED, NO APOSTROPHES) WRITE READ IlDSN ClcrEAR: + WRlTENR ENTER THE NUMBER OF YEARS TO INCREMENT => READ AGE IF (&AGE LT 0) OR (&AGE GT 999) THEN + DO WRITE YEARS TO INCREMENT IS INVALID, TRY AGAIN GOTO CI!KYEAR END &IlDSN.. Y2K&AGE WILL BE CREATED/REPLACED BY THIS JOB CSOS CHAR (K) &STR(/*JOBPAm() 1.=99,7=(0,20),HOID=ALL STEPCAMS EXEC PGM=IDCAMS SYSPRINT DD SYS~ SYSIN DD * &STR ( DELETE) &INDSN. Y2K&AGE PURGE llsas I/WORK llsaslist PDA PDADUT EXEC SASV6,OPTIONS=SYSPARH=&AGE DD SPACE=(6144,(10000,5000) ",ROUND) DD SYSOUT=A DD DS_&INDSN, PDA STRIP FILE DISP=SBR DD DS_&INDSN.. Y2K&AGE, AGED PDA STRIP FILE DISP=(,~TLG,DELETE),UNIT=SYSD@, LlIBEL=RETPD=365, DCB=(RECFH=FB,LRECL=320iBLKSIZ~0), SPACE=(320,(50,20),RLSE), AVGREC=K PRINT DD SYSOUT-~ $ORTPAm( DD * NOLIST *****SYSIN SPECIFIES THE ~TION OF THE UTILITY ********** SYSIN DD DSN=ACS5.SAS.SOURCE(AGEK102), FINIS DISP=SBR Figure 1 - CUST and JCL that invokes the "Incrementing Year Fields" utility_ 67

4 /********************************************************************* PROGRAM trumbl!r : NONE PROGRAM NAME : ACS5.SAS.SOURCE(AGEKl02) INCREMENTING YEAR FIELDS IN FLAT FILES TO TEST YEAR 2000 COMPLIANCE PROGlU>MMER NAKE : BRIAN K. BOWIBR DATE PROGRlIM WRI'l"l'EN: 06/06/97 FUNCTION/BRIEF DESCRIPTION : MACBINE-REMllIBLE RECORD LAYOUT (S) : NONE PARAMETERS PASSED TO THIS PROGRlIM trumbl!r OF YEARS TO AGE PASSED OSING SYSPARM INPUT FILES (INCLUDE DDNAMES) : FDA PDAE.K102.A FORMAT FILE OUTPUT FILES (INCLUDE DDNAKES) : PDAOOT PDAE.K102.A FORMAT FILE EXTERNAL SUBROUTINES CALLED (NAME - FUNCTION) NONE RETOlUI CODES 0'1'BR THAN ZERO (AND INTBRPRETATION) : NONE REVISION DATE : MH/DD/U REVISION REASON/DESCRIPTION REVISOR NAME : *********************************************************************/ OPTIONS SOURCE /* PRINTS THE PROGRAM STATEMENTS TO THE LOG */ PAGENO=l /* SETS FIRST PAGE trumbl!r TO 1 */ LS=79 /* SETS CHARACTERS PER PRINTED LINE */ PS=60; /* SETS LINES PBR PRINTED PAGE */ 'LET AGE=&SYSPARM; 'LET FOOT1-PROGRAM ACS5.SAS.SOORCE(AGEK102); 'LET YR VARS = PEFFYR PEXPYR TEFFYR DEFFYR DEXPYR ENTYR INCPYR CYCYR PEFFYRER PEXPYRER TEFFYRER DEFFYRER DEXPYRER ENTYRER INCPYRER CYCYRER DATA ERRORS /VIEW=ERRORS ; INFILE FDA ; FILE @ BLOCKl $200. BL0CK2 $120. PEFFYR $2. PEXPYR $2. TEFFYR $2. DEFFYR $2. DEXPYR $2. ENTYR $2. INCPYR $2. CYCYR $1. Figure 2a - "Incrementing Year Fields" SAS Source Statements (part 1) 68

5 I************.****ft** ft** 'It **** ft ** *. **** I /* CREATE ARRAYS FOR YEAR AND ERROR VARIABLES **/ 1********* *** *********** *** / ARRAY YR_VARS(*) &YR_VARS 1**** **** * * * * ** * * _*** */ '* CHECK AND INCREMl!NT ALL FIELDS IN ARRAY ** / /**.*************************** *************/ DO 1=1 TO DIM(YR_VARS) ; ERR VARS(I)=O; *** -DETERMINE IF TIlE YEAR FIELDS HAVE VALID NUMBERS **; DO J=1 TO LENGTH (YR VARS (I) ) ; IF INDEXC(SllBSTR(YR VARS(I),J,1), ' ') = 0 TIlEN ERR_VARS(I) = 1; 2ND; *** IF TIlE FIELD BAS ALL~, INCREMENT TIlE FIELD ***; IF ERR VARS(I) = 0 TIlEN DO; 'LET MDDYEAR = MOD(YR_~(I) + &AGE,10**LENGTH(YR_VARS(I»); **. LEADING ZERO FOR YURS 01., 02, 03, 2TC. ***; 'LET PADYEAR = COMFRESS (, 0 ' I I &MODYEAR); *** PUT TIlE COMPUTED YEAR BACK IN TIlE ORIGINAL FIELD *; YR_VARS(I)= SUBSTR(&PADYEAR, LENGTB(&PADYEAR)-LENGTH(YR VARS(I»+1, LENGTB(YR_VARS(I»); - END; END, /********* * ***********.************/ /* OUTPUT THE AGED RECORD TO TIlE FILE **/ 1* ******* * * *** * * * */ BLClCXl. BLOCK2 PEFFYR PEXPYR TEFFYR DEFFYR DEXPYR ENTYR $2. "@238 INCPYR CYCYR $1. PROC SUMMARY DATA=ERRORS Nll'AY MISSING PRINT SCM N MAXDEC=O; VAR &ERR VARS; TITLE1 'DAiE FIELDS NOT INCREMENTED' ; TITLE2 'SUIF OMBER OF RECORDS WITH NON-NtlMERIC VALtlES' ; TITLES 'N= TOTAL OMBER OF RECORDS IN INPUT FILE'; FOOTNOTEl "&FOO'l'l. " ; RUN ;ENDSAS; Figure 2b - "Incrementing Year Fields" SAS Source Statements (part 2) 69