An Idea Exchange for SAS software and services

by Super User
on ‎05-15-2017 10:32 AM

If I could vote down on a suggestion I would.


If any user can break a lock that another user has then chaos will likely result in many forms.


I would suggest if your organization has this problem often to diagnose why and address the program/user/business model that is causing this.

by Contributor __KiSi__
on ‎05-15-2017 04:21 PM

@ballardw thanks for the suggestion

but the intention is to release the lock to the dataset that was created by the same user.


by Regular Contributor
on ‎05-15-2017 04:24 PM

@__KiSi__: if you're specifically talking about the EG issue, will it solve your problem to view and close the open dataset(s) in question using Tools >> View Open Datasets?

by Contributor __KiSi__
on ‎05-15-2017 04:33 PM

@paulkaefer in many cases locked dataset wasn't visible via Tools >> View Open Datasets. I know that it's possible for instance to kill the process in order to release the lock but it must be done by admin, not a business user who is working on the preparation of the report.

by Regular Contributor
on ‎05-15-2017 05:05 PM

@__KiSi__: if you don't have the dataset open in any processes, yet a lock remains, this sounds like a bug that should be reported to tech support. See here to open a track.

by Contributor __KiSi__
on ‎05-15-2017 05:10 PM

@paulkaefer good point but it was reported fo tech support.

by Regular Contributor
on ‎05-15-2017 05:12 PM

@__KiSi__: did tech support respond? what did they say?

by Contributor __KiSi__
on ‎05-15-2017 05:14 PM

@paulkaefer the same as I wrote before: to kill that session in order to release the lock.

by SAS Employee Casey_SAS
on ‎06-09-2017 10:18 AM
Status changed to: Under Consideration

We are looking for a better solution to the "lock is not available" message that you'll currently get in these situations. It will not involve breaking locks on datasets as the risks of allowing this would create far more problems that it might solve. One of the thoughts is to generate a more descriptive message, displaying the information about the lock - would that be an improvement from your perspective if you knew additional infromation about the lock?

by Contributor __KiSi__
on ‎06-09-2017 05:04 PM

@Casey_SASyes, the more descriptive information about the lock rather than generic "lock is not available" will be good idea. A lot of non-technical people are working with EG on daily basis. IMHO it will be good to inform them not only about the problem but also a potential solution (for instance contact your SAS Administrator). As we know this error (the lock on dataset) can prevent data step before overriding etc. but for these people can be blocker.


Idea Statuses
Top Liked Authors