If the client and server sessions are running on different network nodes, you must
include the TCP/IP node in the server ID in the LIBNAME and PROC OPERATE statements
by using a two-level
server name as follows:
SERVER=node.server
The access method evaluates the node name in this order of precedence:
node is
specified as the fully qualified domain name (FQDN). Here is an example:
mktserver.acme.com
If the server and the client sessions are running on the same node, you can omit the
node name.
server can
be either of the following:
Example 1:
A port is the unique number that is associated with the service that is used for passing
data to and receiving data from the server.
Precede the
port number with two consecutive underscores.
Note: Do not space after the first
underscore or the second underscore.
Note: Specifying a server by using
a port number is not supported for ODBC clients.
libname mylib '.' server=srvnode._ _5000;
Example 2:
If the TCP/IP node name is not a valid eight-character SAS name, assign the name of
the server node to a SAS macro variable, and then use the name of that macro variable
for node in the two-level
server name.
%let srvnode=mktserver.acme.com;
libname sales server=srvnode.server1;
Note: Do not use an ampersand (&)
in a two-level name. An ampersand would cause the macro variable to
be resolved by the SAS parser before syntactic evaluation of the SERVER=
option. The access method evaluates the node name in a two-level server
name.
Example 3:
You might assign the node name and the server ID to a macro variable.
%let srvnode=mktserver.acme.com 5000;
libname sales server=srvnode;