Date:         Fri, 16 Jul 2010 10:00:49 -0400
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: update a dataset in use by other people
Content-Type: text/plain; charset=ISO-8859-1

Can you make it so that normal users access the library with READONLY
access and only the process/user with permission to update the files should
create a libref with write access.  In a normal LIBNAME statement you can
add the ACCESS=READONLY option, not sure how that would translate to SPDS.

And if you do does it make it easier to update the files while users are
trying to read them?

You could also just try Michael's trick of looping until you can get a lock
by using the function to open the dataset instead of the function to open a
file to test for access.


On Fri, 16 Jul 2010 09:17:03 -0400, Dee Karmaoui
<dkarmaoui@BUSINESSDECISION.CO.UK> wrote:

>Sadly - and I should have mentioned it - this is a SPDS table
>
>for anyone not familiar with SPDS:
>SPDS stores tables in multiple different locations. You have one piece of
>metadata, and then a piece of data etc.
>The idea being that SPDS data is stored in multiple places, say 10, with
>each chunk of data being a specific size, say 1GB.
>If you have a table of 2GB in size, you’ll end up with a metadata file, a
>1GB chunk of data in path1 and a 1GB piece of data in path2, this will
>continue until the data is all written.
>All that gumph means you can’t reference it in reality though. What should
>happen is the XYZ library is available to all your SAS sessions, as it’s
>pre-assigned when the session starts.
>
>Thanks for your help though Michael, I'm definitely saving that code for
>later use! :)
>
>