If there isn't a SAS ODBC server running on your PC when
you access a SAS data source from your ODBC application, then the
driver starts a SAS ODBC server. The driver uses the information that
you provided in the
Local Options dialog
box to start one for you automatically.
To access local data sources, the driver uses TCP/IP to communicate
with a SAS ODBC server. You must edit your
TCP/IP services file to define your servers before starting
the SAS ODBC server. It is not necessary for the server to be running
when you define your data sources. However, the server must be running
on your PC for you to access your SAS data sources. For information
about editing the
TCP/IP
services file, see
TCP/IP Services File. For more information about SAS servers,
see
SAS Servers.
If you already have
a SAS session running on your PC, then you can start the SAS ODBC
server in that session by submitting the following statements:
options comamid=tcp;
proc odbcserv id=servername authenticate=optional;
run;
Alternatively, you can
terminate your SAS session so that the driver can start a SAS ODBC
server for you in a new SAS session.
Note: When the SAS ODBC server
is running in a SAS session, the SAS session does not accept user
input from the keyboard.
If the SAS session cannot
be started before the timeout value that you specified in the
Local Options dialog box is reached, a timeout error
is returned to your ODBC client application. An error message is returned
to the client if the SAS session was started, but PROC ODBCSERV could
not execute.