- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Posted 12-02-2008 08:22 PM
(1461 views)
Hi guys,
My question is can i call macro within a proc sql procedure?
I am writing a simple proc sql procedure. the macro will take table a,b fields as parameters.
proc sql;
select a,
b,
c,
¯o(a.sth, b.otherthing)
from table a left join table b
quit;
Thanks,
My question is can i call macro within a proc sql procedure?
I am writing a simple proc sql procedure. the macro will take table a,b fields as parameters.
proc sql;
select a,
b,
c,
¯o(a.sth, b.otherthing)
from table a left join table b
quit;
Thanks,
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Yes, you can.
Remember in mind that macro is just string substitution, which always occurs before code execution.
Remember in mind that macro is just string substitution, which always occurs before code execution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Kevin,
so you mean the macro will be executed first and then sas execute the code.
but some of those parameters are coming from the joined tables, if the table are not joined first, does the macro still be able to take them in as parameter?
thanks,
so you mean the macro will be executed first and then sas execute the code.
but some of those parameters are coming from the joined tables, if the table are not joined first, does the macro still be able to take them in as parameter?
thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
If the macro variable is not initialized, then it would probably not have any value if the join hasn't been done.
Macro variable just holds values that can be assigned globally in SAS session (that is, independent from data steps, SQL etc). They don't get executed. If you talk about macro execution, you probably mean %macro definitions, which probably contain macro statements maybe mixed with other SAS statements/programs.
You could review the on-line documentation for SAS macro programming.
/Linus
Macro variable just holds values that can be assigned globally in SAS session (that is, independent from data steps, SQL etc). They don't get executed. If you talk about macro execution, you probably mean %macro definitions, which probably contain macro statements maybe mixed with other SAS statements/programs.
You could review the on-line documentation for SAS macro programming.
/Linus
Data never sleeps