topic Re: check the log quickly in Advanced Programming

check the log quickly

CorinneT — Wed, 13 Oct 2021 15:54:21 GMT

Hi,

1) Could somebody tell me how to check quickly the LOG? Please an other way as: CTLF+F=error or warning....

2) Do the statement PUTLOG deals with it? Please, If yes, could you tell me how it runs.

Thanks in advance for all answers.

Regards,

Corinne

Re: check the log quickly

japelin — Wed, 13 Oct 2021 16:21:42 GMT

1)try this
type F9, select key and set "log; find 'ERROR:'" to Definition field.
close keys.
Then, type short cut key.
you will able to search keywords "ERROR:";

You need to set "find WARNING" to other key, though.

2)Putlog will always just put in the log window.
It will be easier to understand if you run the following code.

/* put statement */
data _null_;
  set sashelp.class;
  put name;
run;

/* putlog statement */
data _null_;
  set sashelp.class;
  putlog name;
run;


/* put statement with file statement */
filename tmp temp;
data _null_;
  set sashelp.class;
  file tmp;
  put name;
run;

/* putlog statement with file statement */
filename tmp temp;
data _null_;
  set sashelp.class;
  file tmp;
  putlog name;
run;

Re: check the log quickly

Reeza — Wed, 13 Oct 2021 16:20:22 GMT

If you're using Studio or EG there is a summary of the log at the top with the number of ERRORS, NOTES and WARNINGS found in the log.

Re: check the log quickly

CorinneT — Wed, 13 Oct 2021 20:35:49 GMT

Yes, thanks I know. But I use SAS base 9.4 😞

Re: check the log quickly

CorinneT — Wed, 13 Oct 2021 20:38:31 GMT

ok, thanks.

Re: check the log quickly

Quentin — Wed, 13 Oct 2021 22:38:39 GMT

Hi,

If you want to dig deeper, I'd suggest visit lexjansen.com and search for log scanners / log parsers. There are lots of papers by people who wrote macros to make it easier to scan a log (or a directory full of logs), and return a list of errors, warnings, and bad notes.

One of my favorite papers is 20 years old, but worth a read:

https://www.lexjansen.com/nesug/nesug01/cc/cc4008.pdf

They make an excellent recommendation that when looking for bad notes, it's safer to define a list of good notes rather than listing the bad notes. Also, some errors do not start with ERROR:, they start with ERROR ###: where there is a numeric code before the colon. My parser looks for a first line that starts with ERROR WARNING or NOTE, using both space and colon as delimiter.

Re: check the log quickly

CorinneT — Thu, 14 Oct 2021 19:25:52 GMT

Thanks for these tips