Hopefully @ChrisBrooks solution works out for you, that's probably the best way to handle this. If not though you can take an approach I've been using for the past several years, which is to output critical data to a separate log file that you control manually. I initially developed a macro that uses the standard file commands (FILENAME, FOPEN, FPUT, FAPPEND, FCLOSE, etc) to write summary text out to a text file when I was working in a very locked down SAS environment, but since then I've found that the approach is incredibly useful even in an open environment. Basically it lets you create a very concise log file with only the exact things you care about seeing in it. I've found it especially useful when dealing with extremely long programs where I can monitor the progress a lot easier. Recently I also modified my version of this code so that in addition to outputting data to a secondary log file, it also prints it's output directly to the command line so you can follow the progress of a batch program in real-time without even needing to open a separate file.
... View more
