David K's suggestion will output a dataset with the directory names, which you can then read into a macro. ... View more

Are you looking for a program/macro that will read all of the paths and then use those paths as parameters? Or, are you simply looking to write the directories to a data set? ... View more

The "@" symbol in this context is a column pointer control. You've instructed SAS to write the AGE variable at column 5 -- which just so happens to overlap with the values in the NAME variable. Try this instead. data _null_; set Data; file ''C:\Documents and Settings\Desktop\Input\test.txt'; put name @20 age 2.; run; ... View more

This works, assuming only one possible valid_value for each crossing of Variable (as per your desired output). data have ; infile datalines dlm=',' dsd; informat documentation_vv occupancy_vv property_vv purpose_vv $50.; input documentation_invalid documentation_vv $ occupancy_invalid occupancy_vv $ property_invalid property_vv $ purpose_invalid purpose_vv $ ; datalines ; 0,"FULL, SUB, VOI/VOA, NODOC, QUICK",0,"OWNER, 2NDHOME, INVESTOR",1,"SF, MF, TOWNHOUSE, CONDO",0,"PURCHASE, CASHOUT, RATE/TERM" 0,"FULL, SUB, VOI/VOA, NODOC, QUICK",1,"OWNER, 2NDHOME, INVESTOR",0,"SF, MF, TOWNHOUSE, CONDO",0,"PURCHASE, CASHOUT, RATE/TERM" 0,"FULL, SUB, VOI/VOA, NODOC, QUICK",0,"OWNER, 2NDHOME, INVESTOR",0,"SF, MF, TOWNHOUSE, CONDO",0,"PURCHASE, CASHOUT, RATE/TERM" 0,"FULL, SUB, VOI/VOA, NODOC, QUICK",0,"OWNER, 2NDHOME, INVESTOR",0,"SF, MF, TOWNHOUSE, CONDO",0,"PURCHASE, CASHOUT, RATE/TERM" 1,"FULL, SUB, VOI/VOA, NODOC, QUICK",0,"OWNER, 2NDHOME, INVESTOR",0,"SF, MF, TOWNHOUSE, CONDO",1,"PURCHASE, CASHOUT, RATE/TERM" 0,"FULL, SUB, VOI/VOA, NODOC, QUICK",0,"OWNER, 2NDHOME, INVESTOR",0,"SF, MF, TOWNHOUSE, CONDO",0,"PURCHASE, CASHOUT, RATE/TERM" ; ;;;; /* transpose numeric variables */ proc transpose data=have out=counts name=Variable; run ; /* cleanup */ data counts  ; set counts ; drop col1-col6; tot_count = n ( of col1-col6 ); valid_count = sum ( of col1-col6 ) ; invalid_count = tot_count - valid_count ; run ; /* transpose character vars */ proc transpose data=have out=valid_values name=Variable; var documentation_vv occupancy_vv property_vv purpose_vv ; run ; /* cleanup */ data valid_values ; set valid_values ; drop col2-col6; rename col1=valid_values; run ; /* merge */ proc sql ; create table want as select t1.*, t2.valid_values from counts t1   , valid_values t2 where substr ( t1.variable , 1, 8 ) = substr ( t2.variable , 1, 8 ) ; quit; Message was edited by: Michael McCormick ... View more

In the sample of desired output above, you have a column for valid_values. Does your data have more than one non-unique value for "valid_values" for a given crossing? For example, are there values other than "FULL, SUB, VOI/VOA, NODOC, QUICK" for the row "documentation_invalid"? (I realize that your sample data only has one unique value for each proposed crossing, but actual data may not). ... View more

I forgot to mention that your variable names will not show up as you expect them to when you use the proc import code. ... View more

Ok - so the first thing you need to do is to turn your text file into a SAS dataset. Your text file appears to be tab delimited. Try the following code. Once you have a SAS dataset, then try PROC TRANSPOSE. (Second try - code didn't show up the first time . . . ) proc import datafile='some path\real data.txt'      out=datafile1      dbms=dlm      replace;      delimiter='09'x; run; ... View more

Maybe I'm asking something that everyone already knows the answer to, so I apologize if I'm asking out-of-turn. Is your data ("dataset1") already in a SAS dataset? Or, is it in the form of text as per your "Real data.txt.zip"? ... View more

True true, the Case statement sitll works via "advanced expression". For some reason, SAS is promoting "if-then-else" logic via the "recode column" function. Both the "advanced expression" and the "recode column" features result in a CASE expression (when used for if-then-else logic). ... View more

You are definitely on the right track. In EG 4.2 http://support.sas.com/kb/38/261.html In EG 4.1 http://support.sas.com/kb/32/160.html ... View more