While I'm not a fan on such inconsistencies, this is not a new one. A
search of SAS-L archives shows that the message:
ERROR 180-322: Statement is not valid or it is used out of proper order.
Goes back at least to 1994. So this bug might have been biting folks
already. My current log checker looks at each line, grabs the first word
(using space and : as delimiter) and keeps it if it is NOTE WARNING or
ERROR. It seems to work reasonable well. Seems to me there may be some
other messages I've missed (is it possible to get an error message
starting with "FATAL" which does not also produce another standard ERROR
message, or at least a WARNING?)
On Thu, 3 Jun 2004 12:38:01 -0700, Pardee, Roy <pardee.r@GHC.ORG> wrote:
>Good thing it's got the regexes we'll need to find 'ERROR' ocurring
>before digits, eh? 8^)
>From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of SAS
>Sent: Thursday, June 03, 2004 11:49 AM
>Subject: Re: Log checkers, new ERROR: style in v9 ?
>A simple task (looking for "ERROR:") just got a lot harder
>Thanks SAS, thanks a lot
>"Richard A. DeVenezia" <firstname.lastname@example.org> wrote in message
>> I am unfamiliar with this apparently new style of error message. ERROR
>> nnn-mmm: <error message>
>> Be sure to update your log checking macros to look for this new
>> 1 data _null_;
>> 2 declare hash h1;
>> 3 declare hash h1;
>> ERROR 567-185: Variable h1 already defined.
>> 4 run;
>> NOTE: The SAS System stopped processing this step because of errors.
>> NOTE: DATA statement used (Total process time):
>> real time 0.03 seconds
>> cpu time 0.00 seconds