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.

SAS Innovate 2025: Call for Content

Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!

Submit your idea!

SAS Enterprise Guide vs. SAS Studio

What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

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