An Idea Exchange for SAS software and services

Comments
by Super User
on ‎03-27-2015 08:32 AM

Since the SASFILE mechanism enables certain write operations, the file is locked accordingly.

I don't expect this to be changed.

A workaround for this is to use the operating system's functions to delete the file at the OS level (the user who has opened it will still see "his" version as the inode and data remain until closed) and then create the dataset.

by Contributor AndrewZ
on ‎03-27-2015 12:07 PM

KurtBremser: I am suggesting a new option that trades write operations for releasing the lock.

Based on "inodes," it sounds like you are using Linux, but Windows does not allow a locked file to be deleted.

by Super User
on ‎03-30-2015 04:58 AM

It still would not be a solution for your problem. If users are inconsistent in unloading the loaded datasets, they also cannot be expected to use the new option reliably, leaving you back at square one.

(If Windows is your problem, switch to a real OS that helps you out instead of getting in your way.)

Idea Statuses
Top Liked Authors