https://communities.sas.com/t5/SAS-Enterprise-Guide/exception-handling-for-SAS-ERROR-A-lock-is-not-available-for/m-p/790865#M40170 <P>Take a look at the LOCK statment.</P> <P>If this is a frequent thing you might want to look into</P> <UL> <LI>Throw out SAS sessions (works if you have a server only libref)</LI> <LI>Move your data to a multi user engine (SAS/SHARE, SAS SPD Server or external RDBMS)</LI> <LI>If your users uses EG make sure they upgrade to the latest release, where locks are released from data sets automatically.</LI> </UL> Wed, 19 Jan 2022 12:34:22 GMT LinusH 2022-01-19T12:34:22Z https://communities.sas.com/t5/SAS-Enterprise-Guide/exception-handling-for-SAS-ERROR-A-lock-is-not-available-for/m-p/790862#M40169 <P>Hi there</P><P>We have jobs scheduled that run on Flow Manager and alot of them exit because of the ERROR: A lock is not available for xxxxxx. Is there a way to solve for this using some SAS code so that the code can retry to run?</P> Wed, 19 Jan 2022 12:08:55 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/exception-handling-for-SAS-ERROR-A-lock-is-not-available-for/m-p/790862#M40169 Citrine10 2022-01-19T12:08:55Z https://communities.sas.com/t5/SAS-Enterprise-Guide/exception-handling-for-SAS-ERROR-A-lock-is-not-available-for/m-p/790865#M40170 <P>Take a look at the LOCK statment.</P> <P>If this is a frequent thing you might want to look into</P> <UL> <LI>Throw out SAS sessions (works if you have a server only libref)</LI> <LI>Move your data to a multi user engine (SAS/SHARE, SAS SPD Server or external RDBMS)</LI> <LI>If your users uses EG make sure they upgrade to the latest release, where locks are released from data sets automatically.</LI> </UL> Wed, 19 Jan 2022 12:34:22 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/exception-handling-for-SAS-ERROR-A-lock-is-not-available-for/m-p/790865#M40170 LinusH 2022-01-19T12:34:22Z https://communities.sas.com/t5/SAS-Enterprise-Guide/exception-handling-for-SAS-ERROR-A-lock-is-not-available-for/m-p/790869#M40171 <P>If your backend runs on a UNIX system, consider my method to remove the target dataset before writing to it, as presented in my <A href="https://communities.sas.com/t5/SAS-Global-Forum-Proceedings/How-to-Deal-With-Locked-Data-Sets-on-UNIX-systems/ta-p/726339" target="_blank" rel="noopener">SASGF 2021 paper</A>.</P> Wed, 19 Jan 2022 12:42:07 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/exception-handling-for-SAS-ERROR-A-lock-is-not-available-for/m-p/790869#M40171 Kurt_Bremser 2022-01-19T12:42:07Z https://communities.sas.com/t5/SAS-Enterprise-Guide/exception-handling-for-SAS-ERROR-A-lock-is-not-available-for/m-p/793047#M40198 <P>Are your jobs trying to update the same datasets and the same time or are other users locking them? If the updating is all under your control then there are SAS options like FILELOCKWAIT that may be helpful.</P> Fri, 28 Jan 2022 00:59:06 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/exception-handling-for-SAS-ERROR-A-lock-is-not-available-for/m-p/793047#M40198 SASKiwi 2022-01-28T00:59:06Z