I'm having a problem which I think MAY be related to this bug but I'm not sure because I'm venturing into new SAS coding territory! I'm using a combination of PROC STREAM, a macro template to spit out XML, and inside the template calling a macro that has a logic to set a global variable which will get used after the dosubl call. /** Something similar to this **/
proc stream outfile=REQUEST
begin%due_date_template(...)
;;;;
run;
.
.
.
/** sub section of the due_date_template macro **/
%do i=1 %to &numAlerts;
.
.
%let rc= %sysfunc(dosubl('due_date_macro(var1,var2,var3...)'));
.
.
.
/** inside the due_date_macro, there is logic to set a global variable called
due_date
**/
%put due_date = &due_date;
%end;
/**
1st time through the due_date gets set properly
the remaining times in the iteration the due_date remains the initial value set
by the dosubl call even though a new due_date is being calculated.
**/ Is this part of the bug in M3? I've tried everything to get that &due_date macro to update after the dosubl call but it always remains the first value set! -Matt
... View more