Date: Sun, 6 May 2001 12:24:02 -0700
Reply-To: kmself@IX.NETCOM.COM
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Karsten M. Self" <kmself@IX.NETCOM.COM>
Subject: Re: unix work directory:
In-Reply-To: <3AF57B43.96AB70FA@wubios.wustl.edu>; from aldi@WUBIOS.WUSTL.EDU
on Sun, May 06, 2001 at 11:26:44AM -0500
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
on Sun, May 06, 2001 at 11:26:44AM -0500, Aldi Kraja (aldi@WUBIOS.WUSTL.EDU) wrote:
> Hi,
>
> I am running a program in many loops. I save the results as permanent
> data sets or as *.lst.
> To delete the temporary datasets, Although I have used in many places
> the:
>
>
> proc datasets lib=work;
> delete <specific_sas_datasets_names>;
>
> I am thinking that a general one in the start of the new loop would do
> the work:
>
> proc datasets lib=work kill memtype=data nowarn;
>
> Now my questions are:
> 1. If I am working in a shared unix env., does this kill deletes the
> temporary data created from other programs running parallel with this
> one, or sas in a sastmp directory creates a work dir for each program
> individually? Is there any difference in principle between the 6.12 and
> 8.01 versions?
No. Your WORK directory is specific to your current SAS job. Other
jobs and other users will be unaffected.
> -----Directory-----
>
> Libref: WORK
> Engine: V612
> Physical Name: /sastmp/SAS_worka00003A8C
> File Name: /sastmp/SAS_worka00003A8C
>
> 2. Are the sasmac and sascatalog specific to this program or they are
> shared with other programs? So, if I leave out the memtype=data, would
> this delete the macro variables and macro functions created temporary
> from other parallel running programs?
> TIA,
> Aldi
No.
>
>
> --
--
Karsten M. Self <kmself@ix.netcom.com> http://kmself.home.netcom.com/
What part of "Gestalt" don't you understand? There is no K5 cabal
http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org
[application/pgp-signature]
|