Date: Sun, 1 Apr 2001 14:43:22 -0700
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Karsten M. Self" <kmself@IX.NETCOM.COM>
Subject: Re: How to continue the sas batch job after is suspended:
In-Reply-To: <3AC77EA6.5E7A83F8@wubios.wustl.edu>; from aldi@WUBIOS.WUSTL.EDU
on Sun, Apr 01, 2001 at 02:16:54PM -0500
Content-Type: multipart/signed; micalg=pgp-sha1;
on Sun, Apr 01, 2001 at 02:16:54PM -0500, Aldi Kraja (aldi@WUBIOS.WUSTL.EDU) wrote:
> During the night the server in a specific account ran out of space.
> Running a sas in batch mode in Unix under Solaris 8, I reached to clear
> some hard drive, in mean time that sas was waiting me to respond on one
> of many
> choices. When I was sure that I had space available, I selected N-do
> nothing, thinking that this was the choice of continue, but I find that
> sas suspended the work.
> Here is what the system responds when checking the job:
> + Suspended(signal) <and the name of the work>
> Can someone advise how to continue the work? I did a search on SAS site,
> but did not find the right response.
How are you launching your SAS job? If it's something like:
$ sas myprog.sas &
...then you can monitor it with the 'jobs' command in most shells (korn,
POSIX, csh, tcsh, bash). If the job is stopped awaiting "tty input"
(e.g.: user response -- typically what SAS tells you when it gets hung
up over some resource or emotional problem), you'll want to bring it to
the "foreground" with the 'fg' command. You should then be able to
direct your program as to what it should do.
Personally, I prefer to completely detach my batch SAS process by
submitting them to the 'at' or 'batch' queues:
$ echo 'sas myprog.sas' | batch
$ echo 'sas myprog.sas' | at <time specification>
Karsten M. Self <firstname.lastname@example.org> http://kmself.home.netcom.com/
What part of "Gestalt" don't you understand? There is no K5 cabal