Chapter Contents
Previous
Next
Communications Access Methods for SAS/CONNECT and SAS/SHARE Software

SAS/SHARE

Client Tasks

System Administrator or User
To prepare to access a SAS/SHARE server, perform the following tasks:
  1. Set security for connecting clients.

  2. Specify the APPC access method.

  3. Specify a server name.

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 Communications Access Method

You must specify the APPC communications access method at the connecting 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 that is 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 a Windows 95 client connecting to an OS/390 server follows: 

comamid=appc
comaux1=tcp

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

Specifying a Server Name

You must specify the server name in the LIBNAME and the PROC OPERATE statements as follows: 

SERVER=server-id

where server-id is defined in an APPL statement when configuring the OS/390 system for use with the APPC access method. The APPC syntax allows a server name that contains up to eight characters. Because APPC and SAS naming requirements are compatible, there should be no naming conflict. See System Configuration for the APPC Access Method for SAS/SHARE for details about defining an LU for the server.

An example of specifying a server name from a client follows: 

libname demo 'SAS.DATA.LIB' server=server-id;

where server-id is defined when configuring the OS/390 host for the APPC access method. See System Configuration for the APPC Access Method for SAS/SHARE for information about specifying a server identifier.

See SAS Language Reference: Dictionary for details about SAS naming rules. See SAS/SHARE User's Guide for details about the PROC OPERATE and LIBNAME statements.

Client Example

The following example illustrates the statements that you specify in an OS/390 client configuration file to access a server with the APPC access method: 

luprefix=sascon
lufirst=1
lulast=10
lu62mode=appcmode

LUPREFIX SASCON is specified with the LUFIRST and LULAST options to form ACBNAME LU names ranging from SASCON01 to SASCON10. The LU62MODE name is APPCMODE. 

options comamid=appc;
libname sasdata '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

Server Administrator
Perform the following tasks at the server:
  1. Verify that the SAS SVC routine has been installed.

  2. Set server security by means of the APPCSEC option.

  3. Specify the APPC access method.

  4. Specify the server name.

Installing the SAS SVC Routine

The SAS SVC control program routine is an interface between the OS/390 operating system and a specific request, such as "third-party checking." This facility provides verification in the form of calls for authentication of both the userid and password and of library authority.

  1. Install the SAS SVC routine, if necessary.

    If you have already installed the SAS SVC routine for Release 6.09E of SAS software, do not repeat the step here. If you need to perform the installation, see the Installation Instructions and System Manager's Guide, The SAS System under OS/390 for details.

    Because SAS SVC in Release 6.09E is backward compatible, it replaces the SAS SVC routines from previous releases. You may continue using previous releases of base SAS and SAS/SHARE with the Release 6.09E SAS SVC that is installed on your system.

  2. Verify the SAS options for the SVC routine.

    You must verify that the SAS options for the SVC routine accurately reflect the way that the SAS SVC is installed. The SAS option SVC0SVC should be set to the number at which the SAS SVC is installed (for example, 251 or 109). If the SAS SVC is installed at 109 as an ESR SVC, the SAS option SVC0R15 should be set to the ESR code (for example, 4).

  3. Verify installation on all CPUs, as needed.

    If you have more than one CPU, verify that the SAS SVC routine is installed on the systems that will be running SAS/SHARE at your site.

Setting Server Security

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 both valid userids and passwords for the host at which the server is running. A secured server uses the validated userid and password to verify a user's authority to access a SAS library or a SAS file.

Requiring connecting clients to supply both a valid userid and password enforces server security. At the server, set the APPCSEC option to the value _SECURE_. For information about setting the APPCSEC option, see Providing Client Identification in a pre-Version 8 Session.

Specifying the APPC Access Method

You must specify the APPC communications access method at the server before you create 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 only 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. Use 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 an OS/390 host follows: 

comamid=appc
comaux1=tcp
comaux2=xms

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 XMS access methods.

See SAS/SHARE User's Guide for details about starting a server.

Specifying a Server Name

You must specify the server name in the PROC SERVER statement using the following syntax: 

SERVER=server-id

where server-id is defined in an APPL statement when configuring the OS/390 system for use with the APPC access method. The APPC syntax allows a server name that may contain up to eight characters. Because APPC and SAS naming requirements are compatible, there should be no naming conflict. See System Configuration for the APPC Access Method for SAS/SHARE for details about defining an LU for the server.

An example of specifying a server name from a client follows: 

libname demo 'SAS.DATA.LIB' server=server-id;

where server-id is defined when configuring the OS/390 host for the APPC access method. See Defining an LU Pool for information about specifying a server identifier.

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 configuration file on the OS/390 host at which you start a server: 

appcsec=_secure_
comamid=appc

The _SECURE_ value for the APPCSEC option requires clients to supply a userid and a password that are valid on the server.

The following statements in a SAS session on the OS/390 remote host start a server: 

proc server id=share1 authenticate=req;
run;

The server SHARE1 is started on the OS/390 remote host.


Chapter Contents
Previous
Next
Top of Page

Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.