@gw2021, That is very curious. Are you located in Asia? Welcome to SAS Communities I see you joined a couple of weeks ago so it may be a small data problem.   Jared ... View more

@MariaD, SASPy has matured since my last update on this thread. You can configure it to communicate from your PC or a seperate unix server thorough IOM to HP-UX.  This allows python programmers to use SAS analytics for their computing. It also simplifies collaboration between SAS programmers and Python programers for analytical tasks. Here are some links:  IOM configuration doc for SASPy: https://sassoftware.github.io/saspy/install.html#remote SAS Global Forum 2019 Papers with mention of SASPy: https://support.sas.com/en/search.html.html?q=saspy&fq=siteArea%3A%22Papers%20%26%20Proceedings%22&fq=siteAreaChild%3A%222019%20SGF%20Proceedings%22       ... View more

@SASKiwi, As of January 7th I have a new decay scheme to favor more recent articles. Your recommendations appear to be much more recent. Can you look and tell me what you think?   Jared ... View more

One update that might be helpful to people who find this thread is that the options for accessing configuration files (sascfg) have been increased. You can now use the cfgfile= parameter on the SASsession method to use any configuration file visible from where saspy is installed. Here is the code: sas = SASsession(cfgfile='/some/path/to/your/config/sascfg_personal.py') The full documentation section is here: https://sassoftware.github.io/saspy/install.html#sascfg-personal-py   ... View more

You should take a look at the issues that have been reported on SASPy in GitHub: https://github.com/sassoftware/saspy/issues From the limited information Issue 24 (https://github.com/sassoftware/saspy/issues/24) or Issue 58 might give you some trouble shooting https://github.com/sassoftware/saspy/issues/58   If looking through the issues doesn't yield a solution please open a new issue.   Jared ... View more

The shipped version of the sascfg.py includes configuration details for the various connection methods for saspy. These are guidelines and likely your environment will require some modifications. The latest version of the file can be viewed on GitHub.  The documentation has configuration section that walks through the options step by step. If you have feedback or enhancements I welcome your input.   Here are a few common items to check (line 35) SAS_config_names=['default'] this line is a python list of the available configuration names. If there is only one configuration name then saspy will use that, if there are multiple and not explicitly specified the user will be prompted. A winlocal reference configuration is included in the file, to use it change the above line to this and saspy will automatically attempt to connect to your local PC SAS version. winlocal is just a name that represents a python dictionary  SAS_config_names=['winlocal']  or if you're connecting to multiple SAS servers then you might want to have something like this:   SAS_config_names=['winlocal', 'zos', 'viya']   To connect using IOM, you will need to have java installed where python (or Jupyter) will be run and several SAS jars that came with your deployment. On PC SAS, that will just be a matter of finding the location on your system (line 145 shows a default path for 9.4m3 install yours will likely be different). If you're connecting to a remote server via IOM then you'll need to copy the jars from one system to another.   lock_down. This prevents users from overriding configuration options. For PC SAS this won't really matter, but for a server installation I would set it to True (the default). Here is the inline documentation beginning at line 26 # Based upon the lock_down configuration option below, you may or may not be able to override option # that are defined already. Any necessary option (like user, pw for IOM or HTTP) that are not defined will be # prompted for at run time. To dissallow overrides of as OPTION, when you don't have a value, simply # specify options=''. This way it's specified so it can't be overridden, even though you don't have any # specific value you want applied.    Jared ... View more

Edward, I don't think we have any of those at the momemnt but if you enter an issue on the GitHub repo (https://github.com/sassoftware/saspy/issues) for what you're looking for one of hte maintainers or community members can help you get it created.   Best, Jared ... View more

Edward, Can you give an example of what you mean by "daily operation tasks"?    Thanks, Jared ... View more

-- Edward, Thank you for your write up on SASPy and and SAS 9.4+. I saw your wish to have the package supported on python 2.7. I think you can accomplish what you're after (to have a Jupyter notebook server running from your HPUX server) if you install Python3. It looks like ActiveState has a port here. You might also check Anaconda but I didn't see a port for HPUX explicitly listed.   Python 2.7 support is something we're evaluating but many of the extensions for Juypter are only supported on Python 3 and so I think moving to Python 3 is the better long term move.   Your example is great. For those looking for more background the documentation for the package is here: https://sassoftware.github.io/saspy/   ... View more