topic Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will in SAS Programming

macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will be compiled.

tom12122 — Thu, 17 May 2012 11:58:28 GMT

Hi.

I've got problem apparently with some macro execution timing.

I've got macro A from which I execute macro C in a loop %do %while%.

I need to assure that macro C finished executing in iteration n before executing macro C in iteration n+1.

Now I get errors:

Line 696: ERROR: The macro C is still executing and cannot be redefined.

Line 697: ERROR: A dummy macro will be compiled.

and in the log i see that some iterations of macro C did not start at all.

Is there a way to force SAS to woit for macro execution?

Thanks for help.

Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will be compiled.

Tom — Thu, 17 May 2012 12:21:46 GMT

Sounds like you have code like:

%macro a;

%macro c;

%mend c;

%c;

%mend a;

Move the definition of macro c outside of the definition of macro a.

%macro c;

%mend c;

%macro a;

%c;

%mend a;

Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will be compiled.

tom12122 — Thu, 17 May 2012 12:35:17 GMT

i have;

%macro c;

%mend c;

%macro a;

%do %while ...

%c;

%end;

%mend a;

Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will be compiled.

Tom — Thu, 17 May 2012 13:01:08 GMT

Next suspect is unbalanced quoting. Try starting SAS fresh. Does the macro A work the first time it is called?

Does it matter the values that are passed to it?

Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will

thepushkarsingh — Fri, 23 Feb 2018 11:18:25 GMT

I am facing the same issue.

The macro 'c' works perfectly when stand alone, but when called in loop like -

%macro a;

%do i=1 %to 20;

%c;

%end;

%mend;

%a;

It gets stuck at some point and goes in never ending loop. And when forced 'STOP', any code I try to run that loop starts its run. Each time I had to close the project.

Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will

gamotte — Fri, 23 Feb 2018 11:26:31 GMT

Hello,

Without knowing what the macro c contains, it is difficult to answer.

Could there be a conflict between macrovariables used in a and c ?

For instance, if you use the same counter i in both macros they have

to be declared as local.

Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will

thepushkarsingh — Fri, 23 Feb 2018 11:37:59 GMT

macro 'c':

%macro combos(trxn=);
%let I=1;
data _ben_;
set _benef_(obs=&I. firstobs=&I.);
if senders gt 1 then do;
call symput('n_connect',senders);
end;
run;

proc surveyselect
data= _senders_ (where=(trxn_per_benef=compress(&trxn.))) out= _sen_ method=srs n= Compress(&n_connect.) noprint;
run;

data _tmp_;
merge _ben_ _sen_;
run;

data _tmp_;
set _tmp_;
n=_n_;
if missing(benef_id) then
do;
do until (not missing(benef_id));
n=n-1;
set _tmp_(keep=benef_id n_ben_f senders in_trxn trxn_per_sender) point=n; *second SET statement;
end;
end;
run;
%reset;
%if &upto. >= 100 %then %goto exit;

%fill_s: %do I=&I. %to &upto.;
/*Switch to Senders*/
%fill_senders;
%end;
%reset;
%if &upto. >= 100 %then %goto exit;

%do I=&I. %to &upto.;
/*Switch to Recipients*/
%fill_benefs;
%end;
%reset;
%if &upto. < 100 %then %goto fill_s;
%exit:

%mend;
%combos(trxn=1);

Macro 'a' :

%macro create_combos;

%do t=1 %to 20;

%combos(trxn=&t.);

%end;

%mend;

But then again the other two macros 'fill_benefs' and 'fill_senders' are using macro variables 'I' and 'TRXN', common to them but I need them as start from the value one ends like if 'I' ends in %fill_benefs at 15, I need the I starting from 16 in %fill_senders.

Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will

gamotte — Fri, 23 Feb 2018 13:03:36 GMT

Please use the" little running man" icon to post code with proper identation.

%macro combos(trxn=);

    %let I=1;
    
    data _ben_;
        set _benef_(obs=&I. firstobs=&I.);
        if senders gt 1 then do;
            call symput('n_connect',senders);
        end;
    run;

    proc surveyselect
        data= _senders_ (where=(trxn_per_benef=compress(&trxn.))) out= _sen_ method=srs n= Compress(&n_connect.) noprint;
    run;

    data _tmp_;
        merge _ben_ _sen_;
    run;

    data _tmp_;
        set _tmp_;
        n=_n_;
        if missing(benef_id) then
        do;
            do until (not missing(benef_id));
                n=n-1;
                set _tmp_(keep=benef_id n_ben_f senders in_trxn trxn_per_sender) point=n; *second SET statement;
            end;
        end;
    run;

    %reset;
    
    %if &upto. >= 100 %then %goto exit;

    %fill_s: 

    %do I=&I. %to &upto.;
        /*Switch to Senders*/
        %fill_senders;
    %end;
    
    %reset;
    
    %if &upto. >= 100 %then %goto exit;

    %do I=&I. %to &upto.;
        /*Switch to Recipients*/
        %fill_benefs;
    %end;

    %reset;
    
    %if &upto. < 100 %then %goto fill_s;
    
    %exit:

%mend;

%macro create_combos;

    %do t=1 %to 20;

        %combos(trxn=&t.);

    %end;

%mend;

You still have loops calling macros that are black boxes to us. Do these macro modify the macrovariable upto ?

If not why testing the same condition several times. Insetad of using gotos, you should enlose treatments with do end

so that it's easier to follow the logic.

You initialize loops on macrovariable I with its own value &i. I guess the reset macro reinitialise I otherwise your second loop will then go from &upto+1 to &upto. which i doubt you really want.

Can you try to post a minimal executable example replicating the issue ?

Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will

thepushkarsingh — Fri, 23 Feb 2018 13:08:41 GMT

As you said, in some cases I got stuck with "otherwise your second loop will then go from &upto+1 to &upto.". Thanks a lot!

Re: macro timing - error - The macro C is still executing and cannot be redefined.A dummy macro will

Tom — Fri, 23 Feb 2018 15:29:13 GMT

The first line of the inner macro should give a good hint into the most likely source of your problem.

%macro combos(trxn=);
%let I=1;

Macro variable scoping.

If the environment that has called %COMBOS() already had a macro variable named I that it was using to control a loop then the first line in COMBOS just changed the value of that existing macro variable. Follow these simple rules and you should be ok.

Always define your macro variable's scope before you use them.
Unless you intend to modify an existing macro variable or need to reference the value after the macro finishes then define your macro variable as LOCAL.
Always test if a macro variable exists before defining it as GLOBAL.

The macro COMBOS has defined one local macro variable TRXN (all parameters are by definition local macro variables) but it is referencing these macro variables without defining their scope.

I
N_CONNECT
UPTO

And it is also calling other macros that might be lackadaisical in their use of macro variable scoping.