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

Did you figure out your host and port? Also, you had the `appserver` key in your posted config, with an invalid value. It's not clear you need that, but specifying it with an invalid value will cause a problem. Not seeing the actual errors or output from what you're trying doesn't help. Can you show the code you're submitting and all of the output? Do you still need help with this? Or did you get it working? Tom ... View more

hosts and ports are defined in metadata. You can see what they are using SMC, or via proc iomoperate: https://sassoftware.github.io/saspy/advanced-topics.html#using-proc-iomoperate-to-find-object-spawner-hosts-and-workspace-server-ports ... View more

Did you get this working? Was that syntax error the only issue? ... View more

Have you tried using SASPy outside of proc fcmp, so you can figure out how it works and see if what you are doing is correct? Trying to figure out what's wrong from running inside of proc fcmp isn't going to work. cfgfile is the path of the config file you want to use, when you don't simply have it in any of the search paths where it would already be found. cfgname is the name of a config definition in that file (python Dict with config values). So, no, that wouldn't make sense. You're just running this with a local SAS install on your PC? Just run Python and SASPy there outside of SAS to get a connection and see that what you're trying to do is correct.       ... View more

I can't speak to your overall workflow, but the error you're getting is because you need the keyword for that value: cfgfile= sas = saspy.SASsession(cfgfile='E:\Program Files\Python311\Lib\site-packages\saspy\sascfg_personal.py') All parameters for SASsession are keyword, not positional. So, that should get rid of this error.   Tom ... View more