Meh. If it was me I'd do up a script to act as the controller. That
way you don't have to rely on the humans (too much) to clean up after
But different strokes for different folks...
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Lou
Sent: Tuesday, June 06, 2006 7:14 PM
Subject: Re: Watch out for SAS keeping old data in memory while running
""Pardee, Roy"" <pardee.r@GHC.ORG> wrote in message
> Another way to go is to just always run in batch mode. You can do >1
> thing at a time then, and the log file documents exactly what
So, there are projects where a team of programmers can spend a few
months writing a couple hundred programs, and when it comes time to
deliver, they all have to be run, there are dependencies so things have
to run in a specific order, and the whole thing might take several
hours. We control that by writing a control program that basically
consists of a series of %INCLUDE statements, and whether the thing is
run in batch or interactively, it's all one SAS session. Heaven help
you if something you've done screws up someone else's piece of the job.
You'll be the one there at midnight trying to fix things after everyone
else has gone home at 5. It's not only a many of politeness, it's
enlightened self interest - clean up after yourself.