LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (July 2002, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 12 Jul 2002 10:05:12 -0400
Reply-To:     Dianne Rhodes <RHODESD1@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Dianne Rhodes <RHODESD1@WESTAT.COM>
Subject:      Re: automated log-checking
Comments: To: Quentin McMullen <QuentinMcMullen@WESTAT.com>
Content-Type: text/plain; charset="iso-8859-1"

Quentin said:

>One issue I hadn't really considered was how log-checking >should detect >user-generated error messages. > Following a discussion of the use of

If cond then error ; or

If cond then _error_ = 1;

Q, I think both statements are doing the same thing, that is setting the automatic variable, _error_ to True or 1.

IMHO they should be treated the same as any other ERROR; the author needs to evaluate them and decide if they are problems.

What about when _error_ is set back to 0?

_error_ = 0 ;

I have done that in a program where I had known bad data and did not want to see the errors written to the log.

Dianne Louise Rhodes Sr. Systems Analyst Westat

>


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