Snipplr - sarathannapareddy

(SAS) CALL EXECUTE: Easy way to print or sort multiple files.

Mon, 26 Apr 2010 19:42:48 GMT

When printing multiple files, or sorting multiple datasets, the traditional method is to write multiple steps as below. Proc print data=libref.ae; var _all_; run; Proc print data=libref.conmed; var _all_; run; Proc print data=libref.demog; var _all_; run; Proc print data=libref.lab; var _all_; run; Proc print data=libref.medhist; var _all_; run; If you are like me who likes to simplify the traditional SAS code here is the tip. CALL EXECUTE comes to rescue here.

(SAS) Finding the number of observations in the Dataset

Tue, 11 Aug 2009 16:22:13 GMT

There are a number of ways of finding out the number of observations in a SAS data set and, while they are documented in a number of different places, I have decided to collect them together in one place. At the very least, it means that I can find them again. Read more at: http://studysas.blogspot.com/2008/08/finding-number-of-observations-in-sas.html

(SAS) Call Sumput vs Call SymputX

Tue, 11 Aug 2009 16:15:40 GMT

Call Symput: Use CALL SYMPUT is you need to assign a data step value to a macro variable. Syntax: Call Symput (“Macro variable”, character value) The first argument to the Symput routine is the name of the macro variable to be assigned to the value from the second argument.

(SAS) Renaming All variables in the SAS dataset using SASHELP VIEWS/DICTIONARY.tables

Thu, 30 Jul 2009 13:12:57 GMT

We can rename all the variables in the dataset using the SASHELP views or Dictionary.Tables... I.e SAS metadata... here is how....

(SAS) maxvarlen_macro: Check the Length of all character variables length is LT 200

Sun, 07 Jun 2009 22:25:04 GMT

(SAS) Retrieve the path name and filename of executing program ... programmatically

Tue, 07 Apr 2009 13:09:15 GMT

Oftentimes, I was asked to keep the name and path of the executing program in the FOOTNOTE of the generated table or listings. I have always created a macro variable using the %let statement and, then I called the Macro variable in the footnote statement to get the name of the program. Eventhough it is simple.. it may not be suitable when we write application which need to self document... Here is another technique which can be used to retrieve the pathname and filename (last executed) ..... To get the last opened filename: proc sql noprint; select scan(xpath,-1,'\') into :progname from sashelp.vextfl where upcase(xpath) like '%.SAS'; quit; %put &progname; read more.. at ...http://studysas.blogspot.com/2009/04/how-to-determine-executing-program-name.html

(SAS) Hoe to check if the variable exsits in the dataset or not

Tue, 07 Apr 2009 13:06:32 GMT

In SAS sometimes, we need to check whether the variable is exist in the dataset or not, we usually run the proc contents program and physically check if the variable exist in the dataset or not. If we want to check it programmatically, then use the following code.... Sample dataset:... data _null_; dset=open('old'); check=varnum(dset,'SCORE4'); call symput('chk',check); run; %put &chk;