https://communities.sas.com/t5/SAS-Enterprise-Guide/Using-SAS-on-a-Unix-server-datasets-locked/m-p/984868#M46446 <P>"Insufficient authorization to access" - this looks like your admins changed not only path but also access right. Ask them to double check if previous group/access-rights weren't changed.&nbsp;</P> <P>&nbsp;</P> <P>Bart</P> Tue, 17 Mar 2026 14:13:06 GMT yabwon 2026-03-17T14:13:06Z https://communities.sas.com/t5/SAS-Enterprise-Guide/Using-SAS-on-a-Unix-server-datasets-locked/m-p/984865#M46445 <P>Hello,</P> <P>&nbsp;</P> <P>Here's the error message</P> <P>How to solve that issue?</P> <P>&nbsp;</P> <PRE><CODE class=" language-sas">/.../perfop/master_perfop/Courtier/agence.data.spds_lock9. System Error Code = 13. ERROR: Insufficient authorization to access /.../perfop/master_perfop/Courtier/agence.data.spds_lock9. </CODE></PRE> <P>Please note that it is a sas code trigger by control-M.&nbsp; Before March 7, 2026 . On March 8, 2026, the SAS admin has added a prefix to all the path<BR /><BR />Example: old path = /dwh_actuariat/sasprocess/prodmens/...<BR /><BR />/sasdwh/dwh_actuariat/sasprocess/prodmens<BR /><BR /></P> <P>I wonder if the lock issue could be related to that.&nbsp; How to solve that issue.</P> <P>Please provide unix command to investigate and solve that issue.</P> <P>&nbsp;</P> <P>Regards,</P> <P>&nbsp;</P> Tue, 17 Mar 2026 12:21:36 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/Using-SAS-on-a-Unix-server-datasets-locked/m-p/984865#M46445 alepage 2026-03-17T12:21:36Z https://communities.sas.com/t5/SAS-Enterprise-Guide/Using-SAS-on-a-Unix-server-datasets-locked/m-p/984868#M46446 <P>"Insufficient authorization to access" - this looks like your admins changed not only path but also access right. Ask them to double check if previous group/access-rights weren't changed.&nbsp;</P> <P>&nbsp;</P> <P>Bart</P> Tue, 17 Mar 2026 14:13:06 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/Using-SAS-on-a-Unix-server-datasets-locked/m-p/984868#M46446 yabwon 2026-03-17T14:13:06Z