Communications Access Methods for SAS/CONNECT and SAS/SHARE Software

SAS/SHARE

Client Tasks

User or Applications Programmer

To prepare for creating a SAS/SHARE server and accessing it, perform the following tasks:

Configure the server in the CONFIG.SAS file.
Specify the TCP/IP access method.
Specify a server name.

Configuring the Server in the CONFIG.SAS File

Each SAS/SHARE server must be defined as a service in the CONFIG.SAS file on each remote host node on which a server runs and on each node from which a user session will access the server. See Configuring Services in the CONFIG.SAS6xx File for more information.

Specifying the TCP/IP Communications Access Method

You must specify the TCP/IP communications access method at the connecting client before you access a server.

Use the following syntax to specify the TCP/IP access method at each connecting client:

OPTIONS COMAMID=access-method-id;

where COMAMID is an acronym for Communications Access Method Identification. access-method-id identifies the method used by the server to communicate with the client. TCP (short for TCP/IP, which is an abbreviation for Transmission Control Protocol/Internet Protocol) is an example of an access-method-id.

Because the Macintosh platform supports only one communications access method, you can use only the COMAMID option. See SAS/CONNECT and SAS/SHARE: Supported Access Methods According to Host Release for the supported access methods by host.

Example:

options comamid=tcp;

The server is accessed using the TCP/IP access method.

You may specify the COMAMID option in an OPTIONS statement, in a SAS configuration file, or in the CONFIG.SAS file.

An example of a configuration file entry for a Macintosh client connecting to a UNIX server follows:

-comamid tcp

Specifying a Server Name

If the client and server sessions are running on different network nodes, you must include the node name in the server identifier in the LIBNAME and PROC OPERATE statements as follows:

SERVER=node.server-id

This representation is known as a two-level server name.

node must be a valid TCP/IP node name. server-id identifies the service that has been configured in the CONFIG.SAS file. See Configuring Services in the CONFIG.SAS6xx File for more information.

If the TCP/IP node name is not a valid SAS name, you can assign the name of the server's node to a SAS macro variable. Then use the name of the macro variable for node in the two-level server name.

The access method evaluates the node name in this order of precedence:

SAS macro variable
valid node name.

The following example shows the assignment of a SAS macro variable to a server's node name:

%let srvnode=mktserve.acme.com;
libname sales 'machd:sasdata' server=srvnode.server1;

Note: Do not use an ampersand (&) in a two-level server name. An ampersand causes the macro variable to be resolved by the SAS parser prior to syntactic evaluation of the SERVER option. The access method evaluates the node name in a two-level server name. [cautionend]

See SAS Language: Reference, Version 6, First Edition for details about SAS naming rules. See SAS/SHARE Software: Usage and Reference, Version 6, First Edition for details about the PROC OPERATE and LIBNAME statements.

Client Example

The following example illustrates the statement that you specify in a Macintosh client CONFIG.SAS612 file to configure the server service.

-set gsbn_server1 5015

The following example illustrates the statements that you specify in a Macintosh client SAS session to access a server with the TCP/IP access method:

options comamid=tcp;
libname sasdata 'edc.prog2.sasdata' 
        server=rmthost.share1;

The first line declares the TCP/IP access method. The LIBNAME statement specifies the name of the data library that is accessed through the server, which is identified by the two-level name RMTHOST.SHARE1.

Server Tasks

User or Applications Programmer

To prepare for starting a SAS/SHARE server, perform the following tasks:

Specify the TCP/IP access method.
Specify a server name.

Specifying the TCP/IP Communications Access Method

You must specify the TCP/IP communications access method at the server before you start a server. Use the following syntax to do this:

OPTIONS COMAMID=access-method-id;

where COMAMID is an acronym for Communications Access Method Identification. access-method-id identifies the method used by the server to communicate with the client. TCP (short for TCP/IP, which is anabbreviation for Transmission Control Protocol/Internet Protocol) is an example of an access-method-id.

Because the Macintosh platform supports only one access method, you can use only the COMAMID option. See SAS/CONNECT and SAS/SHARE: Supported Access Methods According to Host Release for the supported access methods by host.

Example:

options comamid=tcp;

The server will be available only to SAS sessions that use the TCP/IP access method.

You may specify the COMAMID option in an OPTIONS statement, in a SAS configuration file, or in the CONFIG.SAS file.

An example of a configuration file entry for a server that is running on a Macintosh host follows:

-comamid tcp

Specifying a Server Name

If the client and server sessions are running on different network nodes, you must include the node name in the server identifier in the PROC OPERATE SET SERVER statement as follows:

SERVER=node.server-id

This representation is known as a two-level server name.

node must be a valid TCP/IP node name. If the server and the client sessions are running on the same node, you may omit the node name. server-id identifies the service that has been configured in the CONFIG.SAS file. SeeConfiguring Services in the CONFIG.SAS6xx File for more information.

The access method evaluates the node name in this order of precedence:

valid node name
SAS macro variable.

The following example shows the assignment of a SAS macro variable to a server's node name:

%let srvnode=mktserve.acme.com;
libname sales 'machd:sasdata' server=srvnode.server1;

Configuring the Server in the CONFIG.SAS File

Server Administrator

To prepare for starting a SAS/SHARE server, perform the following task:

Configure servers in the CONFIG.SAS file.

Each SAS/SHARE server must be defined as a service in the CONFIG.SAS file on each remote host node on which a server runs, and on each node from which a user session will access the server. See Configuring Services in the CONFIG.SAS6xx File for more information.

Specifying a Server Name

If the client and server sessions are running on different network nodes, you must include the node name in the server identifier in the PROC SERVER statement as follows:

SERVER=node.server-id

This representation is known as a two-level server name.

If the TCP/IP node name is not a valid SAS name, you can assign the name of the server's node to a SAS macro variable, then use the name of that variable for node in the two-level server name.

The access method evaluates the node name in this order of precedence:

SAS macro variable
valid node name.

The following example shows the assignment of a SAS macro variable to a server's node name:

%let srvnode=mktserve.acme.com;
libname sales 'machd:sasdata' server=srvnode.server1;

Note: Do not use an ampersand (&) in a two-level server name. An ampersand causes the macro variable to be resolved by the SAS parser prior to syntactic evaluation of the SERVER= option. The access method evaluates the node name in a two-level server name. [cautionend]

Server Example

The following example illustrates the statement that you specify in a Macintosh server CONFIG.SAS612 file to configure the server:

-set gsbn_server1 5015

The following example illustrates the statements that you specify in a SAS session on the Macintosh host at which you start a server:

options comamid=tcp;
proc server id=share1;
run;

The TCP/IP access method is declared and the server SHARE1 is started on the Macintosh host.

Chapter Contents
Previous
Next
Top of Page