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.   >>>            ... View more

Yes, that all sounds correct. The SAS_Kernel is just a jupyter extension that calls SASPy under the covers, so all you can do in a SAS notebook is execute SAS code. A Python notebook lets you use SASPy directly and have all the functionality at your disposal. But, in either case, it is just a connection to a single, one time use, SAS Process in a container, in a pod, on the K8S deployment that's Viya. SASPy isn't a Viya application, like say SAS Studio, which is part of Viya itself. I have to believe that SAS Studio would have a way to access the SAS Drive and upload files from your client.    I have to admit, I don't use any of that which is why I don't simply have the answer for you. What would need to happen, is for any SAS session you spin up and connect to in the Viya deployment, there would have to be a libref or fileref that it knows about and can access the 'Drive' you have with whatever data you have in it. I just an not familiar with any of that, but I will do some more investigation to see if I can figure it out. If a SAS session itself can access that, then it should be doable from SASPy. If all of that has to be implemented by a Viya client, and SAS itself had no concept of the SAS Drive component in the Viya deployment (there are hundreds of components in a Viya deployment), then you can't get at any of that from SAS directly via saspy because it's only connected to the SAS process in Viya, not all of the other stuff. Let me try to figure this out and see what I come up with! ... View more

I'm afraid I don't know. Were there instructions that came with the free trial you're using?  ... View more

You can use saspy to upload/download file between client and server. From the SAS Kernel, you can't do anything but submit SAS code, so I don't know how you would do that. FWIW, the sas.submitLST() method from a python Kernel is the equivalent of the SAS Kernel, and you can do so much more w/ python. Just sayin.    Here's an example of using upload (download is similar) to upload a sas data set (can be any file) to the work directory of a viya deployment; that's about the only dir in viya you have write permission to.    >>> sas Access Method = HTTP SAS Config name = tth SAS Config file = /opt/tom/github/saspy/saspy/sascfg_personal.py WORK Path = /opt/sas/viya/config/var/tmp/compsrv/default/6eca835b-7b16-48df-af86-6dad81576f75/SAS_workF01B000001BE_sas-compute-server-094e063f-11eb-450c-88a6-8261f5b3c3e1-56/ SAS Version = V.04.00M0P10142024 SASPy Version = 5.100.3 Teach me SAS = False Batch = False Results = Pandas SAS Session Encoding = utf-8 Python Encoding value = utf_8 SAS process Pid value = 446 SASsession started = Thu Oct 17 09:23:32 2024 >>> sas.list_tables('work') [] >>> sas.dirlist(sas.workpath) ['sasmac3.sas7bcat', 'sasmacr.sas7bcat', 'sastmp-000000004.sas7bitm', 'sas.lck', 'sasgopt.sas7bcat', 'profile.sas7bcat', 'regstry.sas7bitm'] >>> log = sas.upload('a.sas7bdat', sas.workpath) >>> for item in log: print(item, ':', log[item]) ... Success : True LOG : 108 filename _sp_updn 108! '/opt/sas/viya/config/var/tmp/compsrv/default/6eca835b-7b16-48df-af86-6dad81576f75/SAS_workF01B000001BE_sas-compute-server-094e 108! 063f-11eb-450c-88a6-8261f5b3c3e1-56//a.sas7bdat' recfm=N permission=''; 109 filename _sp_updn; NOTE: Fileref _SP_UPDN has been deassigned. >>> >>> sas.list_tables('work') [('A', 'DATA')] >>> sas.dirlist(sas.workpath) ['sasmac3.sas7bcat', 'sasmacr.sas7bcat', 'a.sas7bdat', 'sastmp-000000004.sas7bitm', 'sas.lck', 'sasgopt.sas7bcat', 'profile.sas7bcat', 'regstry.sas7bitm'] >>> sd = sas.sasdata('a') >>> sd.columnInfo() Member Num Variable Type Len Pos 0 WORK.A 1.0 x Num 8.0 0.0 >>> ... View more

Have you looked at the instructions https://sassoftware.github.io/saspy/configuration.html#iom? The sascfg_personal.py file is a python module, not a .txt file, but I assume you just typed that wrong here, else you would be getting an error, not being prompted for credentials.  Can you provide the contents of that file so I can see what you've done? Can't really help without any information. FWIW, did it connect when you provided your credentials? Did you try to put them in the authinfo file, so you don't need to enter them?  ... View more

