A function to tackle "FILE LOCKING"

[ReNSFW]

Hey Can you confirm that the Sas job is initiated from a .bat?

If so does the .bat set the log location?
If so thats probably what has the log file open. I am wrestling with the same issue atm.

My options (i am yet to investigate) in order of preference is. Disregard lock, find a read only access method, Duplicate then delete.

Hope this helps

[SASKiwi]

If you are using the sasbatch.bat file to execute SAS batch jobs, all this file is doing is calling sas.exe with some options, one of which might be the -LOG option to specify the name and location of the SAS log file. It's the SAS executable that is creating and locking the log file, not sasbatch.  

[ReNSFW]

User said they were using SAS in batch.

[SASKiwi]

There are various ways of invoking SAS in batch mode. You can call the SAS command directly from a command line or via a scheduling tool, run the SAS-provided sasbatch BAT file, or run SAS via a user-written BAT or script file. You will need to provide more details of your problem before we can help.