Yes, that makes perfect sense.  As I'm regrettably new to SAS Communities, I'm not sure how a particular post gets marked as the 'answer'. Do you believe that your previous post, stating that you've go it working should be marked as that? I don't see how to mark it as such, myself. Maybe only the person who creates the thread can mark it that way?   Also, can I help with the config file? Is that still a problem?   Thanks, Tom ... View more

I'm glad that you're up and running! I see from the links, the issue was the host and port, which are for the Object spawner and Workspace server, not the metadata server. You solved that and are connecting. Not sure about the config file though, so if you'd like to explore that further, just let me know. I'm sure we can figure out what's going on with that.  We can continue here, or you can open an issue on saspy (https://github.com/sassoftware/saspy/issues), either way is fine. I can help either way!   Thanks! Tom ... View more

Ok, so I was able to at least connect to one of these myself, using a personal email (employees can't get at it w/ our credentials). It appears that you're not missing anything, but we are. the saspy that's installed in this system isn't configured right. The SAS_kernel in jupyter uses saspy under the covers to submit the code and get the results. In the python kernel of jupyter you can run saspy directly; which get's the same error, of course, as that is the saspy error from the SAS notebook too.   I've gotten up with our folks internally who support this and we will fix it. I will let you know when this is resolved.   Sorry about that, but I imagine they were trying out the python swat (talks to CAS) on this deployment and not saspy. But whatever the mix up, we'll address it!   Thanks! Tom ... View more

@jimbarbour, I've just see this post and I'm trying to investigate.I'm not familiar with this, so I don't know what for sure what's in this trial. Poking around I found this, I'm assuming this is what you were trying?   https://www.sas.com/en_us/trials.html And I suppose the one labeled Open Source Programmer?   I'm in the process of tracking down the folks who set this up so I can get into the system they are running to see why this isn't working.   The following is a bit of a guess, since I can't see what's here, but it's an educated guess FWTW 🙂 I believe that the jupyter interface you're using for this notebook is the SAS_kernel, which means, yes, it's SAS code that you submit in those cells. Jupyter has different 'kernels', which is just language interpreters for a given notebook. Notebooks are all the same; cells you type code into which then display results following that code, inline. This notebook is running the SAS_kernel, so it's SAS code you submit.   I see nothing wrong with what you're trying, it appears something is not correct in the installed code or configuration or something like that with the image you've been provided.   I'll try to get access to the underlying image and diagnose the problem. I assume I can reproduce it, as these are probably all identical images of code and configuration that each user gets for the trial. But again, I don't really know how this is all set up - yet 🙂   Also, can you show me what python code you're running that you mentioned was working? Were you able to do 'SAS' work via the Python kernel in a notebook, or was it just 'native' python code that was working?   Thanks, and I'll let you know what I find! Tom ... View more

2.2.9 is the current version, so you can just do pip uninstall saspy    and then  pip install saspy and you should get the current 2.2.9 version.   Be sure your configuration is in your sascfg_personal.py file, not the example sascfg.py file that is part of the saspy repo, because sascfg.py can be overwritten when you do this. That's why you put your configurations in the _personal file so they don't get clobbered when you upgrade!   Tom ... View more

Hey, so I think you can get what you need. The jars will be in the SAS installation where the workspace server you are connecting to is running (the one EG connects to currently). You said you have a SAS admin, or talked to them? If you can't access that system where the jars are yourself, they should be able to get there. You can copy those jars from that system to your client machine and put them in whatever directory you want. Then just point your classpath to where you put them. Those jars or compatible between windows and linux, so you don't have to worry about that either. If you know of a SAS 9.4 install on another machine that you can access, you can grab them from there too. Tom ... View more

Hey, glad to see you got connected up and are running with saspy. So, there's a couple of possibilities here. You are connected to a workspace server, and if that server had pre-assigned libraries, they would be available to you through the code you're running. So, either the library you do see assigned in your EG session is not pre-assigned in the workspace server via metadata, but perhaps by EG, or another possibility is that there is more than one Appserver, and EG is connecting to a different one that you've configured for saspy. Not knowing which is the case, the other obvious question is whether you can simply assign it yourself and at least accomplish your task. there's a saslib() method off the SASsession you can use to assign it. Or, of course, you can submit() the libname statement as well. If that works, and until you find out why it's not already there, you can add another key to your configuration definition to have saspy pre-assign it for you when you make a connection (new in 2.2.9);   'autoexec' : 'libname ua19 whatever_path_or_options_you_need;'   Can you verify that this workspace server is the same one as in EG, and, I suppose the other thing is if you are connecting with the same credentials. It could be possible that the library could be pre-assigned via mnetadata, but only for some users. I don't know for sure, but if you're using the same creds then that's moot.   Thanks, Tom   ... View more