Here are the most common reasons why SAS can't find the file or folder you are referencing:
1. A typo in the code. For example, I am running PC SAS. There are SAS data sets in the c:\testfile folder that I need. I submit this code:
LIBNAME T "C:\testfiles";
and the LOG says:
NOTE: Library T does not exist.
2. SAS doesn't have access to the file location you have specified. This usually happens when you're using client software, like Enterprise Guide or SAS Studio, to write and submit your SAS code, but SAS isn't installed on your computer - it's running on a server somewhere else. It gets tricky because it's essential to differentiate between what the client can see and what the SAS server can see because now they are installed on two different machines. So let's step through this, starting with SAS installed on your computer. Windows Explorer (gear image) can see the files on the local hard drive. Because SAS is installed on the PC, if you expand Folders under the Local server in Enterprise Guide, you can see the same files there:
If I have a network drive mapped, both Windows Explorer and the Enterprise Guide Server can see those files, too:
Now, when SAS is installed on a separate server (including SAS University Edition, where SAS is running on a virtual server), the SAS server can no longer "see" files on the PC hard drive. Windows and SAS no longer share the same "view". If you browse the SAS Server files in Enterprise Guide, you can see the view is different:
If the PC and SAS server both have access to the same network location, you can move files there in Windows and "see" them in SAS, but the PATH to those in Windows will be different than the path on the SAS server:
So, when SAS was installed on the PC, this LIBNAME would have worked:
libname t "s:\workshop";
And with SAS on the server, this LIBNAME would see the same data:
libname t "/mnt/share/workshop";
If you can't locate your network files in Enterprise Guide (or SAS Studio) by browsing in the Server -> Files folders, it might still be possible to access them from SAS, but you'll need to ask your SAS administrator how to specify the proper path.
May the SAS be with you!
Mark
... View more