It doesn't look like it. The way that viya system's configured, it not only requires a unique authcode every time you connect, but the url for getting the code is a different one every time also, so you're forced to have to try to connect, get the unique url and then provide the code that you get from that. This has nothing to do with saspy (though I support it as a connection mechanism), it's viya that's configured this way as the only way to connect to it.   Previously when they came up with this authcode scheme, the URL was fixed, so you could at least go get the code and then pass it in on the SASsession call as below. But now it uses a PKCE URL which is required and precludes being able to even know the url to get a code from because the url changes every time, just like the code. It's all in the name of security it seems. And yes, it's no fun, but I can't fix that. If they enables user/pw authentication, you could have used your creds in an authinfo file and it would just connect you like you (anyone) want(s). But that's not allowed, only the PKCE authcode scheme.   >>> sas = saspy.SASsession(cfgname='vft', authcode='VhZSA1xZVOskqT8aMWeu4gMEyGO7ZEiq') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/tom/github/saspy/saspy/sasbase.py", line 598, in __init__ self._io = SASsessionHTTP(sascfgname=self.sascfg.name, sb=self, **kwargs) File "/opt/tom/github/saspy/saspy/sasiohttp.py", line 751, in __init__ self.sascfg = SASconfigHTTP(self, **kwargs) File "/opt/tom/github/saspy/saspy/sasiohttp.py", line 518, in __init__ js = self._authenticate(user, pw, authcode, client_id, client_secret, jwt, cv) File "/opt/tom/github/saspy/saspy/sasiohttp.py", line 623, in _authenticate raise SASHTTPauthenticateError(msg) saspy.sasexceptions.SASHTTPauthenticateError: Failure in GET AuthToken. A PKCE URL is configured to be used to acquire an authcode with is system, but a non-PKCE authcode was passed in. Failure in GET AuthToken. >>> sas = saspy.SASsession(cfgname='vft', authcode='IOBhsXdPFv4P1LvWUZcFLqCAZKgCNzzN') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/tom/github/saspy/saspy/sasbase.py", line 598, in __init__ self._io = SASsessionHTTP(sascfgname=self.sascfg.name, sb=self, **kwargs) File "/opt/tom/github/saspy/saspy/sasiohttp.py", line 751, in __init__ self.sascfg = SASconfigHTTP(self, **kwargs) File "/opt/tom/github/saspy/saspy/sasiohttp.py", line 518, in __init__ js = self._authenticate(user, pw, authcode, client_id, client_secret, jwt, cv) File "/opt/tom/github/saspy/saspy/sasiohttp.py", line 623, in _authenticate raise SASHTTPauthenticateError(msg) saspy.sasexceptions.SASHTTPauthenticateError: Failure in GET AuthToken. A PKCE URL is configured to be used to acquire an authcode with is system, but a non-PKCE authcode was passed in. Failure in GET AuthToken. >>> ... View more

And, just to show you can get there from the SAS_Kernel too (which just uses SASPy under the covers). Given the following Configuration Definition in my sascfg_personal.py:   vft = {'url' : 'https://azureuse011476.my-trials.sas.com', 'context' : 'SAS Studio compute context', }   I can connect the same (BTW, at the prompt for authcode or userid, since the default is authcode, you can just hit enter - that's why you don't see 'authcode' typed in):   ... View more

Ok, well, I googled viya free trial and got to it. I guess it's the same as what you're using. This is set up for authcode authentication, like I would have guessed. That requires you to go to a web page and sign in to get a one time authcode to use to sign in. Like when you log on to anything on the internet these days and they send you a one time use code you have to enter.   >>> sas = saspy.SASsession(url='https://azureuse011476.my-trials.sas.com') To connect to Viya you need either an authcode or a userid/pw. Neither were provided. Please enter which one you want to enter next. Type one of these now: [default=authcode | userid]: The PKCE required url to authenticate with is https://azureuse011476.my-trials.sas.com/SASLogon/oauth/authorize?client_id=SASPy&response_type=code&code_challenge_method=S256&code_challenge=3f5_r3_ynBTMoAPlvDLAI6BTu8LdVLuXgePKMOmstMg Please enter authcode: Q_mq25QG-GzdUPS_GzcFjhSJCWbdfhRI Please enter the SAS Context you wish to run. Available contexts are: ['Import 9 service compute context', 'SAS Visual Forecasting compute context', 'Data Mining compute context', 'CAS Formats service compute context', 'CAS Management service compute conte xt', 'SAS Job Execution compute context', 'SAS Studio compute context', 'Natural Language Conversations service compute context', 'SAS Model Manager compute context', 'SAS Backup job compute context'] SAS Studio compute context SAS server started using Context SAS Studio compute context with SESSION_ID=b6181d9f-a809-41ee-9997-f136a2cf02e4-ses0000 >>> sas Access Method = HTTP SAS Config name = default SAS Config file = /r/sanyo.unx.sas.com/vol/vol810/u81/sastpw/.config/saspy/sascfg_personal.py WORK Path = /opt/sas/viya/config/var/tmp/compsrv/default/b6181d9f-a809-41ee-9997-f136a2cf02e4/SAS_work239F0000016D_sas-compute-server-035b3e9a-339d-470c-8cf2-11a28d5e0de5-4m7d5/ SAS Version = V.04.00M0P03182024 SASPy Version = 5.100.3 Teach me SAS = False Batch = False Results = Pandas SAS Session Encoding = utf-8 Python Encoding value = utf_8 SAS process Pid value = 365 SASsession started = Fri Sep 13 09:27:51 2024 >>> sas.assigned_librefs() ['SASHELP', 'MAPS', 'MAPSSAS', 'MAPSGFK', 'SASUSER', 'WORK'] >>> ... View more

