Date: Sat, 21 Jan 2006 10:51:48 -0500
Reply-To: Hari Nath <hari_s_nath@YAHOO.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Hari Nath <hari_s_nath@YAHOO.COM>
Subject: Re: Issue a message window if there is an error in the log
Content-Type: text/plain; charset=ISO-8859-1
Thanks Stephane and Art for your answers.......I went through the pdf
paper sent by Art and it looks like proc mixed is an exception along with
some other procs....now i see the problem.....
On Sat, 21 Jan 2006 15:26:32 +0100, Stéphane Colas <saslist@DATAMETRIC.FR>
>You can use the value of SYSERR as a condition to determine further
>take or to decide which parts of a SAS program to execute.
>SYSERR can contain:
>0 Execution completed successfully and without warning messages.
>1 Execution was canceled by a user with a RUN CANCEL statement.
>2 Execution was canceled by a user with an ATTN or BREAK command.
>3 An error in a program run in batch or non-interactive mode caused SAS
>enter syntax-check mode.
>4 Execution completed successfully but with warning messages.
>>4 An error occurred. The value returned is procedure dependent.
>warning is 4.
>Selon Hari Nath <hari_s_nath@YAHOO.COM>:
>> Hi all,
>> When i have errors in my log, &syserr condition works well and
>> if there are any errors. But is there any similar way for checking the
>> output with WARNINGS, because syserr doesnt recognize warnings.....Are
>> there any other fixes for this........