Chapter Contents
Previous
Next
|
Chapter Contents |
Previous |
Next |
| Communications Access Methods for SAS/CONNECT and SAS/SHARE Software |
| Client Tasks |
| Setting Security for Connecting Clients |
Requiring connecting clients to supply a valid userid and a password enforces server security. At the client, set the preferred security method for relaying a userid and a password that are valid on the server host. For details, see Setting Security for SAS/CONNECT and SAS/SHARE.
| Specifying the APPC Access Method |
You must specify the APPC communications access method at the client before you access a server.
Use the following syntax to specify the APPC 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. APPC (an abbreviation for Advanced Program-to-Program Communication) is an example of an access-method-id.
Example:
options comamid=appc;
The server is accessed using the APPC 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, depending 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 a Windows NT server follows:
-comamid appc -comaux1 tcp -comaux2 netbios
If the server cannot be reached with the APPC method, a second attempt is made with the TCP/IP access method, and then with the NetBIOS access method.
| Specifying the Server Name |
The server name that you specify in the PROC SERVER, PROC OPERATE, and LIBNAME statements must be defined as the local-LU at the SAS/SHARE server and as a remote-LU at the SAS/SHARE client. For complete information about defining appropriate LUs for use with SAS/SHARE, see System Configuration for the APPC Access Method.
The server name must meet the criteria for a valid SAS name. See SAS Language Reference: Dictionary for details about SAS naming rules.
An example of specifying the server name follows:
options comamid=appc; libname demo 'C:\' server=remote-lu;
In this example, at the client, the server name is expressed as a remote-LU.
For details about creating LIBNAME, PROC OPERATE, and PROC SERVER statements, see SAS/SHARE User's Guide.
| Client Example |
The following example illustrates the statements that you specify in an OS/2 client configuration file to access a server with the APPC access method:
-comamid appc -set appc_lu62mode appcmode
The APPC communications access method is declared. The APPC_LU62MODE option is set to APPCMODE.
options comamid=appc; libname sasdata 'c:\edc\prog2\sasdata' user=_prompt_ server=share1;
The APPC access method is declared. The LIBNAME statement specifies the name of 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 |
| Authenticating Connecting Clients |
Authenticate users at the server by setting up APPC conversation security within the SASTP62 TP (transaction program) definition.
For further details about setting up TP definitions, see System Configuration for the APPC Access Method.
| Setting Server Security |
To run the server in secure mode, set the CONV_SECURE_RQD parameter in the SASTP62 transaction program to YES. See Defining the SASTP62 Transaction Program for information about setting server security.
| Specifying the APPC Access Method at the Server |
Specify the APPC communications access method before you create and access a SAS/SHARE server.
Use the following syntax to specify the APPC 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. APPC (an abbreviation for Advanced Program-to-Program Communication) 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 the COMAMID option.
Example:
options comamid=appc;
The server will be available only to SAS/SHARE sessions that use the APPC 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 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 appc -comaux1 tcp -comaux2 netbios
When the server starts, all of the communications access methods are initialized. The server is simultaneously available to client sessions that use the APPC access method as well as to clients that use the TCP/IP and NetBIOS access methods.
| Specifying the Server Name |
The server name that you specify in the PROC SERVER statement must be defined as the local-LU at the SAS/SHARE server and as a remote-LU at the SAS/SHARE client. For complete information about defining appropriate LUs for use with SAS/SHARE, see System Configuration for the APPC Access Method.
The server name must meet the criteria for a valid SAS name. See SAS Language Reference: Dictionary for details about SAS naming rules.
An example of specifying the server name follows:
options comamid=appc; libname demo 'C:/\' server=remote-lu;
In this example, at the client, the server name is expressed as a remote-LU.
For details about the PROC SERVER statement, see SAS/SHARE User's Guide.
| Server Example |
The following example illustrates the statements that you specify in a configuration file on the OS/2 host at which you start a server:
-comamid appc
The APPC communications access method is declared.
The following example illustrates the statements that you specify in a SAS session on the OS/2 remote host at which you start a server:
proc server id=share1; run;
The server SHARE1 is started on the OS/2 remote host.
|
Chapter Contents |
Previous |
Next |
 Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.