Date: Tue, 13 Jul 2010 08:28:17 -0400
Reply-To: Michael Raithel <michaelraithel@WESTAT.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Michael Raithel <michaelraithel@WESTAT.COM>
Subject: Re: Masking macros in rsubmit-block
Content-Type: text/plain; charset="utf-8"
Jesper posted the following reply to Mark's helpful suggestion in this continuing thread:
> Hi Mark,
> Thanks for the reference.
> In the conclusion is stated: "In many cases just moving the
> RSUBMIT/ENDRSUBMIT outside the macro causes everything to work as
> By doing this you are causing the macro itself to be complied on the
> host leaving no room for error as to what should and shouldnâ€™t get
> In my example this doesn't hold true (maybe because of macro-nesting),
Jesper, I have not been following this thread to closely, and--to be honest--I am a bit lazy this morning and not hep to reading through the entire thread as I wait for this morning's 8:30am SAS Resource Planning Group meeting to start. So, let me throw a quick suggestion your way:
Can either the %SYSLPUT or the %SYSRPUT macro statements help you out here? They are used to assign macro variables between SAS/CONNECT sessions on the client and the host.
Just a thought. Oops! Meeting starts in 2 minutes; gotta go!
Best of luck in all your SAS endeavors!
I hope that this suggestion proves helpful now, and in the future!
Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.
Michael A. Raithel
"The man who wrote the book on performance"
Author: Tuning SAS Applications in the MVS Environment
Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
Author: The Complete Guide to SAS Indexes