11-28-2013 05:56 PM
In addition to Tom's advice, it might be worth trying to figure out why the log is so large.
When I get "log full" type problems, it usually turns out to be because something in my program is generating a very large number of notes/warnings. For instance, if I'm doing something that generates a note at every observation of a 2-million-observation file, that will choke up the log very quickly. One way to identify this is to run the program on a smaller data set so that I can look at the log and see what's taking up the space. If I can identify a step that's spamming the log, I can then fix that problem without needing to shut off logging altogether.
11-28-2013 06:30 PM
If you submit the program as a background or batch job then you will not get those messages. If you really have a long running job then that is how you should be submitting the code anyway. That said you should still look into WHY the job is generating such a large log file.
11-28-2013 11:26 PM
Hi Thomas. Thanks for your guidance,,, Its very helpful. Can you please let me how can i run a .sas file in batch mode. when i m running my programme in cmd prompt its always open SAS programe, and if i create .BAT file it also doing same.
can you please help me .
11-29-2013 03:09 AM
The normal way that I submit SAS programs is to include the filename on the command line when I type the command that starts SAS.
Example: sas myfile
This will look for the code in myfile.sas and write the log to myfile.log and the listing output to myfile.lst. This is how SAS has worked since it was first available on interactive systems.
Now if you are trying to use Windows then it may be harder to invoke SAS from the command line, but when SAS is installed it should create multiple associations into the Windows Registry for .sas files. So if you right click on SAS program file in a Windows Explorer window you should have a choice for Batch submit.
Need further help from the community? Please ask a new question.