sasroot is the name of an environment variable:   %put sasroot: %sysget(sasroot);   This is the path your work folder:   %put sasuser: %sysfunc(getoption(sasuser)); if you are submitting programs in batch then startup-only option sysin contains the path/filename.ext    %put sysin: %sysfunc(getoption(sysin));   I can't remember the session option/macro-variable which has this path+filename.   trivial comment: you can code this without the assignment and reference to curdir   %let rc = %sysfunc(filename(fr,.)); /* %let curdir = */ %sysfunc(pathname(&fr)); %let rc = %sysfunc(filename(fr)); /*&curdir */ %mend curdir;   ... View more

Here's an sql program that uses monotonic to add memnum to a list of data set names.   *name: make-list-memnames-sql.sas; PROC sql noprint; create table list_memnames(label = "&libname") as select libname, monotonic() as memnum label='member number', memname, nobs, nvar as nvars, memlabel from dictionary.tables where libname eq "%upcase(&libname)" and memtype eq 'DATA'; quit; %put trace make-list-memnames-sql ending; *name: make-list-memnames-sql-test.sas; %let libname = sashelp; %include 'make-list-memnames-sql.sas'; proc print; run; here's the listing:   Obs libname memnum memname nobs nvars memlabel 1 SASHELP 1 AACOMP 1544 4 2 SASHELP 2 AARFM 61 4 3 SASHELP 3 ADSMSG 426 6 4 SASHELP 4 AFMSG 1090 6 5 SASHELP 5 AIR 144 2 airline data (monthly: JAN49-DEC60) 6 SASHELP 6 APPLIANC 156 25 Sales time series for 24 appliances by cycle This is from the paper Advanced Programming Concepts: History of the List Processing and Cardinality Ratio Memes published in SESUG.2017 http://www.lexjansen.com/sesug/2017/CC-98.pdf   Ron Fehd  macro maven ... View more

