Industry Applications

Transcription

1 IMPLEMENTING ABEllA VIOR SCORE MODEL USING A SAS TO COBOL TRANSLATOR by David A. Wolovick Statistical models are used to predict behavior. They assign scores to individual customers or accounts which reflect the probabilities calculated by the model. The development of a scoring model begins with an attempt to identify any data elements which could be useful in predicting future behavior. Relationships between the data elements, called, are constructed. In some cases the data element itself is a characteristic. More often, though, it is a simple mathematical formula using one or several data elements, a statistical (SAS) :function, such as MEAN or MAX, or a unique algorithm. A characteristic resolves to a value. Accounts with similar profiles or patterns of behavior are grouped together into the same &oneard. Each scorecard has a unique set of Attributes. An Attribute is the number of points assigned to a range of values. That is, the same characteristic with the same value may result in a different number of points in a different scorecard. The sum of the attributes is the score. SAS is the language often used for developing and validating Behavior Score Models. COBOL is the language of the Production Systems, the Posting and Billing streams where the scores will actually be calculated on live accounts. Traditionally, the model developers provide written documentation or specifications to the COBOL programmers and analysts. There are several problems with that approach: Misunderstandings are inevitable when the definitions and logic of one computer language is translated into English and then retranslated into another computer language. After the design phase, the actual coding of any program is a tedious clerical task, prone to error. With Scoring models, the number of values, ranges, etc., which need to be hardcoded is staggering. Incremental development is generally not supported. That is, until all the Scorecards are provided, coding and testing will not begin. The SAS-to-COBOL Translator is an attempt to address those issues, so that the time required to implement a new set of Scorecards can be decreased dramatically. The purpose of the SAS-ta-COBOL translator is not to produce a complete COBOL program; it is assumed that a COBOL scoring module already exists or that a "skeleton" is being written. Changes to the translator may have to be made to conform to particular data names used in that module. The translator creates four output :files. After the Production COBOL scoring program has been modified to disable the old scoring routines (if they exist), it must be recompiled with these files "copied" or "included". The Data Division of a COBOL program is where the variables are declared. Two of the four files are Data Division entries. General working or temporary fields are declared in one file. Also all the characteristics are declared. The same characteristic may be used in several scorecards, but it must only be declared once. The unique combinations of characteristic and scorecard are declared in the other file. For each characteristic within each scorecard, there are ranges ofvalues with corresponding attributes. Calculations are done in the Procedure Division of a COBOL program. The other two files are Procedure Division entries. In one file each characteristic has a separate paragraph or routine where its value is calculated. The other file is essentially a very large "Evaluate" statement (equivalent to the "Select" in SAS) based upon the scorecard. The value of each characteristic associated with that scorecard is calculated. The result is then compared to the ranges declared for the particular scorecardcharacteristic combination to get the attribute. All the attributes are then added to get the score. SCORE DEVELOPMENT CODE AS INPUT DATA The SAS code used to developlvalidate the behavior scores is input data. There are three types of code and for each there were structural/syntactical assumptions made. Extract Data Elements. This code reads the Production Master:file(s) and creates test data. The requirement here is that absolute pointer controls be used in the Input statement, that there be only one per line and that only :five different Informats be used: SCHARw., Sw., w.d, Pdw.d and HEXw.. Each Characteristic must be defined in a Macro (with the Macro name as the Characteristic name) and each Macro must be in its own separate file. If comments are desired in the 336

