>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
>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
>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
>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
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
Regardless of the size of the data set, I thinkthe problem is going to be
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
is cranking out lots of SASgoop. I'm going to recommend that you re-design
process. Take the massive macro out and re-write your code. Things ought
a lot faster too, which will make your life better.
Trying to fix the amount of generated output is not a good approach, if
should not be that much output in the first place. Perhaps you could write
and explain *why* you have such a massive macro and so much output, and
maybe someone could suggest alternatives to simplify your process, your
your life, ...
David L. Cassell
3115 NW Norwood Pl.
Corvallis OR 97330
Donít just search. Find. Check out the new MSN Search!