Date: Fri, 30 May 1997 22:28:47 -0600
Reply-To: "Raymond V. Liedka" <liedka@UNM.EDU>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: "Raymond V. Liedka" <liedka@UNM.EDU>
Subject: Re: Underground SAS on Unix -Reply
In-Reply-To: <m0wN7LF-0000XBC@crux.unm.edu>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Well...
This is a little late, but there might still be some interest.
I had indicated in a posting that running a job in the background with
the ampersand (typing at the prompt: sas jobname & ) would allow one
to log off. Several helpful folks indicated that while that does set a
job running in the background, the job would end execution when I logged
off.
Well..it turns out that for the modified C-shell (sinified by "tcsh" rather
than just "csh") it seems that running a job in the background DOES allow you
to logout without interruption. I tested this yesterday by running a SAS
program that does bootstrapping of a CALIS analysis. First, the macro
estimates the model on the actual data, saves the output var-covar matrix,
reads that into IML and uses SVD to then generate lots of bootstrap samples,
catenating them into a single matrix with boot id, then creates a SAS dataset
from it with the "create" IML command. Then, the macro fits the CALIS model
to each of the generated bootstrap samples and saves the results from
each into a dataset that grows with each iteration, finally saving it
permanently to disk. I ran it to generate 200 bootstrap samples, and ran
it in the background. I immediately logged out, and checked back about
30 minutes later, the job had finished and created a final dataset with
200 records in it.
So it would seem that this is an advantage of the modified C-shell.
Apparently, another is that you get step up/step down control over the
command history using the up and down arrow keys (I like this perk!).
later...
ray
Raymond V. Liedka
Department of Sociology
University of New Mexico
| 
