Hi, I have seen several different methods when analyzing logs. My personal preference is to have a separate utility which you can drop a log onto and that provides a report on errors/warnings/notes found. Note this is a custom built tool I wrote however you could do something similar in SAS. I built a small .NET app which you can drag text files onto the icon and it will scan them for known issues from another text file. You could wrap each procedure up in some additional code to check the outcome, but its a bit a of work and is it really worth the effort when you can just check the output log. If your running interactively then run each step individually, if you run the whole program direct logs to a file then scan that file (this would also go further if your automating things, then the log could be automatically scanned). Also, you need to be clear on what you are looking for as its not only errors/warnings which could trip you up, there are logical errors and some notes could also impact.
... View more
