topic Re: Basic SAS %macro question in SAS Programming

Basic SAS %macro question

Wafflecakes — Thu, 05 Oct 2017 14:57:37 GMT

Good day all,

Suppose I have a sas macro like so...

%macro test

proc reg data=testing;

model y=x1 x2 x3;

output out=testing2

run;

proc print data=testing2;

var x1 x2 x3

run;

%mend test;

I need to call the macro many, many times, but the 'testing2' output dataset is different each time I call it. How do I make this change?

Re: Basic SAS %macro question

Reeza — Thu, 05 Oct 2017 15:01:04 GMT

Your code has errors. I'm going to assume it's sample/representative code.

Add a parameter to your macro definition that provides the data set name and then call the macro multiple times using CALL EXECUTE.

Or build an automatic DO loop into your macro.

There are examples of either here:

https://stats.idre.ucla.edu/sas/seminars/sas-macros-introduction/

or search Lexjansen.com

Re: Basic SAS %macro question

Kurt_Bremser — Thu, 05 Oct 2017 15:05:14 GMT

You only use a macro if you need dynamic code. There is nothing dynamic in your example code.

IF there is something in your real code that needs to be made flexible, you can use the parameters used for that to name the output datasets in some way.

Suppose this code

proc reg data=testing;
model y=x1;
output out=testing1;
run;

proc print data=testing1;
var x1;
run;

has to be made flexible, then you would do this:

%macro test(param);

proc reg data=testing;
model y=x&param.;
output out=testing&param.;
run;

proc print data=testing&param.;
var x&param.;
run;

%mend;

%test(1)
%test(2)
%test(3)

Re: Basic SAS %macro question

Wafflecakes — Mon, 09 Oct 2017 18:54:33 GMT

Kurt - what if more thna 1 parameter needs to be made flexible?

Re: Basic SAS %macro question

Kurt_Bremser — Mon, 09 Oct 2017 18:59:06 GMT

@Wafflecakes wrote:

Kurt - what if more thna 1 parameter needs to be made flexible?

Use more macro parameters.

Re: Basic SAS %macro question

Wafflecakes — Mon, 09 Oct 2017 19:07:22 GMT

%macro test(par, param);
proc reg data=testing;
model y=x;
where test=&par
output out=&param.;
run;

proc print data=&param.;
run;

%mend;

%test(1,1)
%test(2,2)
%test(3,3)

Is this correct?

Alternatively....

%test(1, linear1)

%test(2, linear2)

%test(3, linear3)

Re: Basic SAS %macro question

Wafflecakes — Mon, 09 Oct 2017 19:09:11 GMT

Keep in mind the &par refers to the value of a variable in the dataset and &param refers to the name of an outputted dataset.

Re: Basic SAS %macro question

Kurt_Bremser — Mon, 09 Oct 2017 19:11:19 GMT

Your first version to call the macro won't work, as single digits are not valid as dataset names; your second version will work.

Re: Basic SAS %macro question

Wafflecakes — Mon, 09 Oct 2017 19:12:20 GMT

I got some output but the numbers are off.

Re: Basic SAS %macro question

Kurt_Bremser — Mon, 09 Oct 2017 19:16:03 GMT

If proc reg doesn't give you the results you expect, you should post that as question in the stat proc forum.

Re: Basic SAS %macro question

Wafflecakes — Mon, 09 Oct 2017 19:22:23 GMT

when you put &param and call %test(1,linear1), does the name of the dataset get called linear1 where &param first shows up and gets used in the subsequent proc print step as linear1?

Re: Basic SAS %macro question

Kurt_Bremser — Mon, 09 Oct 2017 19:25:45 GMT

@Wafflecakes wrote:
when you put &param and call %test(1,linear1), does the name of the dataset get called linear1 where &param first shows up and gets used in the subsequent proc print step as linear1?

If I read you right, yes. Use options symbolgen mprint mlogic; to show all macro activity in the log.

Re: Basic SAS %macro question

Wafflecakes — Mon, 09 Oct 2017 19:46:42 GMT

the proc reg part of the macro works but not the proc print - does it matter if the proc print step is actually a data step: data &param; set &param;

Re: Basic SAS %macro question

Kurt_Bremser — Mon, 09 Oct 2017 20:42:08 GMT

Look at the log; you'll see which dataset is created by proc reg, and which one is used in proc print.

Re: Basic SAS %macro question

Reeza — Mon, 09 Oct 2017 23:53:21 GMT

@Wafflecakes wrote:
does it matter if the proc print step is actually a data step: data &param; set &param;

What? That doesn't make a lot of sense.