About Tom

Tom · ‎07-27-2011

Why not just use the INTNX function that SAS already has?

Tom · ‎07-25-2011

Unless you use PROC FCMP to make a function you cannot call PROC CORR inside of a DATA STEP. Perhaps instead you want to transpose your "array" so that you can call PROC CORR with a BY statement?

Tom · ‎07-25-2011

CSV files are a little easier to deal with as you can just use normal input functions. This program will just read your two variables as character strings (VAR1 and VAR2), but you can just change the input statement to read them as dates or numbers and give them more meaningful names. The program counts the number of columns by reading the first line until it hits an empty string. Then in reads the next row into an array so that the names are available when reading the data. It does not output the empty cells. You might want to also not output the cells where the first variable is '#NA #NA' and the second is empty. You might want to add a PROC SORT to get the data back into a more reasonable order. filename in 'c:\downloads\Data.csv'; data out ; array names (5000) $20 _temporary_ ; length name $20 var1 var2 $20 ; infile in dsd lrecl=300000 truncover ; if _n_=1 then do ; do ncols=1 by 1 until(name=' '); input name @ ; end; input ; do i=1 to ncols/2 ; input name name @ ; names(i)=name; end; input ; end; do i=1 to ncols/2 ; input var1 var2 @ ; if not ( missing(var1) and missing(var2) ) then do ; name = names(i); output ; end; end; keep name var1 var2 ; retain ncols; run;

Tom · ‎07-25-2011

To change the length of a variable you need to create a new dataset. data new; length wb $6 ; set wbhat ; run; Do you really care if the DBF file has numeric or character variables? You could convert AGE to $1 using a PUT function call. data new; set wbhat (rename=(age = numeric_age) ); age = put(age,1.) ; drop numeric_age ; run; If you are more comfortable with SQL syntax then use PROC SQL. proc sql ; create table new as select wb as wb length=6 , put(age,1.) as age length=1 , put(mg,3.) as mg length=3 from wbhat ; quit;

Tom · ‎07-25-2011

You cannot use a FORMAT statement to change the length of the character variables. You can change the length by using a data step or proc sql statement to create the variable with a different length. You cannot change the 16 spaces that SAS uses to store the numeric fields. Here is the link to the SAS 9.2 documentation: http://support.sas.com/documentation/cdl/en/acpcref/63184/HTML/default/viewer.htm#a003087278.htm Converting SAS Variables to DBF Fields Numeric variables are stored in character form by DBF files. SAS numeric variables become numeric variables with a length of 16 when converted from a DBF file. SAS decimal values must be stored in a decimal format to be converted to a DBF decimal value. Associate the SAS numeric variable with an appropriate decimal format. The corresponding DBF field does not have any value to the right of the decimal point. You can associate a format with SAS variables when you create the data set or with the DATASETS procedure. If the number of digits including a possible decimal point exceeds 16, a warning message is issued and the DBF numeric field is filled with the character 9 . All SAS character variables become DBF fields of the same length. When you convert a SAS data set to a DBF file that is compatible with dBASE III or later, SAS date variables become DBF date fields. When you convert a SAS data set to a dBASE II file, SAS date variables become dBASE II character fields in the form YYYYMMDD.

Tom · ‎07-25-2011

What NOTEPAD are you using? Is the Windows program? If so then try using WORDPAD instead. If you do want to use PROC EXPORT to create two or more files look into the dataset options FIRSTOBS and OBS. proc export data=have(obs=10000) .... ; proc export data=have(firstobs=10001) .... ;

Tom · ‎07-25-2011

I suspect that it is the EXACT statistics request that is taking a long time. You can look at your SAS log and see how long each step takes to confirm. Not sure why you are using a macro and looping through the variables. Why not just tell SAS to do them all at once? Your macro is assuming that you have variables named NUMGENO1 to NUMGENO&n where &N is the number of variables in the dataset. (not sure how that is possible if you also have a variable named COL1D in the dataset.) proc freq data=a1 noprint; output out=n1 trend exact; tables &outcome*(numgeno1 - numgeno&vnum) / exact trend; run;

Tom · ‎07-25-2011

Use options obs=max. The actual value will vary depending on the version of SAS and your hardware. xx options obs=100; xx %put %sysfunc(getoption(obs)); 100 xx options obs=max; xx %put %sysfunc(getoption(obs)); 9223372036854775807

Tom · ‎07-25-2011

The two main problems I see with doing what I think you want to do with an INFORMAT are what you are inputting and what you are outputting. You are attempting to define a character informat but the MMDDYY format is a numeric format. It outputs a numeric date not a character string. You are attempting to define the inputs as date constants, but informats need character strings as inputs. That is why it complains about overlapping ranges. '01JAN1990' is less than '01JAN2007' which is less than '31DEC2004' because '19' < '20' and '31' > '01'.

Tom · ‎07-22-2011

Use the INPUTN function which allows the second argument to be a variable name. data tmp; Char_date='20110701'; Date_format='yymmdd8.'; num_date = inputn(char_date,date_format); put (char_date date_format num_date) (=) num_date = date9. ; run; Char_date=20110701 Date_format=yymmdd8. num_date=18809 num_date=01JUL2011

Tom · ‎07-22-2011

You can use the LIST statement to get SAS to dump the input records to the log. Then you can check for special characters like '0A'x (linefeed) that might be making SAS think that they line has ended. If you have an embedded linefeed you can use the TERMSTR=CRLF option on the INFILE statement. Another possibility is that the end of that line is empty. You might try using the TRUNCOVER option. Look at this thread. http://communities.sas.com/message/101557 Another possibility is that the lines contain tab ('09'x) characters and that SAS is expanding the tabs into spaces. This would make the input buffer longer as one tab might be expanded into upto 8 spaces.

