LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (February 2005, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Tue, 15 Feb 2005 09:00:28 -0800
Reply-To:   "Pardee, Roy" <pardee.r@GHC.ORG>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   "Pardee, Roy" <pardee.r@GHC.ORG>
Subject:   Re: Critical SAS Messages in the log
Comments:   To: Gerhard Hellriegel <ghellrieg@T-ONLINE.DE>
Content-Type:   text/plain; charset="us-ascii"

How about the error you get when you leave a closing double-quote character off a label or format definition value? I don't recall it off top, but that one's easy to provoke...

It'd also be cool if your program could register "expected errrors", for those cases where, e.g., you really do want to do a cartesian product.

I'd personally love it if there were a PROC SQL option you could specify so that it would throw an error rather than "remerge summary statistics blah blah blah". I just about never do that one on purpose...

Cheers,

-Roy

-----Original Message----- From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Gerhard Hellriegel Sent: Tuesday, February 15, 2005 5:36 AM To: SAS-L@LISTSERV.UGA.EDU Subject: Re: Critical SAS Messages in the log

perhaps the macro ones, e.g. "symbolic reference" or "not resolved"

maybe you could also ignore cases. I assume, you read the logs with a utility where you look for your triggers with the index-function. Why not comparing like

if index(upcase(line),upcase(trigger)) then....

On Tue, 15 Feb 2005 13:58:11 +0100, gertrud Thaer <Gertrud.Thaer@BC.BOEHRINGER-INGELHEIM.COM> wrote:

>Dear all, >We plan to use a SAS programs which tests the SAS log for critical >messages. > >This is our current list: >ERROR >WARNING >uninitialized >Invalid >More than one >0 observations >multiple length >Overwritten >FATAL >truncated >MERGE Statement has more than one data set with repeats of BY values > >Or > >repeats of BY values >Division by zero detected >Outside the axis >A missing equal sign has been inserted >Duplicate BY variable(s) specified >is already in the library >At least one W.D. format was too small for the number to be printed >Invalid third argument to function SUBSTR >INFO: The variable >The query as specified involves ordering by an item that doesn't appear

>in its SELECT clause The execution of this query involves performing >one or more Cartesian product joins that can not be optimized. >The query requires remerging summary statistics back with the original data > >Failed to converge >singular > > >Are there further critical messages which we shoul include to our list? > >Best regards >Gertrud


Back to: Top of message | Previous page | Main SAS-L page