topic Re: Programmatically check log for error messages? in SAS Health and Life Sciences

Programmatically check log for error messages?

sassygrl — Fri, 02 Nov 2007 15:56:44 GMT

As the subject line says, is there a way to programmatically check the log for error/warning messages?

I'm thinking in terms of a yes/no macro variable, or maybe an option to stop submitting code once there is an error message.

Thanks!

Re: Programmatically check log for error messages?

Doc_Duke — Sat, 03 Nov 2007 03:04:34 GMT

If you save the log to a file, you can search it with grep or using the SAS perl regular expressions. I'm not sure that is what you were searching for, but it works reasonably well in a batch environment.

Doc Muhlbaier
Duke

Re: Programmatically check log for error messages?

deleted_user — Mon, 05 Nov 2007 09:31:34 GMT

In my humble opinion, the best approach by far is to save the log as a file and then parse it for any of the SAS statements that indicate we have wrong data, bad code, system issues or misunderstandings. These can be as simple or as comprehensive as you need.

You might also look up the system macro symbols in the documentation that start with %Sys. These can give you some insight into the success or failure of individual steps.

Kind regards

David

Re: Programmatically check log for error messages?

sassygrl — Wed, 07 Nov 2007 20:26:20 GMT

Thanks to both!

Re: Programmatically check log for error messages?

JasonDiVirgilio — Mon, 28 Jan 2008 22:42:03 GMT

For those using Unix, a shell program like the following could catch common errors:

#!/bin/ksh
if [ $# != 1 ]
then
echo "Usage: mylogchecker.sh "
exit -1
fi

grep -n ERROR ./$1
grep -n WARNING ./$1
grep -in UNINITIALIZED ./$1
grep -in CONVERTED ./$1
grep -in REPEATS ./$1
grep -in 'BY ZERO' ./$1
grep -in UNKNOWN ./$1
grep -in 49-169 ./$1
exit