Date: Tue, 10 Dec 2002 08:56:52 -0600
Reply-To: "Suzanne D. McCoy" <smccoy@LUCIDAN.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Suzanne D. McCoy" <smccoy@LUCIDAN.COM>
Subject: Re: Macro Variables: Deleting
Content-Type: text/plain; charset=iso-8859-1
> It might be simpler to start a new session
> If you want to go down new-ish methodologies
> .... and have sas/connect available.....
> you might put each of these "SAS program" tasks
> into a sas/connect "remote" session which is just
>starting another sas session on your platform.
> Then with connectwait=NO, you can sit back and watch
> (with command rdisplay) your system perform
> multiple sas jobs concurrently !
> Using this sas/connect methodology knowmn as MPconnect
> is a lot more interesting than trying to "clean" your current
> environment of not only those macro variables but also
> macros, formats and perhaps other, more or less-obvious,
> global options.
> Good Luck
> Peter Crawford
> Datum: 05/12/2002 18:49
> An: SAS-L@LISTSERV.UGA.EDU
> Antwort an: David Friedman <harrypotterdhf@EARTHLINK.NET>
> Betreff: Macro Variables: Deleting
> I have the need to run multiple SAS programs. Everytime I run I want to
> make sure that all macro variables are cleared out in the pool. How
> would I accomplish this.
Clear _all_ does a reasonable job of reseting most macro variable values.
If you use keyword parameters and fill them in dynamically, you can
completely control the values that are being submitted. Then you could
submit each program to the batch processor via a X command without running
MP Connect definitely has it's uses and I employ it to speed up processing,
however, it can be difficult to debug. If a session just hangs there and
you kill it, you will NOT get a log that lets you know where it hung at.
It is also very easy to run into dataset contingencies with MP Connect,
expecially if using permanent format catalogs.
Suzanne D. McCoy
Lucid Analytics Corp.
A SAS Alliance Partner