Even so this is not a full DATA step.  there is no DATA or SET statement.The macro variables are defined elsewhere? Retaining values is across observations.  Since we cannot see where the observations are coming from or what variables are on the PDV, we have to guess as to what is being retained. Can you perhaps modify one of my silly examples from above using the CLASS data set to show us what you have so far and what you want to have happen? ... View more

'push the boundaries of being a good programmer'....  Being a good programmer does NOT mean that the most complicated solution should be used.  A good programmer understands the range of possible programming solutions and picks the best one for the task.  The better the programmer the broader the range of choices and the better the understanding of all the ramifications of that choice. In these forums you often see the range of solutions to problems that reflect these levels of understanding.  At SAS Global Forum next month I will be presenting a paper that addresses some of the issues of those choices and the topics came from these forums. ... View more

In the first step that follows the 30 dates are created for each observation so retaining is not necessary. data want;    set sashelp.class;    array dates {30} date1-date30;    do date = '01may2013'd to '30may2013'd;       output want;    end;    run; In the second example the array is filled once and then the observations are read in a DOW loop.  This step could be simplified, but will be more efficient for large data sets.  In either case I am not sure that you really want the thirty dates repeated for each observation. data want2;    retain date1-date30 .;    array dates {30} date1-date30;    i=0;    do date = '01may2013'd to '30may2013'd;       i+1;       dates{i}=date;    end;    do until(done);       set sashelp.class end=done;       output want2;    end;    stop;    run; ... View more

Array values are not retained unless you specify a retain statement or if you use a temporary array.  Since we can only see a fragment of your DATA step, it is not obvious how to answer your questions. ... View more

In the Enhanced Editor or EG blocks of text can easily be inserted using Keyboard abbreviations.  a number of these abbreviations have been posted on a sasCommunity article. http://www.sascommunity.org/wiki/Abbreviations/Macros ... View more

Are you saying that the PROC PRINTTO did not work for you?  Show us the PRINTTO steps. ... View more

We cannot see the end of your macro to see how you are making the report itself.  Most likely you want to create the WHERE in the DATA step so that it has all the appropriate dates.  You can also eliminate your DATA _NULL_ step. %let lastddate = %sysfunc(intnx(Month, %sysfunc(TODAY()), &n)); %let startdate  = %sysfunc(intnx(Month, %sysfunc(TODAY()), %eval(&n-1))); the WHERE becomes something like: where &startdate le date le &lastdate; But until we know more of what you need these are guesses. ... View more

as suggested by @Quentin PRINTTO should do the trick.  You could also submit the jobs individually using the OS scheduler.  Other options include the use of the ALTLOG options and the use of DM statements to redirect the log. ... View more

Although I have not used PROC PANEL, I do not believe that that it supports programming statements. You can calculate the median of a variable using other procedures.  Most likely for your needs will be either MEANS or SUMMARY. proc summary data=have; class country; var size; output out=want median= /autoname; run; ... View more