The problem is TABLE3.  You want to concatenate it with TABLE2 so that you get all the dates, but you also want to merge it by PID so that all records for the same PID get the value of the MS variable. data table1 ;   input pid sex $ dob occ $ ; cards; 1 F 1985 EDU 2 M 1986 IT 3 M 1986 EDU run; data table2 ;   input pid date_1 ; cards; 1 1999 2 1999 run; data table3 ;   input pid date_2 ms $; cards; 2 2002 A 3 2000 B run; data table4 ;   input pid sex $ dob occ $ ms $ date ; cards; 1 F 1985 EDU . 1999  2 M 1986 IT A 1999 2 M 1986 IT A 2002 3 M 1986 EDU B 2000 run; data dates;   set table2 table3 ;   by pid;   drop ms; run; data want ;   merge table1 table3 (keep=pid ms) dates ;   by pid ;   date = coalesce(date_1,date_2); run; proc compare data=want compare=table4; run; ... View more

I am sorry, but what is the question?  Did you get an error message? Or are you not getting the expected results? ... View more

Are you using CALL EXECUTE to call the macro? You might try changing that to instead write code to a file and %INC the file.  Here is an example. 275 %macro test; 276 data x; 277  line1='This is testing how long lines of code look'; 278  line2='This is testing how long lines of code look'; 279  line3='This is testing how long lines of code look'; 280 run; 281 %mend test; 282 283 data _null_; 284   call execute('%test'); 285 run; MPRINT(TEST):  data x; MPRINT(TEST):  line1='This is testing how long lines of code look'; MPRINT(TEST):  line2='This is testing how long lines of code look'; MPRINT(TEST):  line3='This is testing how long lines of code look'; MPRINT(TEST):  run; NOTE: DATA statement used (Total processtime):      real time           0.00 seconds      cpu time            0.00 seconds NOTE: CALL EXECUTE generated line. 1   +data x;  line1='This is testing how longlines of code look';  line2='This istesting how long lines of code look';  line3='This is testing how long lines of codelook'; run; NOTE: The data set WORK.X has 1 observationsand 3 variables. NOTE: DATA statement used (Total processtime):      real time           0.01 seconds      cpu time            0.00 seconds 286 287 filename code temp; 288 data _null_; 289   file code; 290   put '%test;'; 291 run; NOTE: The file CODE is:      Filename=C:\DOCUME~1\ABERNA~1\LOCALS~1\Temp\SAS TemporaryFiles\_TD2288\#LN00010,      RECFM=V,LRECL=256,File Size (bytes)=0,      Last Modified=30Sep2011:14:29:38,      Create Time=30Sep2011:14:29:38 NOTE: 1 record was written to the file CODE.      The minimum record length was 6.      The maximum record length was 6. NOTE: DATA statement used (Total processtime):      real time           0.00 seconds      cpu time            0.01 seconds 292 %inc code; MPRINT(TEST):  data x; MPRINT(TEST):  line1='This is testing how long lines of code look'; MPRINT(TEST):  line2='This is testing how long lines of code look'; MPRINT(TEST):  line3='This is testing how long lines of code look'; MPRINT(TEST):  run; NOTE: The data set WORK.X has 1 observationsand 3 variables. NOTE: DATA statement used (Total processtime):      real time           0.00 seconds       cpu time            0.00 seconds ... View more

Shouldn't you have an OUTPUT statement where you can specify the dataset name using the OUT=. proc transreg data=TEMP outtest=TEMPb ss2 cli; model boxcox(variable)=identity (pig); output out=tempnorm ; run; quit ; ... View more

Is the problem how to resolve a macro variable name when you want to use another macro variable's value as part of the name? If so then use extra &'s. Try this little bit of code: %let e1monthago='01AUG2011'd; %let N=1; %put e&n.monthago=&&e&n.monthago; ... View more

I am confused.  Let me try to re-state the task. You have a MACRO variable EDATESET that contains a SAS date value. You want to generate COUNT new MACRO variables that contain SAS date values for the previous COUNT months. Anyway try: %macro exclude(count,sdate); %local i var; %do i=1 %to &count ;    %let var=e&i.monthago;    %global &var;    %let &var=%sysfunc(intnx(month,&sdate,-&i)) ; %end; %mend exclude; Why would you call such a macro EXCLUDE? Perhaps if you explain the larger task there is a much easier way to do what you want? ... View more

The + signs are usually an indication of included code and not macro generation.  Normally I turn off SOURCE2 and turn on MPRINT. How are you calling the macro?  Are you using SAS/Connect so that macro is generating code that is sent to the remote session? ... View more

Looks likes your limitation is that you only have Excel 2003. That is limited to 64K rows. ... View more

Do you have examples of what you mean? In general the issue I have seen is that for long statements the MPRINT lines will be flowed into a single line.  Indentation is also lost. Is this what you are talking about?  If so I think you are out of luck. What you can control are your comments. When writing a macro I distinquish in my comments those that are useful when reviewing the log and those that are useful when editing or reviewing the code.  An example of the latter is and explaination of a particularly tricky piece of code or a special syntax requirement so that I don't break the code code the next time I edit it. For the first type I use normal *...; comments. These will print with the code lines when MPRINT is on.  For the latter I use %*... ; comments.  I try not to use /* */ comments other than for header blocks and rarely when I need to embed a comment in the middle of a statement. Placement of your comments are important. 1) Do not put *..; comments at the end of a line after the code because then the comment prints below the statement in the log. 2) Place comments for conditional blocks of code inside the conditional so that they will print only when the condition is true. %if %sysfunc(exist(mydata)) %then %do; * Generate summary of MYDATA; proc summary data=mydata .... %end; ... View more

I am really not clear on what you mean by "use the hash key" in proc sort. Why do you want to sort your data? Would an index serve your needs? Also how large is your dataset? What number does 12lacs represent? ... View more

Let me see if I can translate the code into english. Looks like you have a list of treatment codes and are trying to loop over them. Personally I am not that fond of making a series of macro variables when the information can be maintained in a single variable. Your list of treatment codes could be recorded into a single macro variable using two different delimiters. If we use space and slash as the delimiters we could store your example as: %let treatments=a b/c d e; %let ngroups=2; %let maxtrt=3; Then you seem to want to generate a SAS dataset with these treatment codes. You should be able to do that with a data step and not need to worry about macro logic at all. data treatments;    array trt $ trt1-trt&maxtrt ;   do i=1 to &ngroups;      call missing(of trt(*));      do j=1 to &maxtrt;         trt(j)=scan(scan("&treatments",i,'/'),j,' ');      end;      output;    end;    drop i j ; run; ... View more