LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (February 2006, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Thu, 23 Feb 2006 13:30:03 -0800
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: Hoiw to stopr from printing into output SAS window
In-Reply-To:   <200602232031.k1NIvhZx015363@malibu.cc.uga.edu>
Content-Type:   text/plain; format=flowed

pavlo@INORBIT.COM wrote: >I made this mistake this morning: >I started running my SAS code which is a macro. >The data set has like over a million records and about 100 fields. >I started ruunin the macro like 3 hours ago. It still runs. >Ever so often, I have to babysit this thing because the output window gets >full. >Then I have to press the C button to clear the window so the program can >start running again. >If this thing runs many more hours, I won't be at work to baysit this >thing. >How can I tell SAS to not output all these iterations in the window and >fill it up. >A simple error message (log) will suffice to let me know if the job was >completed correctly. >All this other stuff filling up the windo is a nuisance right now.

I'm going to disagree with everyone. Even Ron. (Hey Ron, is this a first?)

Your problem is likely to be much more fundamental than switching off a few options... Or even using ODS LISTING CLOSE to stop churning stuff to the output window, which won't stop the amount of junk that goes to the log... Or even running your code in batch instead, so the output and log go directly to files instead.

Regardless of the size of the data set, I thinkthe problem is going to be your macro code. I'm looking into my crystal ball, and I am seeing a massive loop around a large SAS process, leading to hundreds - or maybe thousands - of iterations, each of which is cranking out lots of SASgoop. I'm going to recommend that you re-design your process. Take the massive macro out and re-write your code. Things ought to run a lot faster too, which will make your life better.

Trying to fix the amount of generated output is not a good approach, if there should not be that much output in the first place. Perhaps you could write back and explain *why* you have such a massive macro and so much output, and maybe someone could suggest alternatives to simplify your process, your code, your life, ...

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

_________________________________________________________________ Don’t just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/


Back to: Top of message | Previous page | Main SAS-L page