2 COBOL code, they may be put in o/os1r functions within %LET statements. SAS Statements may be on multiple lines but there may not be multiple SAS statements on one line (parsing stops when the first semicolon is found). There can be up to 8 SAS functions in one statement; iflelse clauses are supported as long as the else clause does not contain a SAS function. Also not supported are arrays and temporary fields. Any unsupported features. including date transfonnations, can be handled by adding ad-hoc translation code to the SPECIAL Macro. Scorecards and Attributes. Each Scorecard must be defined in its own separate file, which is in fact an executable SAS job. In that job the relevant Macros are invoked, PROC FORMAT is used to assign Attribute values and a series of PUT functions are used to link the two. The Partitioned Data Set (PDS) where the Characteristic Macro is located (but not the member name) must be defined in the JCL. The actual member names must be identified in %INCLUDE statements (multiple members for one PDS can be referenced). In PROC FORMAT there must be only one transformation value per line. Examples: Extract CORP ASA ACCNUM A I CLOST D-CLOST D-PLOST D-MEM A PD4. *TCHAROl FIRST TEST CHARACTERISTIC ; %MACRO TCHAR01; IF RANGE(A DUES,A DUE4,A DUE3) GT 3.3 THEN TCHAROl = - - MEAN(OF A DUE1-A DUES) + (MAX(N 60LT,N SOLT) + FLOOR(RSCORE All; ELSE TCHAR01=-777; - %LET MCTITLE1=%STR ( 'TEST RANGE MEAN FLOOR MIN ' ) ; %LET MCTITLE2=%STR ('SECOND LINE OF COMMENT'); %LET MCTITLE3=%STR(' '); %MEND ; Scorecards and Attributes II EXEC SAS608 IISYSPRINT DD SYSOUT=* IITPDSl DD DSN=$SUPDXW.SCORE.DATA,DISP=SHR I/TPDS2 DD DSN=SUPDXW.MVS.DATA,DISP=SHR ** * *INCLUDE THE MACROS TO CALCULATE CHARACTERISTICS; %INCLUDE TPDS1(TCHAROl TCHAR02 TCHAR07) ; %INCLUDE TPDS2(TCHAR03); ** FORMAT STMT ASSIGNS WEIGHTS TO ATTRIBUTES FOR THE CHARACTERISTICS; PROC FORMAT; VALUE FTCHAROl LOW - 0 = 18 o < <-.6 = 11.6 <-.8 = 11.8 <-.9 = 12.9 <- HIGH = 24 OTHER = 18; VALUE FTCHAR02 LOW = 9 ITCHAROl ITCHAR02 ITCHAR03 ITCHAR <- 0 = -4 o <- 100 = <- 150 = 6 = PUT(TCHAR01,FTCHAR01.); = PUT(TCHAR02,FTCHAR02.); = PUT(TCHAR03,FTCHAR03.); = PUT(TCHAR07,FTCHAR07.); 337

3 Implementing a Behavior Score Model Using a SAS to COBOL Translator Page 1 of 4 Layout of Production Data as SAS Dataset SAS: Extract Data Elements XTR: SAS-COBOL variable name xref Manual Adjustment and Reconciliation Duplicates, Discrepancies and No-matches Score Development TRANCOB: Generated xref Macro SAS: SAS: Scorecards and Attributes Legend Execution Generated Used As Data wolovick@aol.com 338

4 Implementing a Behavior Score Model Using a SAS to COBOL Translator Indust~II~:afi~ns R'un each time a new Scorecard is ready Input data is cumulative list of Scorecards. Yes Scorecard IDs and Location of SAS code Allocate space for 5 output files Set up Macro for JObcard. PDS and File Names ATTRIB: Scorecards as Parameter List MVSJCL: Jobcard. PDS and File Names START: Generate JCL and Macro for Next Job Legend execution Generated wolovick@aol.com 339

5 Implementing a Behavior Score Model Page 3 of 4 Using a SAS to COBOL Translator MVSJCL: Jobcard, PDS and File Names ATTRMACR: Undupe and Generate JCL SAS : Scorecards and Attributes ATTR: Process SAS code for Scorecards and Attributes and Value Ranges; New flagged I--ot( COBOL : Calculation of Variables in Procedure Division COBOL :,Ranges of Values Declared in Data Division Legend Execution Generated JCL COBOL : Evaluate Statement in Procedure Division Generated wolovick@aol.com Used As Data 340

6 Implementing a Behavior Score Model Using a SAS to COBOL Translator Industry Applications Page 4 of 4 SAS: Flat File of ; One line per SAS statement and Value Ranges; New flagged TRANCOB: Generated xref Macro CHAR: Process SAS for FUNCS: Macro to Translate SAS Functions Yes Add code to SPECIAL Legend COBOL CODE: Variables Declared in Data Division Execution, Generated COBOLCo<1e: Calculation of Variables in Procedure Division SPECIAL: Macro to Translate Non Standard Used As Data 341 wolovick@aol,com

7 STEP! The purpose of the first step is to create a Cross Reference Macro of SAS data-names to COBOL datanames. It is assumed that there exists or that you can easily create the COBOL file layout as a SAS Dataset XIR reads in that dataset and, using Starting Position and Field Size as the match key, merges it with the SAS code which extracted the data. What is produced is TRANCOB. a cross-reference Macro, essentially a series oftranwrd functions. After reviewing the reports which also are produced by the SAS run, manual adjustments may have to be made to the Cross-Reference. STEP 2 SAS statement flatfile. Step 2 creates JCL to run Step 3 and Step 3 creates JCL to run Step 4. MVs.JCL is a Macro called in both of these steps which sets up the Jobcard, PDS and file names. START reads in a flat file listing of Scorecards and their respective file names. It generates JCL and ATTRIB, a file of SAS code (3 Macros, each with the Scorecards as the list of arguments). These Macros are called in the next step by Macros with the P ARMBUFF option, which allows a different number of arguments each time it is invoked. Each time a new Scorecard is ready, Step 2 is run, taking as its input the cumulative list of Scorecards. Step 2 is the beginning of the iterative process in which Scorecards are translated as they are ready. The first time that it is run, space must be allocated for the four SO-byte COBOL flatfile outputs plus the one 200-byte -----Alphabetic List of Variables and Attributes----- # Variable Type Len Pos COBNAME Char COBTYPE Char DECIMALS Num SIZE Num START Num Sort Information----- Sortedby: START SIZE validated: YES Character Set: EBCDIC %MACRO TRANCOB; COBL1NE=TRANWRD(COBL1NE,'SASNAME2','PROD-COBOL-NAME-2'); COBLINE=TRANWRD(COBLINE,'SASNAMEl','PROD-COBOL-NAME-1'); %MEND TRANCOB; %MACRO ATTR1BX (X)/PARMBUFF; %LET STOP=%LENGTH(&SYSPBUFF); %DO 1=1 %TO &STOP; %LET SCARD=%SCAN(&SYSPBUFF,&I); %IF &SCARD NE %THEN %DO; %ATTRIB (&SCARD) % %ELSE %LET I=&STOP; %END %M %MACRO ATTRIB (SCARD); DATA FMAT&SCARD (KEEP=FMAT FORMTYPE HIBOUND ATTR) XREF&SCARD (KEEP=FMAT CHAR) JCL1&SCARD (KEEP=PDS SYMB) JCL2&SCARD (KEEP=MEMB SYMB); * FORMTYPE O=VALID l=default(other) ; LENGTH ATTR HIBOUND $14 ; INFILE F&SCARD; FULLINE $72.; 342

8 Generated Fi1es ****** ***************************** TOP OF DATA ** (ATTRIB) %ATTRIBX (127, , ) DATA JCL; SET 0000 %JCLNUMX (127, , ) PROC SORT NODUPKEY; BY MEMB; %JCLNULL DATA COBOL; SET %SORTNUMX (127, , ) ****** **************************** BOTTOM OF DATA ****** ***************************** TOP OF DATA **** (JCL) //$SUPDXWJ JOB (CSROID,JMM),'SCORE',MSGCLASS=X,CLASS=S,REGION=OM //SAS EXEC SAS //PROCDIV2 DD DSN=$SUPDXW.SCORE.COBOL.PROCDIV2,DISP=SHR //PROCDIV1 DD DSN=$SUPDXW.SCORE.COBOL.PROCDIV1,DISP=SHR 0000 //DATADIV1 DD DSN=$SUPDXW.SCORE.COBOL.DATADIV1,DISP=SHR //JCL DD DSN=$SUPDXW.MVS.CNTL(SCOREXE2),DISP=SHR //MACR DD DSN=$SUPDXW.SCORE.DATA,DISP=SHR //SYSIN DD DSN=$SUPDXW.SCORE.DATA(ATTR),DISP=SHR //F127 DD DSN=WCMKCH.SCORING.DATA(SCORE7),DISP=SHR //F500 DD DSN=$SUPDXW.MVS.CNTL(SCORE500),DISP=SHR //F031 DD DSN=$SUPD~.MVS.CNTL(SCORE031),DISP=SHR ****** **************************** BOTTOM OF DATA ********************* STEP 3 The input to Step 3 is the SAS code which we are translating, here the Scorecards and Attributes. They will become the COBOL code where the ranges of values and their associated point totals (per Scorecard) are declared. Also, the "Evaluate" statement is created, which tells the COBOL progmm which need to be calculated for each Scorecard. ATTRMACR defines the three Macros with the P ARMBUFF option, each of which loops and executes another Macro for each argument (Scorecard). The first one reads the Scorecard file and produces two temporary SAS Datasets. One, with the PDS and member name for each Characteristic, is created by match-merging parsed extracts from the JCL with parsed extracts from the %INCLUDE statements. The other, with the Characteristic name, attribute and value of the high end of the range, is created by a similar match-merge of parsed data, this time from the Value statements in PROC FORU4Tandfrom the PUTfunction statements. The other two Macros concatenate these two outputs. A TTR reads the concatenated data and match-merges it with one of the COBOL flat files to produce a printout, where which have not been defined yet are flagged. Also output are two other COBOL flat files and the JCL for the next step. STEP 4 Step 4 translates the SAS code where the are defined. Generally, they will be in the form of iflthen statements with one or several SAS statistical functions. However, before proceeding, the SAS statements flagged as "new" in the Step 3 printout should be examined to see if they are "non-standard", i.e., they contain anays, temporary variable names, date variables, etc. If so, ad hoc code has to be added to the SPECIAL Macro. CHAR reads in the Score Development SAS Macros where the calculations are defined. Multiline SAS statements are concatenated. SPECIAL is invoked to bypass designated, whose translation is being done by ad hoc code within that Macro. Otherwise, each SAS statement is parsed, the SAS functions being translated by the FUNCS Macro. The TRANCOB Macro (the variable name crossreference) is also invoked. 343

9 portion of CHAR * IDENTIFY AND CONVERT SAS FUNCTIONS ADD EQUAL SIGN TO LIST OF SCAN DELIMITERS; %LET DELIMS=%STR('.«+&*);-1,='); END IDX=O; DO 1=1 TO 100 WHILE (SCAN (FULLINE,I,&DELIMS) NOT =, ') FUNCWORD=SCAN(FULLINE,I,&DELIMS); IE' FUNCWORD IN{'MIN','MAX', 'SUM', 'MEAN', 'RANGE', 'MOD', 'INT', 'CEIL', 'FLOOR') THEN DO; * DETERMINE STARTING AND ENDING DISPLACEMENTS; START = END_lOX +. INDEX(SUBSTR(FULLINE,END IDX+1),TRIM(FUNCWORD»; END IDX = START + - INDEX(SUBSTR(FULLINE,START),')') - 1; * DETERMINE NUMBER OF VARIABLES IN FUNCTION; VX=START; DO V = 1 TO 100 ; WORD=SCAN(SUBSTR(FULLINE,START), V, &DELIMS) ; VX=VX+ INDEX(SUBSTR(FULLINE,START),TRIM(WORD»; IF WORD=', OR VX > END_lOX THEN DO; VARNUM=V; - V=lOO; * THE SAS FUNCTION RESOLVES TO A COBOL VARIABLE SAB-TOTAL', WHERE H REFERS TO A UNIQUE SEQUENCE NUMBER ASSIGNED TO EACH SAS FUNCTION IS MAX) USED IN CALCULATING THE CHARACTERISTIC; FUNCCONV+1; SE~INPUTIPUTIFUNCCONV,I.),$I.); %FUNC1 REPL=' FCNV' I I SEQ; LFUNC = END lox - START + 1; SUBSTR(FULLINE,START,LFUNC)=REPL; f* SAS FUNCTION FOUND *1 f* END OF LINE PARSING TO FIND SAS FUNCTIONS * 1 IF CHARFLAG=1 THEN DO; FIRSTLIN=O; CHARFLAG=O; 1 *'; FIRSTLIN+l; LENGTH OPERATOR $1 ; ARRAY OPS (14) $4 (I ( _,, I '+ _ I 1/ _ 1* _ I t~ _ I,> _ I '<_ 1(+"_+'1++1'/+' _* + I '= + I I> + I '< + ') DO 1=2 TO 7; 1* MAKE OPERATOR A WORD *1 OPERATOR=SUBSTRIOPS{I),I,I); OPWORD=' 'IIOPERATORII' '; FULLINE=TRANWRDIFULLINE,OPERATOR,OPWORD); FULLINE=TRANWRDIFULLINE,') ',') '); FULLINE=COMPBL(FULLINE); DO 1=1 TO 14; /* CORRECT FOR + OR - AS SIGN NOT OPERATOR *f FULLINE=TRANWRDIFULLINE,OPS{I}, SUBSTR(OPS{I},1,3»; FULLINE=TRANWRDIFULLINE,'( ','I'); FULLINE-TRANWRDIFULLINE,' )',')'); FULLINE=TRANWRDIFULLINE,'> =','>='); FULLINE=TRANWRDIFULLINE,'< =','<='); FULLINE=TRANWRD(FULLINE,'FCNV','SAS-TOTAL'); WORD='SAS-' IICHARNAME; FULLINE=TRANWRD(FULLINE,TRIM(CHARNAME), TRIM (WORD) ); Portion of I!'UNCS IF SCAN(SUBSTR(FULLINE,START),2) = 'OF' THEN DO; FNAME2=SCAN(SUBSTR(FULLINE,START),3); FNAME3=SCANISUBSTR(FULLINE,START),4); L2=LENGTH(FNAME2);. L3=LENGTH(FNAME3); * DETERMINE ROOT AND SUBSCRIPT ; %LET NUMERICS = tstr ( 10 ', '1', 2', '3 I, '4 I, '5 I I 16' I ';,, 'e t,, 9' ) ; IF SUBSTR(FNAME2,L2-1,1) IN (&NUMERICS) > 0 THEN DO; VALl=SUBSTR(FNAME2,L2-1,2); FNAMEO=SUBSTR(FNAME2,I,LZ-Z); ELSE DO; VALl=SUBSTR(FNAMEZ,LZ,1); FNAMEO=SUBSTR(FNAME2,1,L2-1); IF SUBSTR(FNAME3,L3-1,1) IN(&NUMERICS) > 0 THEN VAL2=SUBSTR(FNAME3,L3-1,2); ELSE VAL2=SUBSTRIFNAME3,L3,1): COBLINE='PERFORM VARYING SAS-SUB,ROM 'II COBOL Data Div:L.ion (1) 01 SAS-TCHAR PIC S9(S)V9(4) VALUE +.5. PIC S9(S)V9(4) VALUE +11. PIC S9(S)V9(4) VALUE +.6. PIC S9(S)V9(4) VALUE +11. PIC S9(S)V9(4) VALUE +.S. PIC S9(S)V9(4) VALUE +11. PIC S9(5)V9(4) VALUE +.9. PIC S9(S)V9(4) VALUE +12. PIC S9(S)V9(4) VALUE +0. PIC S9(S)V9(4) VALUE +1S. PIC S9(S)V9(4) VALUE PIC S9(S)V9(4) VALUE +24. PIC S9(S)V9(4) VALUE REDEFINES SAS-TCHAROI-201. SAS-TCHAR01-Z01-TBL OCCURS 6 INDEXED BY SAS-TCHAROl-201-SUB. 10 SAS-TCHAR MAX PIC S9(5)V9(4). 10 SAS-TCHAR01-Z01-ATTR PIC S9(5)V9(4). SAS-TCHAR01-Z01-OTHER PIC S9(S)V9(4). 01 SAS-TCHAR02-Z01. COBOL Data Div:L.ion (2) ********** SAg WORKING STORAGE VARIABLES ***** 01 SAS-TOTALO PIC S9(S)V9(4). 01 SAS-TOTALR REDEFINES SAS-TOTALO. SAS-INTEGER PIC S9(S). SAS-DECIMAL PIC 9(4). 01 SAS-TOTALS. 01 SAS-TOTAL1 SAS-TOTAL2 SAS-TOTAL3 SAS-TOTAL4 SAS-TOTALS SAS-TOTAL6 SAS-TOTAL7 SAS-TOTAL8 REDEFINES SAS-TOTALS. SAS-TOTALX OCCURS 8 PIC S9(S)V9(4). PIC S9(S)V9(4). PIC S9(5)V9(4). PIC S9(5)V9(4). PIC S9(S)V9(4). PIC S9(5)V9(4). PIC S9(5)V9(4). PIC S9(5)V9(4). PICXI9). 344

10 01 SAS-SUB PIC S9(4). 01 SAS-DATE PIC 9 (6). 01 REDEFINES SAS-DATE. SAS- -YMD PIC 99. SAS-MM-YMD PIC 99. SAS-DD- MD PIC REDEFINES SAS-DATE. SAS-MM-MD PIC 99. SAS-DD-MDY PIC 99. SAS- Y-MDY PIC 99. SAS CHARACTERISTICS *************** 01 SAS-CHAR-AREA. SAS-TCHAR01 PIC S9(s)V9(4) COMP-3. SAS-TCHAR02 PIC S9(S)V9(4) COMP-3. SAS-TCHAR03 PIC S9 (5)V9 (4) COMP-3. SAS-TCHAR07 PIC S9(5)V9(4) COMP-3. COBOL Procedure DiVision (1) MOVE ZERO TO FI-RAW-SCORE (1) MOVE SPACES TO SAS-CHAR-AREA EVALUATE FI-SCRD-ID (1) WHEN 201 TCHAR01 SCORECARD 201 PERFORM SAS-TCHAR01-ROUTINE IF SAS-TCHAR01 NOT NUMERIC ADD SAS-TCHAROl-201-OTHER TO FI-RAW-SCORE (1) ELSE SEARCH SAS-TCHAROl-201-TBL VARYING SAS-TCHAROl-20l-SUB AT END ADD SAS-TCHAROl-20l-OTHER TO FI-RAW-SCORE (1) WHEN SAS-TCHAROl-201-MAX (SAS-TCHAROl-201-SUB) >= SAS-TCHAR01 ADD SAS-TCHAROl-201-ATTR (SAS-TCHAROl-201-SUBI TO FI-RAW-SCORE (1) END-SEARCH TCHAR02 SCORECARD 201 COBOL Procedure DiVision (2) SAS-TCHAR01-ROUTINE. TEST RANGE MEAN FLOOR MIN * SECOND LINE OF COMMENT CONVERT SAS RANGE FUNCTION MOVE SPACES TO SAS-TOTALR MOVE SPACES TO SAS-TOTALX (1) IF BCM-BAL-HIST-AMT-DUE(51 NUMERIC IF SAS-TOTAL1 NOT NUMERIC OR BCM-BAL-HIST-AMT-DUE(s) > SAS-TOTAL1 MOVE BCM-BAL-HIST-AMT-DUE(s) TO SAS-TOTALl IF SAS-TOTALO NOT NUMERIC OR BCM-BAL-HIST-AMT-DUE(s) < SAS-TOTALD MOVE BCM-BAL-HIST-AMT-DUE(SI TO SAS-TOTALO IF BCM-BAL-HIST-AMT-DUE(4) NUMERIC IF SAS-TOTAL1 NOT NUMERIC OR BCM-BAL-HIST-AMT-DUE(4) > SAS-TOTALl MOVE BCM-BAL-HIST-~-DUE(4) TO SAS-TOTALl IF SAS-TOTALO NOT NUMERIC OR BCM-BAL-HIST-AMT-DUE (4) < SAS-TOTALO MOVE BCM-BAL-HIST-AM!-DUE(4) TO SAS-TOTALO IF BCM-BAL-HIST-AMT-DUE(3) NUMERIC IF SAS-TOTAL1 NOT NUMERIC OR BCM-BAL-HIST-AMT-DUE(3) > SAS~TOTAL1 MOVE BCM-BAL-HIST-AMT-DUE(3) TO SAS-TOTALl IF SAS-TOTALO NOT NUMERIC OR BCM-BAL-HIST-AMT-DUE(3) < SAS-TOTALO MOVE BCM-BAL-HIST-AM!-DUE(3) TO SAS-TOTALO IF SAS-TOTALO NUMERIC COMPUTE SAS-TOTAL1 = SAS-TOTALl - SA5-TOTALO CONVERT SAS MEAN FUNCTION MOVE ZERO TO SA5-TOTALO MOVE SPACES TO SAS-TOTALX (2) PERFORM VARYING SAS-SUB FROM 1 BY 1 UNTIL SAS-SUB >= 5 IF BCM-BAL-HIST-AMT-DUE (SAS-SUB) NUMERIC IF SAS-TOTAL2 NOT NUMERIC MOVE BCM-BAL-HIST-AMT-DUE (SAS-SUB) TO SAS-TOTAL2 ELSE ADD BCM-BAL-HIST-AMT-DUE (SAS-SUB) TO SAS-TOTAL2 ADD 1 TO SAS-TOTALO END-PERFORM IF SAS-TOTALO > ZERO COMPUTE SAS-TOTAL2 = SAS-TOTAL2 / SAS-TOTALO CONVERT SAS MAX FUNCTION MOVE SPACES TO SAS-TOTALX (3) IF BCM-TIMES-60 NUMERIC IF SAS-TOTAL3 NOT NUMERIC OR BCM-TIMES-60 > SA5-TOTAL3 MOVE BCM-TIMES-60 TO SAS-TOTAL3 IF BCM-TIMES-50 NUMERIC IF SAS-TOTAL3 NOT NUMERIC OR BCM-TIMES-SO > SAS-TOTAL3 MOVE BCM-TIMES-sO TO SAS-TOTAL3 CONVERT SAS FLOOR FUNCTION MOVE BCM-RAW-SCORE(l) TO SAS-TOTALO IF SAS-INTEGER > SCM-RAW-SCORE(l) COMPUTE SA5-TOTAL4 = SAS-INTEGER - 1 ELSE MOVE SAS-INTEGER TO SAS-T0TAL4 IF SAS-TOTAL1 > 3.3 COMPUTE SAS-TCHAROl = SAS-TOTAL2 + (SAS-TOTAL3 + SAS-TOTAL4) ELSE COMPUTE SAS-TCHAROl