Please provide more information about your situation.
Like, what kind of processing are you doing (program logic), what engine is used, what is the nature of your SAS environment (ways to access data, SAS servers etc), host OS etc.
depending on the features of your scheduling sw, you cold try to issue an OS command to list the actual processes that is locking any particular file right after the job abends.
Data never sleeps