Date:         Fri, 19 Mar 2010 00:31:52 -0500
Reply-To:     Joe Matise <snoopy369@GMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Joe Matise <snoopy369@GMAIL.COM>
Subject:      Re: Finding ERRORs in SASLOG
Comments: To: Paige Miller <paige.miller@kodak.com>
In-Reply-To:  <0447a200-788d-44eb-9bb6-a9a271dc8f5b@c16g2000yqd.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1

There is I believe a checkbox "Find whole word only" or somesuch.  Check
that, eliminates _ERROR_ at least (and the proc import SERROR etc.)

Still not a substitute for reading your log.  Lots of 'errors' don't
generate error messages.  :)
-Joe

On Thu, Mar 18, 2010 at 8:14 AM, Paige Miller <paige.miller@kodak.com>wrote:

> When I want to search for ERRORs in my SASLOG, I can of course do a
> search for the test string ERROR in the SASLOG, however sometimes this
> turns up _ERROR_, which really isn't an error, it is written to the
> LOG by a data step (for example, if you divide by zero). In this
> instance, and many similar instances, I'm not really interested in
> finding _ERROR_, but there could be a bazillion of them.
>
> So, next, trying to find actual code ERRORs, I  search for
> 'ERROR:' (without the quotes, but with that colon on the end) which
> helps me find normal code errors, but I also have to search for "ERROR
> ' (without the quotes, but with a space after the last R), which helps
> me find MACRO errors.
>
> Is there a better way to find ERRORs in the SASLOG, skipping the data
> step _ERROR_, and finding both MACRO errors and normal code errors?
>