To tell you the truth, I wouldn't recommend reducing the log size at all. It contains useful information. You can turn off the macro debugging tools once you have finished debugging.
I would print the log to a file, and then the size is mostly irrelevant and it can be viewed by any text editor (which of course allows you to search for errors). Example:
proc printto log="c:\yourfolder\whatever\program12.log" new; run; /* Your SAS code goes here */ proc printto; run;
Which particular entries in the log are offensive?
Are you using PUT statements? - Remove them or comment them out.
How large is your log that you find too big? 100 lines? 1000 lines? 100K lines?
How many lines of code are in your program? Generally if your program doesn't have any errors you typically get about 5 or 6 lines per procedure or datastep more than the actual code submitted. If you are getting much more than that I would say that you likely have problems with data or code than need to be addressed but would have to see examples with code and possibly data of where to start.
Nocenter, nodate and nonumber only affect output pages so have zero impact on log size.
I use proc export and it created lots of lines
Unless you have thousands of variables, this should not be a problem. You can reduce the size of such export code considerably by writing the step yourself and omitting unnecessary statements.
Registration is open! SAS is returning to Vegas for an AI and analytics experience like no other! Whether you're an executive, manager, end user or SAS partner, SAS Innovate is designed for everyone on your team. Register for just $495 by 12/31/2023.
If you are interested in speaking, there is still time to submit a session idea. More details are posted on the website.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.