|Communications Access Methods for SAS/CONNECT and SAS/SHARE Software|
The APPC access method on the UNIX platform supports the SAS/SHARE client only.
|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 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:
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.
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 a UNIX client connecting to a Windows NT server follows:
-comamid appc -comaux1 tcp
If the server cannot be reached using the APPC access method, a second attempt is made with the TCP/IP access method.
|Specifying a Server Name|
The server name that you specify in the PROC OPERATE and the LIBNAME statements must be defined at the SAS/SHARE server and the client.
The form of the server name is based on the type of host on which the server is running. For the correct form of the server name, ask the network administrator of the appropriate remote host on which the server runs.
The following table specifies server names by host type.
|Type of Server Host||Server Identifier|
|OS390||name of APPC/MVS scheduler LU|
|CMS||name of AVS (APPC/VM VTAM Support) private gateway LU for VM system|
|VSE||name of VTAM APPL ID (ACBNAME) that was set up for APPC LU6.2 communications|
|OS/2||name of control-point LU or other OS/2 locally defined LU|
|Windows NT, Windows 95, and Windows 98||name of control-point LU or other SNA server locally defined LU|
For complete information about defining appropriate LUs for use with SAS/SHARE, see System Configuration for the APPC Communications Environment.
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 a server name follows:
options comamid=appc; libname demo 'C:\' server=server-id;
In this example, you might specify the name of the server that is running on a Windows NT system (for example, the SNA server LU).
Note: If the server is running on a CMS system that is connected to your system by means of a VTAM AVS gateway, you must use a two-level server name specification as follows:
libname demo 'demo a' server=gateway.server;
where gateway is defined to the CMS system as the AVS-gateway
For details about creating LIBNAME and PROC OPERATE statements, see SAS/SHARE User's Guide.
The following example illustrates the statements that you specify in a UNIX client session to access a Windows NT server with the APPC access method:
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.
SAS Institute does not provide support for connections to a server that runs on a UNIX host with the APPC access method.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.