Tom · ‎07-21-2011

Just make sure to use the GETNAMES=NO setting on PROC IMPORT. Then use PROC TRANSPOSE in SAS. proc transpose data=have out=want; id f1; var f2 - f5 ; run;

Tom · ‎07-20-2011

Use LAG to get previous value. When it is the first record for the admit date then overwrite that with the admit date. data have; informat admdate testdate mmddyy10.; format admdate testdate mmddyy10. ; input pid $ admdate : testdate : group $ @@; cards; 1 1/1/2011 1/3/2011 A 1 1/1/2011 1/9/2011 B 1 3/4/2011 4/2/2011 B 1 3/4/2011 4/8/2011 B 2 6/1/2010 6/4/2011 C 2 6/5/2010 7/4/2011 C 3 7/1/2011 7/9/2011 D run; proc sort; by pid admdate testdate ; run; data want ; set have ; by pid admdate testdate ; prevdate = lag(testdate) ; format prevdate mmddyy10.; if first.admdate then prevdate=admdate; diff = testdate - prevdate ; put pid admdate prevdate testdate diff group ; run; 1 01/01/2011 01/01/2011 01/03/2011 2 A 1 01/01/2011 01/03/2011 01/09/2011 6 B 1 03/04/2011 03/04/2011 04/02/2011 29 B 1 03/04/2011 04/02/2011 04/08/2011 6 B 2 06/01/2010 06/01/2010 06/04/2011 368 C 2 06/05/2010 06/05/2010 07/04/2011 394 C 3 07/01/2011 07/01/2011 07/09/2011 8 D

Tom · ‎07-20-2011

Use %sysevalf( &sysver > 9.2) to test if you are running a version newer than 9.2. I agree that the NOTE is inappropriate. It does seem strange that even when you ask for keyword format it does not return it, but changing the output now might break old code. Also I would like them to fix the strings returned for values that require quotes when assigning the values. For example if you try this code you will get error messages: options missing=" "; %let sopt=%sysfunc(getoption(missing,keyword)); options &sopt; What I have done is something like: %let sopt=formchar="%qsysfunc(getoption(missing))"; Here is the list of options that I indentified a couple of years ago that require that treatment. missing invaliddata formchar formdlim topmargin leftmargin rightmargin bottommargin xprintnm printerpath

Tom · ‎07-20-2011

It helps to look at some example data. data test; do a=1 to 3; do b=1 to 3; do c=1 to 3; output; end; end; end; run; data _null_; set test; by a b ; put (a first.a last.a b first.b last.b c) (=); run; a=1 FIRST.a=1 LAST.a=0 b=1 FIRST.b=1 LAST.b=0 c=1 a=1 FIRST.a=0 LAST.a=0 b=1 FIRST.b=0 LAST.b=0 c=2 a=1 FIRST.a=0 LAST.a=0 b=1 FIRST.b=0 LAST.b=1 c=3 a=1 FIRST.a=0 LAST.a=0 b=2 FIRST.b=1 LAST.b=0 c=1 a=1 FIRST.a=0 LAST.a=0 b=2 FIRST.b=0 LAST.b=0 c=2 a=1 FIRST.a=0 LAST.a=0 b=2 FIRST.b=0 LAST.b=1 c=3 a=1 FIRST.a=0 LAST.a=0 b=3 FIRST.b=1 LAST.b=0 c=1 a=1 FIRST.a=0 LAST.a=0 b=3 FIRST.b=0 LAST.b=0 c=2 a=1 FIRST.a=0 LAST.a=1 b=3 FIRST.b=0 LAST.b=1 c=3 a=2 FIRST.a=1 LAST.a=0 b=1 FIRST.b=1 LAST.b=0 c=1 a=2 FIRST.a=0 LAST.a=0 b=1 FIRST.b=0 LAST.b=0 c=2 a=2 FIRST.a=0 LAST.a=0 b=1 FIRST.b=0 LAST.b=1 c=3 a=2 FIRST.a=0 LAST.a=0 b=2 FIRST.b=1 LAST.b=0 c=1 a=2 FIRST.a=0 LAST.a=0 b=2 FIRST.b=0 LAST.b=0 c=2 a=2 FIRST.a=0 LAST.a=0 b=2 FIRST.b=0 LAST.b=1 c=3 a=2 FIRST.a=0 LAST.a=0 b=3 FIRST.b=1 LAST.b=0 c=1 a=2 FIRST.a=0 LAST.a=0 b=3 FIRST.b=0 LAST.b=0 c=2 a=2 FIRST.a=0 LAST.a=1 b=3 FIRST.b=0 LAST.b=1 c=3 a=3 FIRST.a=1 LAST.a=0 b=1 FIRST.b=1 LAST.b=0 c=1 a=3 FIRST.a=0 LAST.a=0 b=1 FIRST.b=0 LAST.b=0 c=2 a=3 FIRST.a=0 LAST.a=0 b=1 FIRST.b=0 LAST.b=1 c=3 a=3 FIRST.a=0 LAST.a=0 b=2 FIRST.b=1 LAST.b=0 c=1 a=3 FIRST.a=0 LAST.a=0 b=2 FIRST.b=0 LAST.b=0 c=2 a=3 FIRST.a=0 LAST.a=0 b=2 FIRST.b=0 LAST.b=1 c=3 a=3 FIRST.a=0 LAST.a=0 b=3 FIRST.b=1 LAST.b=0 c=1 a=3 FIRST.a=0 LAST.a=0 b=3 FIRST.b=0 LAST.b=0 c=2 a=3 FIRST.a=0 LAST.a=1 b=3 FIRST.b=0 LAST.b=1 c=3

Online Status	Online
Date Last Visited	4 hours ago