BookmarkSubscribeRSS Feed
SASPhile
Quartz | Level 8

I'm getting the error "ERROR: A lock is not available for". I closed the session and re-started , yet this error comes. I'm using windows environment and submitting batch jobs. 

 

4 REPLIES 4
Astounding
PROC Star

The typical scenario:  it takes patience. 

 

One batch job is using the data set, while another batch job wants to use the data set.  If one of the batch jobs wants to change the data set (for example, running PROC SORT on a permanent SAS data set), it is not possible for both batch jobs to access the data set at the same time.

 

Your programming style can have some impact here.  For example, if you add OUT= to your PROC SORT, then that step doesn't need to tie up the data set.  But in a large number of cases, patience is a virtue.

SASPhile
Quartz | Level 8

1. How to know what processes are running?

2. How to kill the processes on windows?

Astounding
PROC Star

Sorry, I don't have answers for that on Windows.

Kurt_Bremser
Super User

@SASPhile wrote:

1. How to know what processes are running?

2. How to kill the processes on windows?


If you want to make your life easier, can the toybox and switch to a real operating system. At the moment, this means UNIX.

 

I work on a UNIX platform, and on such this is a non-issue, as I can easily remove links to files (aka "directory entries") from the filesystem while a process is still using the file. That is because UNIX systems have a different concept of filesystem structure that is lightyears ahead of the much-too-simple method that Windows has.

sas-innovate-2024.png

Available on demand!

Missed SAS Innovate Las Vegas? Watch all the action for free! View the keynotes, general sessions and 22 breakouts on demand.

 

Register now!

Mastering the WHERE Clause in PROC SQL

SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.

Find more tutorials on the SAS Users YouTube channel.

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