hi both - for SAS, you have to install and licence SAS-Software on the server/pc you use to extract the data. Which is quite expensive (in comparison to free ).
Actually, we are using the same solution as you Nathan - using csv-files.
If we are changing this method i'll place a comment here, if we found a working solution
Hi. We have had same problem and tried to get access from qv via sas odbc to the mainframe.
We solved it as follows (out of SAS ODBC documentation - we are using SAS ODBC driver 64 bit):
Locate the following file:
Enter one of the following entry, depending if you use local sas session or remote. We have used the second one.
local 6000/tcp # service name for local access to SAS data
shr2 5010/tcp # service name for SAS/SHARE server
We must adjust the port and also the "shr2" name to our servername as specified in ODBC configuration settings.
After changing the services file, the problem was solved.
Please find the source document using this link - look at page 20 -> TCP/IP Services File
Special thanks to Frank who has helped me in solving our issue.