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 (July 2005, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Fri, 8 Jul 2005 02:16:23 +0000
Reply-To:   toby dunn <tobydunn@HOTMAIL.COM>
Sender:   "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:   toby dunn <tobydunn@HOTMAIL.COM>
Subject:   Re: Capturing SAS exit code (error code) using Ultraedit
Comments:   To: davidlcassell@MSN.COM
In-Reply-To:   <BAY103-F1542C7AD83468E7055064EB0DB0@phx.gbl>
Content-Type:   text/plain; format=flowed

David,

Lets not forget that one can abort a program and give it it's own special exit code. I have done this in the past with prduction code.

Toby Dunn

From: DavidL Cassell <davidlcassell@MSN.COM> Reply-To: DavidL Cassell <davidlcassell@MSN.COM> To: SAS-L@LISTSERV.UGA.EDU Subject: Re: Capturing SAS exit code (error code) using Ultraedit

awinter@INFORMA.DE wrote: >I am trying to evaluate Ultraedit as a replacement for Textpad which we >have been using as a SAS(8) editor. > >So far everything works fine: Syntax highlighting, Invokation of SAS Jobs, >generation of log-File and lst-File. > >The only thing which does not work is capturing the SAS exit code: In >textpad a window pops up indicating error (exit-) code 2 or 1 if the job >terminated with an error or a warning. This is quite nice so we donīt have >to check the log for errors if there are none. > >So far I have not been successful to capture the exit code in Ultraedit. I >have noticed (and tried) the several options in the Toolbox settings but >nothing has worked so far. > >Is there anyone who has a solution for this? > >(In SAS-L I have found several threads concerning Ultraedit but I havenīt >seen one covering exit codes) > >Thanks for your help, >Arnd Winter (Pforzheim, Germany)

I'm sure there's been at least one SAS-L thread on exit codes, because I remember writing about the *other* exit codes. Yes, there are more than 1 for warning and 2 for error.

More importantly, you can have a job which fails horribly, and still returns a 0, as long as the problem is showing up in a NOTE instead. There have definitely been a lot of threads on logfile checkers, and many of the keyphrases that get searched for in these checkers are not phrases from ERROR and WARNING messages. You really do need to search the log, whether you get a pop-up about '1' and '2' exit codes or not.

HTH, David -- David L. Cassell mathematical statistician Design Pathways 3115 NW Norwood Pl. Corvallis OR 97330

_________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


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