Chapter Contents
Previous
Next
|
Chapter Contents |
Previous |
Next |
| Communications Access Methods for SAS/CONNECT and SAS/SHARE Software |
| Client Tasks |
| Configuring the Server in the SERVICES File |
Each server must be defined as a service in the SERVICES file on each host node from which a client session accesses the server. This file usually is located in the directory in which the TCP/IP product is installed.
If you are using IBM TCP/IP, the SERVICES file is located in the \TCPIP\ETC directory, by default. If you are using Novell LAN WorkPlace, the SERVICES file is in \LANWP file, by default. For all other versions of TCP/IP, refer to your documentation to find out where the SERVICES file is installed. See Configuring the SERVICES File for information about editing the SERVICES file.
| Setting Security for Connecting Clients |
Requiring connecting clients to supply both a valid userid and password enforces server security. At the client, set the preferred security method for relaying a userid and password that are valid on the server host. For details, see Setting Security for SAS/CONNECT and SAS/SHARE.
| Specifying the TCP/IP Communications Access Method |
You must specify the TCP/IP communications access method at the 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 client to communicate with the server. TCP (an abbreviation for Transmission Control Protocol/Internet Protocol) is an example of an access-method-id.
Example:
options comamid=tcp;
The server is accessed using the TCP/IP access method.
You may specify the COMAMID option in an OPTIONS statement, at a SAS invocation, or in a SAS configuration file.
Additionally, you may use the COMAUX1 and COMAUX2 options to designate auxiliary communications access methods. See SAS/CONNECT and SAS/SHARE: Supported Access Methods According to Host Release for the supported access methods by host. If the first method fails to access a server, the second method is attempted, and so on. You can specify up to two auxiliary access methods based on the number of methods that are supported between client and server hosts.
COMAUX options can be specified only at a SAS invocation or in a SAS configuration file. The syntax for the COMAUX options follows:
-COMAUX1 alternate-method -COMAUX2 alternate-method
An example of configuration file entries for an OS/2 client connecting to an OS/390 server follows:
-comamid tcp -comaux1 appc
If the server cannot be reached using the TCP/IP method, a second attempt is made with the APPC access method.
| Specifying a Server Name |
If the client and server sessions are running on different network nodes, you must include the TCP/IP node in the server identifier in the LIBNAME and PROC OPERATE statements as follows:
SERVER=node.server
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 can represent either a server-id or a port number.
libname mylib '.' server=srvnode._ _5000;
See SAS Language Reference: Dictionary for details about SAS naming rules. See SAS/SHARE User's Guide for details about the LIBNAME and PROC OPERATE statements.
| Client Example |
The following example illustrates the statements that you specify in an OS/2 client SAS session to access a server with the TCP/IP access method:
options comamid=tcp; libname sasdata 'c:edc\prog2\sasdata' user=_prompt_ server=rmtnode.share1;
The first line declares the TCP/IP access method. The LIBNAME statement specifies the data library that is accessed through the server, which is specified by the two-level server name RMTNODE.SHARE1, by means of a prompt for a username and a password that are valid on the server.
| Server Tasks |
| Configuring the Server Service in the SERVICES File |
Each server must be defined as a service in the SERVICES file
on each remote host node on which a server runs. This file is located in the
directory in which the TCP/IP product is installed. Find out the correct location
of the TCP/IP package on your host system. See Configuring the SERVICES File for more information.
You may use file permissions to restrict a user's access to libraries and files through a server. A secured server allows connections only from those clients that provide valid userids and passwords for the host on which the server is running. A secured server uses a validated userid and password pair to verify a user's authority to access a SAS library or a SAS file.
Requiring connecting clients to supply a valid userid and password enforces server security. From a server session, set the TCPSEC option to the value _SECURE_. See Providing Client Identification in a pre-Version 8 Session for more information about setting this option.
| Specifying the TCP/IP Access Method at the Server |
You must specify the TCP/IP access method at the server before you start a SAS/SHARE server.
Use the following syntax to specify the TCP/IP access method at the server:
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.
For a server that is running on a host on which only one communications access method is available, use only the COMAMID option.
Example:
options comamid=tcp;
The server will be available only to SAS/SHARE sessions that use the TCP/IP access method.
You may specify the COMAMID option in an OPTIONS statement, at a SAS invocation, or in a SAS configuration file.
However, if the host on which a server is running supports multiple access methods, you may specify up to two auxiliary access methods by which clients may access the server. See SAS/CONNECT and SAS/SHARE: Supported Access Methods According to Host Release for the supported access methods by host.
All of the access methods initialize when the server initializes. The activation of multiple access methods makes a server available to several groups of clients, each using a different communications access method simultaneously.
COMAUX options can be specified only at a SAS invocation or in a SAS configuration file. The syntax for the COMAUX options follows:
-COMAUX1 alternate-method -COMAUX2 alternate-method
An example of configuration file entries for a server that is running on an OS/2 host follows:
-comamid tcp -comaux1 appc
When the server starts, all of the communications access methods are initialized. The server is simultaneously available to client sessions that use the TCP/IP access method as well as to clients that use the APPC access method.
See SAS/SHARE User's Guide for details about starting and accessing a server.
| Specifying a Server Name |
If the client and server sessions are running on different network nodes, you must include the TCP/IP node in the server identifier in the PROC SERVER statement as follows:
SERVER=server
server can represent either a server-id or a port number.
libname mylib '.' server=_ _5000;
See SAS Language Reference: Dictionary for details about SAS naming rules. See SAS/SHARE User's Guide for details about the PROC SERVER statement.
| Server Example |
The following example illustrates the statements that you specify in a SAS session on the OS/2 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 OS/2 host.
|
Chapter Contents |
Previous |
Next |
 Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.