| Date: | Fri, 1 Aug 2008 14:21:26 -0500 |
| Reply-To: | "data _null_," <datanull@GMAIL.COM> |
| Sender: | "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> |
| From: | "data _null_," <datanull@GMAIL.COM> |
| Subject: | Re: one data step |
|
| In-Reply-To: | <OFB9786E2D.71A42F50-ON86257498.00684CA9-86257498.00685CB2@fd9ns01.okladot.state.ok.us> |
| Content-Type: | text/plain; charset=ISO-8859-1 |
Data _null_;
set orders;
call execute('%nrstr(%Summary('|| Order ||'));');
call execute('%nrstr(%Percentages('|| Order ||'));');
run;
Is it is often "good" to delay execution of the macro until after the
data step has finished. There is a timing issue that has been
discussed here many times. It is all way over my head, but unless you
want to use the output of the executed macro in the same data step
that has the CALL EXECUTE then %nrstr is usually desired.
On 8/1/08, Masoud Pajoh <mpajoh@odot.org> wrote:
> Can I do this with one data step?
>
> Data _null_;
> set orders;
> call execute('%Summary('|| Order ||');');
> run;
> Data _null_;
> set orders;
> call execute('%Percentages('|| Order ||');');
> run;
>
|