Hey, sure I can help. First, Can you point me to where the free trial info is, so I can try it out to see; be sure I'm getting at the same thig you are. Second, Viya has more than one authentication mechanism. Are you sure it's configured to use user/pw? They've gone away from that due to 'security' and generally use the authcode mechanism in deployments these days; but I don't know how this is set up. Did you try the authcode path? In the screen shot it shows where it asks you which mechanism to use. Did you try the other? Have you successfully connected to it using any other client? Did you get instructions from the free trial saying how to connect to it (that wouldn't be for saspy, but for Studio or something)?   Thanks, Tom ... View more

It looks like the port you provided would be for the Metadata Server, not the Workspace server. Make sure the IOMHOST is correct for the Object Spawner that launches the Workspace server you're trying connect to, and use the IOMPORT configured for Workspace Server for that Object Spawner.   ... View more

I'll say right now that I'm sure you know more about SAS Macro than I do. I've never needed to use it enough to understand all of it's obtuse functionality. As for the doc, yes, it has bit's of info scattered over different pages and sometimes it's misleading or contradicts itself in different places. The doc I was looking at about it saying & and % is just a different page. I don't know if it's accurate or not. I can't say I tested every possibility of macro strings when implementing symput.    But, given that you can choose any or none of the various macro functions when using symput, or code any way you want with submit, and the fact that I don't make breaking changes to SASPy if I can possibly help it, I'm not inclined to change the default behavior for this and take the chance of breaking someone's code that's already working as they want and expect.   Again, I appreciate your understanding on this!   Thanks! Tom ... View more

That's for your understanding @Quentin . From the SAS doc for %BQUOTE, it states: In addition, %NRBQUOTE masks: & %. So, again, it's just to allow Python strings to be used in SAS as they are, not interpreted/converted as/to something different - by default. SAS is tough in that there are multiple ways to get the same behavior from different things and to get different behavior from the same thing!  ... View more

Hey sorry for the confusion. I can speak to 'why' the SASPy developer chose this, as that's me. One of the goals of SASPy is for it to be intuitive for Python developers and not require intimate knowledge of SAS, it's syntax and it's idiosyncrasies. That's a goal, and clearly not 100% achievable, since SAS has so many options and syntaxes ... Still, the provided methods try to be Pythonic instead of SAS-centric. With the submit methods, you can code anything the SAS way, so you always have that. The goal of symput is to take the value of a Python variable/literal, and make that value exist in SAS as a macro variable. The default for this method is then to make the string from Python be that same string in SAS. Without using the quoting functions, no end of various characters will be parsed/interpreted/changed thus not having the actual Python value be what's in SAS. Of course, providing the option to allow SAS coders to specify special SAS'ism cases is available on the method; thus providing the ability to still get whichever different behavior you want from SAS if you understand the macro language and interpreter. But the default allows real python values to be transferred over without SAS changing them. There's more explanation here: Understanding Why Macro Quoting Is Necessary  I hope that helps provide perspective on why the default wasn't what you were expecting.  Thanks! Tom ... View more

I have to believe the user is referring to using Proc Python in Viya. The proc also has similarly named methods for moving data between pandas and SAS, though the method signatures are different.  Have you looked at the log after the failure to see what errors or other information might be available?   SAS.df2sd(df, "LIBRARY.Table_Name") SAS.printLOG()   Do you know what's in your dataframe? Realize that dataframes can contain things SAS datasets cannot. Each cell of a dataframe can contain anything. They aren't bound by 'relation table' constraints like SAS data sets or database tables. Relational tables require that the data type in every row of a table be the same for a given column. data frames don't require that. There are all kinds of ways a dataframe can't be converted into a SAS data set. But that's speculation at this point as I have no idea what's in your dataframe of what errors might be in log stating what went wrong.   So, let's start by looking at the log for the method you ran that didn't seem to work right. BTW, you can change the setting so the log is simply displayed to begin with:   SAS.hideLOG(False) SAS.df2sd(df, "LIBRARY.Table_Name")   It's also possible that there could be an enhancement or bug fix that's happened since the version of viya you're using. it's almost a year old. So, again, seeing what actually happened will help with that. Looking at the LOG is the first thing to do.   Thanks, Tom ... View more