I'm having issues with stating my informat on the input statment. If I just use an INFORMAT statement, it works and I get no errors/warnings. Does anybody know what the difference is in the following two statements?\   DATA work.DATA1; INFILE "&Lnx_File" DELIMITER=',' MISSOVER FIRSTOBS=2 DSD LRECL=32767; INPUT Policy_Number $ Incurred_Date Paid_Date Amount_Paid_per_Claim ; INFORMAT Incurred_Date YYMMDD8. Paid_Date YYMMDD8. ; FORMAT Policy_Number $9. Incurred_Date MMDDYY10. Paid_Date MMDDYY10. Amount_Paid_per_Claim 10.2 ; The below code seems to be not reading in the data correctly and I get a ton of warnings and notes.   DATA work.DATA1; INFILE "&Lnx_File" DELIMITER=',' MISSOVER FIRSTOBS=2 DSD LRECL=32767; INPUT Policy_Number $ Incurred_Date YYMMDD8. Paid_Date YYMMDD8. Amount_Paid_per_Claim ; FORMAT Policy_Number $9. Incurred_Date MMDDYY10. Paid_Date MMDDYY10. Amount_Paid_per_Claim 10.2 ; ... View more

I'm getting an error of Summary functions are restricted to the SELECT and HAVING ...   Is this because I can't group by a variable in the same statement that I create it in?       PROC SQL; CREATE TABLE work.counts AS SELECT Report_Month, CASE WHEN P = 'ACC' THEN 'A' WHEN P = 'DCL' AND S = 'ACC' THEN 'B' WHEN P = 'DLC' AND S = 'DLC' AND SS = 'ACC' THEN 'C' WHEN SS = 'DLC' THEN 'E' END AS Risk, COUNT(DISTINCT SSN) AS COUNT FROM work.Master GROUP BY Report_Month, Risk, Count; QUIT; ... View more

I figured out a problem I had today because I had nested macros what used macro do loops which both start i=0. Because the inner macro went all the way to 70, when the outside macro referenced i for it's second pass, it thought i was 70 so it didn't need to do another loop.   My question is how to use %LOCAL to stop this.   When using the local statement, do I need to refer to that variable as &i or &j? Is %LET &j= the right syntax or should it be &j.= %EVAL(&i.+1);   Thanks!   %LOCAL i j;   %DO &i.=0 %TO 70;   %LET &j = %EVAL(&i.+1);   ... View more

I don't understand why this isn't working. I want to sum up all the Qtrly_Paids for each Paid_Qtr. I know how to do this in proc sql but can't figure out why this isn't working in a data step.   DATA RDS_Final; RETAIN PAID_QTR QTR_Paids; SET work.RDS_Qtr_Pds(KEEP=Paid_Qtr Qtr_Paids); FORMAT Pd_Clm_From_Rds COMMA20.; BY Paid_Qtr; IF first.Paid_Qtr THEN Pd_Clm_From_Rds = 0; Pd_Clm_From_Rds + Qtr_Paids; DROP Qtr_Paids; RUN; ... View more

Anybody have some materials / advice on creating a program and how to structure it?   For example, I'm working on a program that is currently 600+ lines long and it might end up being 1000 when it is all said and done. It has various data steps, proc sqls, macros, etc. It creates 40+ tables, some temporary, some not. I still learning SAS and haven't really seen anything on structure a long process.   I've started creating user defined macros in the program to kind of help structure what that series of code is doing. Do people tend to do this? I've been thinking of going back and doing this for other steps that I didn't include in macros. Should I create a program for each one of these macros and then %INCLUDE them in a main program that calls them all and then runs the macros?   Any advice would be great!    Thanks, ... View more