Ok, well, it doesn’t appear that the SAS Drive is something accessible from a SAS session itself. I connected to a Viya deployment here (not the trial version), and from the SAS Drive web app I could upload a file; uploaded a SAS data set. Then from SAS Studio web app (connected to a SAS session) I could see that data set in ‘My Folders’ which is the Drive thing which is persistent storage (another component in a pod in the viya deployment). I could also right click on the folder or the file and get the path to it; /Users/sastpw/My Folder.
However, I couldn’t access that from SAS itself; see the output below. I also tried to add that table to a ‘flow’ in Studio, but it says that’s invalid (I assume cuz SAS can’t access it). I don’t really know what this Drive thing is for, but it only seems accessible from the web components themselves and not directly from SAS.
FWIW, in a real viya deployment, you would certainly have some permanent storage configured and mounted to the Compute Servers (that’s the name of the SAS processes – like Workspace Server in SAS 9), such that you would have a filesystem to libname and filename to which would be accessible from each invocation of SAS, just like you would running SAS on a real computer where your local filesystem is available and persistent, even though your WORK library comes and goes with each individual SAS session. I don’t expect that the free trial version of this has any permanent storage location mounted to compute for you to use like this. But in a real deployment, that would be the actual answer to this.
Trying to google how to do this I found another community post, asking the same, but with no answers:
https://communities.sas.com/t5/SAS-Programming/Access-SAS-Drive-from-SAS-Studio-Viya-4/td-p/838460
And, here’s what happens trying to get at that Drive folder from the SAS session:
From a SAS Studio session:
79
80 libname x '/Users/sastpw/My Folder';
ERROR: The path /Users/sastpw/My Folder is not in the list of accessible paths when SAS is in the lockdown state.
ERROR: Error in the LIBNAME statement.
81
82
83 *libname _all_ list;
84
85 libname sasuser list;
NOTE: Libref= SASUSER
Scope= Kernel
Engine= V9
Access= READONLY
Physical Name= /sasuser
Filename= /sasuser
Inode Number= 20709938
Access Permission= rwxrwxrwx
Owner Name= root
File Size= 4KB
File Size (bytes)= 4096
86
87 data sasuser.a;x=1;run;
ERROR: Write access to member SASUSER.A.DATA is denied.
NOTE: The SAS System stopped processing this step because of errors.
NOTE: DATA statement used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds
88
89 filename x '/Users/sastpw/My Folder/a.sas7bdat';
ERROR: The path /Users/sastpw/My Folder/a.sas7bdat is not in the list of accessible paths when SAS is in the lockdown state.
ERROR: Error in the FILENAME statement.
90
Likewise from saspy:
>>> sas.submitLOG("filename x '/Users/sastpw/My Folder';")
34 filename x '/Users/sastpw/My Folder';
ERROR: The path /Users/sastpw/My Folder is not in the list of accessible paths when SAS is in the lockdown state.
ERROR: Error in the FILENAME statement.
>>> sas.saslib('x', path='/Users/sastpw/My Folder')
35 libname x '/Users/sastpw/My Folder' ;
ERROR: The path /Users/sastpw/My Folder is not in the list of accessible paths when SAS is in the lockdown state.
ERROR: Error in the LIBNAME statement.
>>>
