Why does SAS randomly report "Library WORK does not exist" during execution?

[Mahis]

Hello everyone,

We have a SAS script that runs every day. Most of the time it completes without any problems but randomly it fails with the error:

ERROR: Library WORK does not exist

The WORK library is in fact present and available when we check.

Has anyone experienced this kind of intermittent issue before and could you share ideas on how to investigate the root cause?

Environment details:
SAS 9.4 M6
OS: RedHat Linux

Thanks in advance!

[MargaretC]

The error message you are seeing is coming from the Red Hat operating system.  Please check with RH as to why you are receiving this error message. 

An additional question, is your SAS WORK directory on an NFS file system?  

[Mahis]

Thanks for your reply.

The SAS WORK library is on a local file system dedicated specifically for SAS WORK not on NFS.

[AhmedAl_Attar]

Hi @Mahis 

Try adding this line at the start of your SAS script

libname _all_ list ;

It will write to the Log all the assigned library references  at the time of execution.

Keep in mind, SAS WORK library is typically auto-assigned via specifying its root location in 

• sasv9.cfg file
• sasv9_local.cfg file
• -WORK <SomePath> command line option

Check your deployment/execution settings are not negatively affecting where the -WORK is pointing to

Hope this helps

[Ksharp]

Adding the following two rows at the top of your code.
But that would cost you lots of storage at SAS service side, due to not delete the temporary datasets produced by your sas code.

libname x '.';
options user=x ;

[gwootton]

Does this error occur while the SAS code is running or is it preventing the SAS session from starting at all?

SAS is provided a WORK option on startup specifying a parent location (e.g. /tmp). SAS will create a WORK library within that path specifically for it's process (e.g. /tmp/SAS_workFFFFFFFFFFF_hostname)

If the parent path specified by the WORK option is not accessible, SAS will fail to start with an error:
$ ./sas -nodms -work /tmp2

ERROR: Library WORK does not exist.
NOTE: Unable to initialize the options subsystem.
ERROR: (SASXKINI): PHASE 3 KERNEL INITIALIZATION FAILED.
ERROR: Unable to initialize the SAS kernel.

If SAS is running and some process deletes the WORK directory it created, you'll see this error in your code execution:
? data test; x=1; run;

ERROR: Library WORK does not exist.
NOTE: The SAS System stopped processing this step because of errors.

So, if you have some process set up to clean your WORK path periodically, it could be deleting your WORK directory from under you, causing this error.

[Mahis]

In our case the script starts normally and runs through several steps without issues
The error appears only at the point where it needs to write an output dataset into WORK:

ERROR: Library WORK does not exist.

After that, the job keeps running until the end but whenever it references something that should be in WORK we get messages like:

ERROR: File WORK.TEST1.DATA does not exist.

So it looks like the WORK directory disappears (or becomes inaccessible) while the session is still active
The script itself doesn't stop completely it just keeps failing on any step that needs WORK

This happens randomly maybe 3 times a month while most other days the script finishes without any problem

[Tom]

That seems consistent with a cleanup script that is accidentally removing WORK folders while the SAS process that is using them is still running.

Another thing to check is virus scans (and other scans) of the disk where WORK directories are made that might be temporarily locking access.  

Another thing to check is that the algorithm that is being used to generate the name of the directory used for work.  It that is accidentally causing two different processes to want to use the same name for the WORK library it might result in the first program having its work directory access removed because the new directory created for the second program is using different permission.  Or just plain deleting the files that the first program created.

[Sajid01]

Hello @Mahis 
Please check if the user has access to the location defined for work library.

[jklaverstijn]

This is SAS 9.4M6, which is quite old. I have seen errors with WORK happen in the past where the (scheduled) execution of the cleanwork utility would interfere with the normal operation of SAS under certain timing conditions and sometimes ignoring the presence of an active process using the work location. It would always lead to a crashed SAS session.

Have a look at how (if) you have setup cleanwork and maybe get a later version of it (call SAS). I highly doubt this utility is sensitive to the SAS release you are on.

Also, consider upgrading to a later release. 

[thesasuser]

Hello @Mahis 
We are also on SAS 9.4M6  and do use cleanwork utility to cleanup the SASTemp which has users work artifacts.(Work Library).
In my experience, it has only deleted only those folders whose process does not exist. Never did I face a scenario where the artifacts of the running process have been deleted.
When you say "The error appears only at the point where it needs to write an output dataset into WORK:" please examine if there are disk quota limits set at the OS level. May be the quota is being exceeded. (I understand that disk quotas may be set in terms of space or Inode numbers).
 Also consider the suggestion by @MargaretC