clear results/outputs generated by procedures within macro

[TX_STAR]

Hello members,

How can I clear the results and outputs generated by the procedures within a macro? For example, for the following code. How can I only keep the data2 in within the macro and clear the intermediate results generated by % macro bydomain (conditon1=a, condition2=b); before run % macro bydomain (conditon1=c, condition2=d);?

Data data2;

set data1;

run;

% macro bydomain (conditon1, condition2);

data data2;

...

run;

%mend;

% macro bydomain (conditon1=a, condition2=b);

% macro bydomain (conditon1=c, condition2=d);

...

Thanks so much!!!

[Reeza]

https://blogs.sas.com/content/iml/2015/05/28/five-reasons-ods-exclude.html

ODS SELECT and ODS EXCLUDE are what are needed. Or NOPRINT within the various procs. 

[Reeza]

I use a naming convention, with _ to start the name for all my intermediary tables. Then you can drop them using a prefix shortcut which will clear all at once.

delete _:;

[ballardw]

First thing would be to provide a more detailed description and possibly use different data set names in the example.

You only actually show one data set inside the macro, repeating the name of one outside, and it is not clear what you want to keep.

Typically I would use proc datasets to delete any datasets that I don't want. Either at the beginning of a macro to prevent reuse of an existing set or at the end of the macro to clean up before it ends.

The syntax is

Proc datasets library=somelib;

    delete datasetname;

quit;

you may want the NOPRINT option to reduce any output in the log

[r_behata · Accepted solution]

Incase you you are trying to just delete specific intermediate datasets only, try this.

%macro bydomain (conditon1, condition2);

	proc datasets nolist lib=work mtype=data;
		delete data2;
	quit;

	data data2;
		...

		run;
%mend;

[TX_STAR]

I moved the following code inside the macro, the problem solved. But my solution might not be best of efficient one. What happened was When I run the second macro call (conditon1=c, condition2=d) after running the first call (conditon1=a, condition2=b), the N count of the data2 was not right. I guess sas keeps temporary data that replaced initial data2. When I call the 2nd macro, the data2 was not correct one. When I keep the following code inside the macro, each call will start with a initial data2. Hopefully this time I am clear. Thank you all.
Data data2;
set data1;
run;