Date:         Thu, 14 Jun 2007 17:41:04 -0700
Reply-To:     David L Cassell <davidlcassell@MSN.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         David L Cassell <davidlcassell@MSN.COM>
Subject:      Re: Suppress Log Printout at Macro Level
In-Reply-To:  <200706140506.l5E4hjng010778@mailgw.cc.uga.edu>
Content-Type: text/plain; format=flowed

tythong@YAHOO.COM wrote back:
>
>Thanks guys!
>
>I have already confirmed the correct SAS code


But you have no guarantee that *something* will never go wrong.

Keep the log.

If you don't, then you'll never be able to prove that a result your boss
doesn't like is real, and not due to some error you threw out.

If you don't, then you'll never find that rare unfortunate error that mucks
everything up.

If you don't, ...


>                                   but I have to clear the log
>window when all the statements fill up the window.  So, I am thinking to


You have a fundamental issue here, but first let me point out that there
is no reason why you have to run this code in Display Manager.  Run it in
batch mode!  Your log and output will go straight to a file!

Or at least use PROC PRINTTO to re-direct your log.


>suppress the log printout.  I am using Windows SAS version 9.
>
>Thanks again & cheers,
>Thomas

I am going to predict that you are running a large simulation or bootstrap.
And that you are running it in a huge, icky macro loop.

Is that what is really going on?  I think that the *real* problem is
upstream,
namely that you should re-design your process so it is not a vast macro
loop,
but instead uses SAS processing abilities to run faster, cleaner, easier,
...


"We can rebuild him.. make him better than before..."  :-)

David
--
David L. Cassell
mathematical statistician
Design Pathways
3115 NW Norwood Pl.
Corvallis OR 97330

_________________________________________________________________
Don’t miss your chance to WIN $10,000 and other great prizes from Microsoft
Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/