We’re smarter together. Learn from this collection of community knowledge and add your expertise.

Using SAS/ACCESS Interface to ODBC on UNIX Platforms

by SAS Employee mebass on ‎03-09-2016 11:06 AM - edited on ‎03-14-2016 04:10 PM by Community Manager (2,413 Views)

SAS Technical Support and Publications will post a series of articles about using SAS/ACCESS Interface to ODBC on UNIX platforms. From these, you can learn about specific platforms and how they interact with various ODBC drivers and driver managers. 

 

About This Series

No matter what specific interfaces or platforms you want to work with, start with the overview article, followed by a platform-specific build article.  You can then continue with other articles based on what you want to accomplish. Here's a list of articles:

 

Overview

How to configure SAS/ACCESS Interface to ODBC on UNIX Platforms

 

Build the Latest unixODBC Driver Manager

How to build the latest unixODBC Driver Manager for Linux

How to build the latest unixODBC Driver Manager for AIX

How to build the latest unixODBC driver manager for Solaris

 

Drivers and Driver Managers

Where to find sources for ODBC drivers for Oracle on UNIX

 

Configure Various Interfaces

How to configure SAS/ACCESS Interface to ODBC on Linux with an ODBC driver from Oracle

How to configure SAS/ACCESS Interface to ODBC on Linux with a Sybase IQ ODBC driver from Sybase

Comments
by Super User
on ‎03-09-2016 02:57 PM

Nice series, but can you get all of the hyperlinks working?

by Community Manager
on ‎03-10-2016 01:27 PM

Hi 

 

 

by Super User
on ‎03-10-2016 02:55 PM

OK. I think the best thing about this article is gathering all of the setup information in one place.

by Community Manager
on ‎03-11-2016 09:38 AM

Great point 

by Occasional Contributor PascalMaurice
on ‎03-23-2016 01:22 PM

Hi there,

 

we find this advice:

  • A Linux startup script is used to set the needed Oracle and ODBC environment variables. Normally, the best place to set these in the SASENV_LOCAL file in the !SASROOT/bin directory because it ensures that they are set for whoever starts SAS, no matter how it is started.

perhaps the SASENV_LOCAL could not be considered as the best place: now we have the Lev1... directory tree with all the files to be used to tune the SAS platform, doing so we are sure that all the specific tuning and parameters is done in this directory tree and not on files spreaded across Lev1 and sashome.

for example Lev1/level_env_usermods.sh could be a best place ?

by SAS Employee KatT_sas
on ‎04-08-2016 05:19 PM

Your point is well taken, PascalMaurice& you can certainly do that.  One assumption we made for these articles was to be sure that all SAS/ACCESS products working with ODBC on UNIX platforms can be used in the same SAS session.

Contributors
Your turn
Sign In!

Want to write an article? Sign in with your profile.