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

You have to configure SASPy to know where SAS is and how to connect to it.   Error: The OS Error was: No such file or directory SAS Connection failed. No connection established. Double check your settings in sascfg_personal.py file. Attempted to run program /opt/sasinside/SASHome/SASFoundation/9.4/bin/sas_u8 /opt/tsasinside/SASHomeSASFoundation/9.4/bin/sas_u8 isn't on the machine you're trying to use.    See the configuration documentation here: https://sassoftware.github.io/saspy/configuration.html# ... View more

Awesome, that's great! ... View more

Correct, the doc showing this error is here: https://sassoftware.github.io/saspy/troubleshooting.html#java-problems The error is that it can't find the java executable you provided, you need to provide the full path   The OS Error was: The system cannot find the file specified Also, it look like you didn't set the permissions right on the .authinfo file. I think it requires 600 for it to be used. If you get a failure about not being able to get at it, after providing a valid java path, then you may need to remove the 'x' from that. ... View more

It looks like you're trying to code your own classpath, and it also looks like you've manipulated the saspy deployment to move files around to try to match what you're coding in your classpath, which is wrong, based upon just looking at these various pictures you're posted. Why are you coding a classpath? That's been unnecessary/wrong for like 3 years now (https://sassoftware.github.io/saspy/configuration.html#attn-as-of-saspy-version-3-3-3-the-classpath-is-no-longer-required-in-your-configuration-file). This latest error is due to the classpath being wrong, or something with moving the files around being wrong.  I guess I'd uninstall saspy, reinstall it and try a configuration based upon the doc, which is possibly what you have without moving files around and without coding a classpath. And the other thing about this environment not seeming to support prompting seemed correct, so use the authinfo file (https://sassoftware.github.io/saspy/configuration.html#the-authinfo-file-authinfo-on-windows) to provide your credentials to work around that problem with the environment. Be curious to see what other issues you may find; never heard of this particular environment so curious to see what other issues you happen upon, or hopefully, not! ... View more

Great! It's easy when you know how to navigate the metadata, but complicated to tell someone how 🙂   Also, you can put your credentials in an authinfo file so that you won't get prompted and have to enter them each time you connect. See that here: https://sassoftware.github.io/saspy/configuration.html#the-authinfo-file-authinfo-on-windows   Glad you're up and running! Tom ... View more

I'm not completely sure I understand. But, you do show the host and port you would need to configure SASPy to connect to that SASAppCS - Workspace Server. You showed that the Object Spawner 2 launches that workspace server, and that the object spawner is on host 'plnsascrep01.datalake.local' (If I can read that picture right); it's the one from the pic you posted. And, the workspace server is on the default port of 8591.   So just use those for the values in your your sascfg_personal.py configuration and try to connect with SASPy. Can you get into python and try to connect? Can you show your config file and the code you submit and the output it produces?   iomhost = plnsascrep01.datalake.local iomport = 8591   Thanks, Tom ... View more

Well, the proc iomoperate attempts you show aren't what is in the doc for this. You would need to submit the code in the doc. But, having access to SMC is better; same info (it's the metadata in the metadata server), but this is a nicer GUI that you can see the information in. So yes, look at the object spawners and workspace servers for the host names and port numbers.  ... View more

You can use proc iomoperate as described in this section of the doc to query for the Object Spawner host names (IOMHOST) and the Workspace server ports (IOMPORT) for your configuration. https://sassoftware.github.io/saspy/advanced-topics.html#using-proc-iomoperate-to-find-object-spawner-hosts-and-workspace-server-ports I would use the IOM access method, and Not the COM access method; they both require these values anyway, to know where SAS is that they are trying to connect to. But IOM is the fully supported and fully functional access method. ... View more

You'll need to add the 3 encryption jars to your saspy deployment. See the instructions here: https://sassoftware.github.io/saspy/configuration.html#attn-as-of-saspy-version-3-3-3-the-classpath-is-no-longer-required-in-your-configuration-file ... View more