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

SAS/SHARE

Client Tasks

CAUTION:: Windows NT only Server security is supported on the Windows NT platform only.

System Administrator, User, or Network Administrator

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

For a Windows NT client only, assign the appropriate rights to each connecting client.
For a Windows NT client only, set security for connecting clients.
Specify the NetBIOS access method.
Specify a server name.

Assigning the Appropriate Rights for Connecting Clients

CAUTION:: Windows NT only Server security is supported on the Windows NT platform only.

The account in which a connecting client runs must have the appropriate rights. To assign these rights

Click on the Administrative Tools icon.
Click on the User Manager icon.
From the Policies pull-down menu, select "User Rights."
Click the "Show Advanced User Rights" box.
Assign "Log on as a batch job" rights to the appropriate users.

Setting Secure Userids and Passwords for Connecting Clients

CAUTION:: In the Windows environment, server security is supported on the Windows NT platform only.

Set security at the client using either of the methods explained in Setting Security for SAS/CONNECT and SAS/SHARE. For Version 8 security behavior, specify the USER= and PASSWORD= options in the appropriate statement. For details, see USER= and PASSWORD= Options in Selected Statements.

For Version 7 security behavior, if you set the SASSECUR option at the client, either specify a userid and a password that are valid on the server or specify _PROMPT_ to supply the userid and password when connecting to a server. For information about setting the SASSECUR option, see SAS/SHARE SASSECUR Option.

For Windows NT only that runs Version 8, you may qualify username in the form Windows-NT-domain-name\username. Here is an example of how you might specify this information in the LIBNAME statement in SAS/SHARE :

libname test 'prog2 a' user="apex\bass.time2go" server=share1;

Domain name apex identifies the location of the username and password database. Username bass and password time2go will be verified against those in the identified domain's username and password database.

To set up a secure server, you must assign a userid and a password that are valid on the server's host. Once set up, connecting clients must use valid userids and passwords to connect to the server. See SAS/SHARE SASSECUR Option for information about setting the SASSECUR option.

Specifying the NetBIOS Access Method

You must specify the NetBIOS access method at each connecting client before you can access a server. Use the following syntax:

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. NetBIOS (an acronym for Network Basic Input/Output System) is an example of an access-method-id.

Example:

options comamid=netbios;

The server is accessed using the NETBIOS 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/SHARE: Valid Access Methods Between Hosts 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, depending on the number of methods that are supported between client and server hosts.

COMAUX options can be specified only at SAS invocation or in a SAS configuration file. The syntax for the COMAUX options follows:

-COMAUX1 alternate-method
-COMAUX2 alternate-method

An example of SAS configuration file entries for an OS/2 client that is connecting to a Windows NT server follows:

-comamid netbios
-comaux1 tcp
-comaux2 appc

If the server cannot be reached using the NetBIOS access method, a second attempt is made with the TCP/IP access method, and then with the APPC method.

Specifying a Server Name

You must specify the server's identifier on the LIBNAME and PROC OPERATE statements as follows:

SERVER=identifier

Follow standard SAS naming rules when defining a server name. 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.

Example:

server=share1;

Client Example

The following example illustrates the statements that you specify in a Windows NT client configuration file that are used to access a server with the NetBIOS access method:

-set vqmlinks 1
-set vqadaptr 0

See Setting SAS Options and Variables for details about these options.

The following example shows the statements that are specified in a Windows NT client session:

options comamid=netbios;
libname sasdata 'c:\edc\prog2\sasdata' user=_prompt_ server=share1;

The NetBIOS access method is declared. The LIBNAME statement specifies the data library that is accessed through the server SHARE1 by means of a prompt for a username and a password that are valid on the server.

Server Tasks

Server Administrator

Note: Server security is supported on the Windows NT platform only. [cautionend]

To set up a secure server and to make it accessible to a client, perform the following tasks:

Assign the appropriate rights for a secure server for Windows NT only.
Require only validated clients to access a secure server for Windows NT only.
Set NetBIOS access method security for Windows NT only.
Specify the NetBIOS access method.
Specify the server name.

Assigning the Appropriate Rights for a Secure Server

CAUTION:: Windows NT only This process is supported on the Windows NT platform only.

The account in which a secure server runs must have the appropriate rights. To assign these rights

Click on the Administrative Tools icon.
Click on the User Manager icon.
From the Policies pull-down menu, select "User Rights."
Click on the "Show Advanced User Rights" box.
Assign "Act as part of the operating system" rights to the appropriate users.

Setting NetBIOS Access Method Security

CAUTION:: Windows NT only This procedure is supported on the Windows NT platform only.

Before you can create a secure SAS/SHARE server, you must make the access method secure by assigning the _SECURE_ value to the SASSECUR option. See SAS/SHARE SASSECUR Option for information about setting the SASSECUR option.

Specifying the NetBIOS Access Method at the Server

You must specify the NetBIOS communications access method at the server before you can create and access a SAS/SHARE server. Use the following syntax:

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. NetBIOS (an acronym for Network Basic Input/Output System) 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=netbios;

The server will be available only to SAS/SHARE sessions that use the NetBIOS 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 by using the COMAUX1 and COMAUX2 options. See SAS/CONNECT: Valid Access Methods Between Hosts 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 a Windows NT host follows:

-comamid netbios
-comaux1 tcp
-comaux2 appc

When the server starts, all of the communications access methods are initialized. The server is simultaneously available to client sessions that use the NetBIOS access method as well as to clients that use the TCP/IP and APPC access methods.

Specifying a Server Name

Specify the server identifier in the PROC SERVER statement as follows:

SERVER=server-id

Example:

server=share1;

Server Example

The following example illustrates the statements that you specify in a configuration file on the Windows NT host at which you start a server:

-set vqmlinks 1
-set vqadaptr 0

See Setting SAS Options and Variables for details about these options.

Specify the following statements in a SAS session on the Windows NT remote host to start a server:

%let sassecur=_secure_;
options comamid=netbios;
proc server id=share1 authenticate=req;
run;

The first line uses the SAS macro variable SASSECUR to prompt clients for a userid and a password that are valid on the server. The NetBIOS access method is declared for the server SHARE1 that is started on a Windows NT remote host.The additional options in the PROC SERVER statement allow only validated clients to access the server.

Chapter Contents
Previous
Next
Top of Page