Hi, I have a solution for this. 1) check for the .lck file for the sas dataset, if it exists then it is currently being updated so do not try and unlock it. 2) if no .lck file exists, you can OS move(rename) the dataset file(s) including indexes and then copy them back to their original names, once the copy is complete you can remove the renamed copies. This method is qiute IO intensive but always releases the lock and retains the data. If the target table is to be replaced, then you can simply delete the OS dataset files to break the lock. I have written macros to try locking the table, if that fails then it either OS deletes or OS Copies (based on selected option) to break the lock. Please conatct me if you would like my macro..
... View more