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 (June 2006, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 8 Jun 2006 03:02:51 -0700
Reply-To:     chris@OVIEW.CO.UK
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         chris@OVIEW.CO.UK
Organization: http://groups.google.com
Subject:      Re: Watch out for SAS keeping old data in memory while running
Comments: To: sas-l@uga.edu
In-Reply-To:  <BAY103-F35996981EE1B2E3FD338D6B08B0@phx.gbl>
Content-Type: text/plain; charset="iso-8859-1"

A technique I have used is to run programs via a wrapper script, eg

$ runsas my_program

instead of

$ sas my_program

The wrapper invokes SAS to run the program and then checks the return code, creating an empty file called "my_program.clean", "my_program.warnings" or "my_program.errors", as appropriate (it must also delete any of those files which exists before running the job, of course). It is then immediately obvious when looking at the content of the directory, in Windows Explorer or whatever, which programs have run clean and which haven't. This is very useful when re-running hundreds of individual programs overnight etc.

I haven't got the actual code handy at the moment, but can post it later if anyone's interested...

Chris. -------------------------------------------------------- Elvis SAS Log Analyser - http://www.oview.co.uk/elvis --------------------------------------------------------

David L Cassell wrote:

> The way to look for errors and warnings (and plenty of NOTEs that may > signify serious problems with your particular data processing problem) > is to use a log checker or log parser and do it in an automated fashion. > Looking through large logs by hand is too prone to error. There have > been lots of SAS-L threads on 'log checker' or 'log parser' and you can > glean valuable information by searching the SAS-L archives for these > key-phrases. > > HTH, > David > -- > David L. Cassell > mathematical statistician > Design Pathways > 3115 NW Norwood Pl. > Corvallis OR 97330 > > _________________________________________________________________ > Don't just search. Find. Check out the new MSN Search! > http://search.msn.click-url.com/go/onm00200636ave/direct/01/


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