BookmarkSubscribeRSS Feed
Citrine10
Obsidian | Level 7

Hi there

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?

3 REPLIES 3
LinusH
Tourmaline | Level 20

Take a look at the LOCK statment.

If this is a frequent thing you might want to look into

  • Throw out SAS sessions (works if you have a server only libref)
  • Move your data to a multi user engine (SAS/SHARE, SAS SPD Server or external RDBMS)
  • If your users uses EG make sure they upgrade to the latest release, where locks are released from data sets automatically.
Data never sleeps
SASKiwi
PROC Star

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.

hackathon24-white-horiz.png

2025 SAS Hackathon: There is still time!

Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!

Register Now

Creating Custom Steps in SAS Studio

Check out this tutorial series to learn how to build your own steps in SAS Studio.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 3 replies
  • 1322 views
  • 0 likes
  • 4 in conversation