here is an scl solution   you'll need to modify your macro parameters to use this   but otherwise, it can be used to call any macro for every variable in a data set.   options mprint source2; *include 'freqhilo.sas'; %let libname = sashelp; %let memname = class; %let macro_name = mymacro; %let macro_name = echo; %macro echo(libname=,memname=,name=,type=,length=,varnum=); %put _local_; %mend; *echo(libname=1,memname=2,name=3,type=4,length=5,varnum=6); *endsas; %let _dsid = %sysfunc(open (&libname..&memname,i)); %let _n_obs = %sysfunc(attrn(&_dsid,nobs)); %let _n_vars = %sysfunc(attrn(&_dsid,nvar)); %let _rc = %sysfunc(close(&_dsid)); %put echo &=_n_obs &=_n_vars; DATA _null_; attrib name length = $32 type length = $1 length length = 8 statement length = $128; _dsid = open("&libname..&memname"); do varnum = 1 to &_n_vars; name = varname (_dsid,varnum) ; type = lowcase(vartype (_dsid,varnum)); length = varlength(_dsid,varnum); statement = catt ('%',"&macro_name" ,'(name=' ,name ,',type=' ,type ,',length=',length ,',varnum=',varnum ,",libname=&libname,memname=&memname)" ); put statement; call execute(catt('%nrstr(',statement,')')); end; _rc = close(_dsid); run; Ron Fehd this program is based on my SESUG.2017 paper Advanced Programming Concepts Cardinality Ratios and Types   code in the paper will be available after Nov 4.   http://www.sascommunity.org/wiki/Cardinality_Ratios_and_Types   ... View more

I see a number of choices in your problem statement.   My perspective is show in Database Vocabulary: Is Your Data Set a Dimension (LookUp) Table, a. Fact Table or a Report?   My commentary has two parts: example, and critique of your problem   * example of database transaction table, snapshots: periodic(monthly) and accumulating   1. transaction table, of credit card purchases   DATA library.transactions_data_structure; attrib id length = 8 datetime length = 8 vendor length = $16 amount length = 8; stop; DATA transactions_2017; if 0 then set library.transactions_data_structure; infile datalines; datalines; ... ; 2. summary to grain = monthly macro or %include?     PROC summary data = transactions_&year (where =(&date_start <=datetime <=&date_end)); *out =library.snapshot_accum_&year._month This paper Macro_Loops_with_Dates has code to fetch the date_* information into macro variables.   3. accumulating snapshot, which I suspect is kind of what you want. DATA library.snapshot_accum_data_structure; if 0 then set library.transaction_data_structure(keep = id); attrib sum_01 length = 8 ... sum_12 length = 8; stop; DATA library.snapshot_accum_&year; if 0 then set library.library.snapshot_accum_data_structure; update library.snapshot_accum_&year library.snapshot_accum_&year._&month; by id; summary: database theory is always about data structure and what it is used for   * transaction history is only appended to.   * snapshot-periodic (grain in(daily, weekly, monthly, quarter, annual)) is a summation of transaction history, between two date(-times) run once after grain is closed   * snapshot-accumulating for the annual budget summary shown above is run after the periodic-snapshot is complete may be, probably is, in same program.   ** my commentary on your problem. your description kinda/sorta fits the model of snapshot-accumulating.   The choices I see for you are: * I suggest two fields year and AcademicYear I know you have several examples of people who were sophomores for many years.   * naming conventions of variables: cum_GPA_year_2016 or cum_GPA_year_1   * text fields EdLevel and Major ought to be reduced to integers the last thing you want to be doing is editing or worse, parsing text, for information   last advice: design the data structure of your last report first and move back up the line, with the example theory shown above.   hth Ron Fehd  recipe maven   ... View more

This is a non-trivial problem.   note.1: where I changed the length of a known variable with the attribute statement and the var-name does not match the case of the master data set then that var-name is changed. Since is this is a demo of proof-of-concept this may not matter.   note.2 be aware of the fragile nature of the cat* functions; if they return a value larger than $200 then it will truncate your list solution: add a length=nnnn after the catx function call   note.3 data structure may be only <1% of your code but it is the first place I turn to when my algorithm fails. Likewise here: I recommend adding the data structure of A to the code that creates B; this is my recommended solution and solves all later appending.   DATA B; if 0 then set A; *...; note.4 this solution assumes both data sets are different and thus have to be copied in order to change the lengths.   hth Ron Fehd  list processing maven   *note case of name matters in output; data class1; attrib sex length = $2; set sashelp.class; data class2; attrib name length = $10; set sashelp.class; %macro save_attrib(libname=work, memname=,out=); PROC sql noprint; create table &out as select name, lowcase(name) as name_lc, type, length from dictionary.columns where libname eq "%upcase(&libname)" and memname eq "%upcase(&memname)" and memtype eq "DATA"; quit; run; %mend; %save_attrib(memname=class1,out=contents1) %save_attrib(memname=class2,out=contents2) DATA attributes; set contents1 contents2; run; PROC sort data = &syslast; by name_lc length; run; DATA attributes; retain max_length 0; set &syslast; by name_lc; if first.name_lc then max_length = 0; max_length = max(max_length,length); if last.name_lc then output; run; PROC sql noprint; select catx(' ',name,'length=' ,case when type eq 'char' then '$' else ' ' end ,length) into :list separated by ' ' from &syslast; quit; %put echo &=list; %macro update_attrib(data=,base=largest); DATA &DATA; attrib &list; set &data; PROC append data = &data base = &base; run; %mend; %update_attrib(data=class1) %update_attrib(data=class2) proc print data = &syslast; PROC sql; describe table &syslast; quit; ... View more

warning: fragile code!   select cat(...) %*fragile!; into :mvar   @ChrisHemedinger, remember that the cat* functions create text whose default length is $200 and when truncation occurs --- you stuffed tooooo much text into the function call --- no warning is given   Ron Fehd  been burned by this very trick maven ... View more