https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752057#M22544 <P>If you supply the log file name with the -log option on the commandline of your batch job, you can't do anything about this from within SAS, as the job will never start (SAS crashes upon invocation).</P> <P>&nbsp;</P> <P>How you can find a user that keeps you from getting the write lock depends on the operating system; in UNIX, use the fuser command to retrieve the process ID's (numbers), from which you can then list the processes (and their owners) with ps -p.</P> Mon, 05 Jul 2021 11:33:15 GMT Kurt_Bremser 2021-07-05T11:33:15Z https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752026#M22543 <P>Is it possible to find out which particular user had the lock when a batch user wanted to write to the same log location. Can we know which user was trying to use the file at that time?</P> Mon, 05 Jul 2021 07:25:37 GMT https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752026#M22543 techie 2021-07-05T07:25:37Z https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752057#M22544 <P>If you supply the log file name with the -log option on the commandline of your batch job, you can't do anything about this from within SAS, as the job will never start (SAS crashes upon invocation).</P> <P>&nbsp;</P> <P>How you can find a user that keeps you from getting the write lock depends on the operating system; in UNIX, use the fuser command to retrieve the process ID's (numbers), from which you can then list the processes (and their owners) with ps -p.</P> Mon, 05 Jul 2021 11:33:15 GMT https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752057#M22544 Kurt_Bremser 2021-07-05T11:33:15Z https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752093#M22545 <P>1. There could be an issue of lock if two users are trying to write to the same file. Typically this does not happen.<BR />&nbsp; Typically locks are not held on folders having log files. (Unless you have some specific batch that is creating a folder)</P> <P>2. What is your operating system on which the file / folder exists and the job is running?</P> Mon, 05 Jul 2021 14:08:03 GMT https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752093#M22545 Sajid01 2021-07-05T14:08:03Z https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752768#M22572 There is a specific batch id that is creating the log files but in this case it doesn't allow to write to the log file stating "Resource is write-locked by another user"<BR /><BR />The Operation system used here is Linux Thu, 08 Jul 2021 04:12:25 GMT https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752768#M22572 techie 2021-07-08T04:12:25Z https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752770#M22573 <P>Typically log file names are date and time stamped right down to hundredths of a second if the SAS jobs are run from a scheduler. That way it is near impossible for two jobs to write to the same log file and encounter a lock. You haven't provided any details on how your log files are named but date and time stamping them should avoid locks.&nbsp;</P> Thu, 08 Jul 2021 04:44:05 GMT https://communities.sas.com/t5/Administration-and-Deployment/lockout-while-trying-to-write-to-log/m-p/752770#M22573 SASKiwi 2021-07-08T04:44:05Z