Date: Fri, 7 Jan 2011 13:15:41 -0500
Reply-To: Tom Abernathy <tom.abernathy@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Tom Abernathy <tom.abernathy@GMAIL.COM>
Subject: Re: Sas File Locking
On Fri, 7 Jan 2011 18:32:32 +0100, Allen Ziegenfus <aziegenfus@GMAIL.COM>
>4. Today I found the Unix-LIBNAME Optionfilelocks=none. Apparently with
> option SAS does not create any locks at all. My idea was to combine this
> option withaccess=readonly for EG-clients to prevent any conflicts. This
> seems to work, but I don't know if it has any other negative effects.
> libname test"/unix_path/blah_blah"filelocks=noneaccess=readonly;
>I would expect there to be an option that would just prevent these
> read-locks, but still create the normal write locks. But I have not found
> this option.
One method I have used is to use a different libref for writing.
libname mydata 'path' access=readonly;
libname wmydata 'path' ;
This makes it much less likely that a missing semi-colon will overwrite
your permanent datasets.