SAS dataset locked

[Leo9]

Hi All,

I am sure this topic has been discussed multiple times in this forum but I couldn't find good solution after going through different posts. I work in a shared environment where many different programmers work at same time. We have many users trying to look at data and when a programmer is trying to update the dataset they get the dreaded  dataset is locked error. We work in windows SAS environment. 

Is there any solution ? Ideally we would like to update the SAS dataset even if it is opened by another user. 

[Kurt_Bremser]

Since you run your SAS on a glorified XBOX instead of a real operating system, this will not be possible.

You might manage to do it if you create a view for the dataset and have the users use the view only, but I am not sure about that.

Or you instill discipline on your users to not keep datasets open.

PS on a real operating system (read: UNIX), one can remove a directory entry for a file that is in use. My paper for this year's Global Forum dealt with that.

[Cynthia_sas]

Hi:
When a dataset is locked by another user, you would not be able to update the file. There are products like SAS/SHARE that allow concurrent access to data and concurrent updates. You'd need to check with your SAS Administrator whether that was an option. Other products have ways for concurrent access/updates through the use of metadata permissions, but again, you'd need to check with your SAS Administrator whether your data was secured by the appropriate permissions to do what you want to do.
Cynthia

[Leo9]

Thank you. Could you please provide more information regarding metadata solution ? I work for very small company with IT having very little clue about SAS and its administration. 

[Cynthia_sas]

Hi:
Your best resource for help is to open a track with Tech Support. There's no simple or quick answer to this question. How to establish the ability for concurrent access and updates will depend on your system components and the security settings.
Cynthia

[SASKiwi]

I suggest you check out the FILELOCKWAIT option on the LIBNAME statement. If you carefully manage your SAS processes updating the dataset being locked so that it is only locked for a few seconds then this option can be very useful. However if users have a habit of viewing this dataset in a SAS Table Viewer then that could lock the dataset for hours - until they close the viewer window. To avoid this type of behaviour, having a process that creates a temporary copy of the dataset for viewing purposes is useful.  

[AllanBowe]

To avoid the lock, you need to:

• Use clients for viewing that don't lock the dataset (such as SAS Studio, Data Controller, or build your own web interface)
• Set read only permissions to prevent the lock (in this case you may need to run updates using a batch account, or as a Stored Process / Job Execution service
• Switch to a library engine that supports concurrent read/writes, ie, a database.