Date:         Wed, 7 May 1997 14:32:13 -0800
Reply-To:     Jack Hamilton <Jack_Hamilton@HCCOMPARE.COM>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Jack Hamilton <Jack_Hamilton@HCCOMPARE.COM>
Organization: HealthCare COMPARE Corporation
Subject:      Re: Saving SAS log from program
Comments: cc: dla5@CIDHIV1.EM.CDC.GOV
Content-Type: text/plain; charset=us-ascii

"Alderton, David" <dla5@CIDHIV1.EM.CDC.GOV> wrote:
 
> Folks, occasionally I have some fairly large jobs to run (that take 3-8
> hours) and would like to start them as I walk out the door.  For security
> reasons everyone is logged out by the system at some odd (but late) time
> which means I lose the SAS log and/or the printed output from a job.  I can
> request and receive an exception to the policy which gets me around the
> problem.  However, I know that I can issue a DM command from a SAS job
> (e.g., 'DM clear log') but was unable to figure out how save the log and/or
> output.  Ideally, I would like to run the job, save the log, save any
> output, then terminate SAS to clean up the temp files.  Any suggestions?
 
Someone else has already suggested using the ALTLOG and ALTPRINT
options;
that's probably the easiest way to do it.  They can go in your
CONFIG.SAS
file, or on the command line (in the SAS icon in Windows).
 
I *always* use ALTLOG=.  It has saved me a lot of work when SAS or the
LAN has crashed before I have saved my work.  I can edit the LOG file
and extract my SAS code.  The file is overwritten each time I start SAS,
so I don't have to worry about cleaning it up.
 
-----------------------------
Jack_Hamilton@HCCompare.com
HealthCare COMPARE Corp.
West Sacramento, CA