The SUMMARY procedure, among others, will also provide univariate summary statistics. proc summary data=have; class gvkey year; var variable; output out=summry /autoname; run; ... View more

It is always fun to meet those that read and use the SAS Press books.  If you are at SAS Global Forum or PharmaSUG this spring look me up.  I would be very happy to meet and talk with you and to of course sign your book. ... View more

Aside from the problem of evaluating non integers with the implied %EVAL.  The macro language does not evaluate compound expressions in the same way as in the DATA step. In the DATA step if 5 < x < 10 is evaluaged as if 5 < x and x < 10 In the macro language %if 5 < &x < 10 is evaluated as %if (5 < &x) < 10 Regardless of the value of &X this expression is true as both 0 and 1 are less than 10. In the macro language always break up compound expressions. %if 5 < &x and &x < 10 %then .... ... View more

Is the data set used to generate a report?  if so you could probably create the totals using REPORT in the same step as the report is generated. ... View more

Have you tried looking at &SYSRC or the SYSMSG function?  something like the following untested code. %macro tryit; %let dsid = %sysfunc(open(work.a)); %if not &dsid %then %do;    %put %sysfunc(sysmsg());    %put &sysrc;  %end; %if &dsid %then %let rc = %sysfunc(close(&dsid)); %mend tryit; %tryit ... View more

I experimented and here is a work around.  There is probably/must be a better way. 1.  surround the code that has the %INCLUDE with a dummy macro This code will also have your PROC SCAPROC steps. %macro doit; ..... some code .... %include yourcode; . . . . . other code . . . . %mend doit; 2. Turn on the MFILE system option and create a MPRINT fileref filename mprint 'somefile.sas'; options mprint mfile; 3. execute the macro %doit 4. reexecute the file generated by the MFILE option (SOMEFILE.SAS).  This code will have no macro language references and the %INCLUDEs will have been executed.  This means that the SCAPROC will do what you want. ... View more

Thank you for your patience, I believe that I now understand.  While I have only a passing understanding of this procedure, I believe that neither macro language elements or (apparently) iincluded code is passed to the Code Analyzer.  Perhaps someone who has a better understanding of this procedure will join the conversation.  I did not find any options that changed this behavior. Perhaps there is an alternate approach to the problem.  What specifically are you trying to get from the procedure?  A list of steps? ... View more

The results of most procedures are not written to the LOG, but are written to an output destination, such as the OUTPUT window.  Are you saying that the your program is not working or that the SCAPROC procedure is not showing all of the steps in your program? ... View more

Then I do not understand the issue.  The SOURCE2 option should surface code that is included from within a macro.  What do you mean that the SCAPROC treats the included file as a single unit of work?  Is it not shown in the LOG? Are you not seeing the execution notes? ... View more

Have you turned on the SOURCE2 system option?  This option allows the display of included source code in the LOG. ... View more

The following test worked for me: proc format ; value gender 0='Male' 1='Female'; run; data havenum; sex=1; date=today();output; format sex gender. date date9.; run; filename table 'c:\temp\table.out' lrecl=120; ods listing; proc printto print=table new; proc print data=havenum; run; proc printto; run; Notice that, like DATA _NULL_ suggested, the LISTING destination MUST be turned on before the PRINTTO can write to the PRINT location.  The LISTING destination is by default turned off for SAS9.3. The fix for Astounding's comment for detecting versions is to use a %SYSEVALF to surround the expression. %if %sysevalf(&sysver > 6.10) %then %do; ... View more