|Communications Access Methods for SAS/CONNECT and SAS/SHARE Software|
|System and Software Requirements for SAS/CONNECT and SAS/SHARE|
Ensure that the following conditions have been met:
The system requirements for the APPC access method in the UNIX environments are based on which vendor's type of UNIX operating system that you are using. SAS Institute supports the APPC access method on the following types of UNIX systems:
To use the APPC access method under AIX, your site must meet the following requirements:
To use the APPC access method under HP-UX, your site must meet the following requirements:
Note: The Solaris platform is not supported in Version 7 or later.
To use the APPC access method under Solaris, your site must meet the following requirements:
|Configuring the APPC Access Method|
|Understanding APPC Communications Terminology|
Familiarity with these terms will help you when you talk to your network administrator about variable settings.
For more information about this terminology, see System Configuration for the APPC Communications Environment.
|Setting Variables in SAS|
You may need to set specific variables to establish the connections that you want with SAS/CONNECT and SAS/SHARE when using the APPC communications access method.
Consult with your network administrator to determine what variables must be set and what values to assign to them.
You may specify a variable in any of several forms, as follows:
Note: In these examples, the variable name varies according to the form
APPC_SECURE is the environment variable form; APPCSEC is the macro variable
-SET variable-name value
-set appc_secure _none_
Korn shell: export VARIABLE-NAME=value
C shell: setenv VARIABLE-NAME value
export APPC_SECURE=_NONE_ setenv APPC_SECURE _NONE_
Values for these variables may contain up to eight characters, consisting of alphanumeric characters, the percent sign (%), the dollar sign ($), the pound sign (#), the at sign (@), and the underscore (_).
If you set multiple forms of the same variable, here is the order of precedence that is followed:
|SAS macro variable|
|SAS configuration file|
|UNIX environment variable.|
|Setting Security for SAS/CONNECT and SAS/SHARE|
For SAS/CONNECT, you must
supply identifying information to sign on
without a script to a remote host running a spawner program. A SAS/SHARE server,
running secured, requires identification from each connecting client. The
next several sections outline the alternatives for storing security information
for SAS/CONNECT and SAS/SHARE.
In Version 8, you provide client identification to a SAS/CONNECT remote host or a SAS/SHARE server using the USER= and PASSWORD= options. These options are valid in the following statements:
Connect to Remote
Specifying client identification in the APPCSEC variable is still accepted but is not recommended in Version 8. The USER= and PASSWORD= options take precedence over the client APPCSEC variable when both are specified. For example, a SAS/SHARE client's execution of a LIBNAME statement with values assigned to the USER= and PASSWORD= options would override a APPCSEC variable setting in the same client SAS session.
Here is the syntax and definitions for these options:
|USER | USERNAME | USERID | UID=username | _PROMPT_|
|PASSWORD | PASSWD | PASS | PWD | PW=password | _PROMPT_|
Specifying these options allows a user on the local host whose username and password have been verified to access the remote host.
Note: The values provided
when prompted must NOT be quoted.
Specifying USER=_PROMPT_ and omitting the PASSWORD= specification will cause SAS to prompt you for both userid and password.
This is especially useful for allowing the SAS statements containing the USER= and PASSWORD= options to be copied and otherwise effectively reused by others.
For SAS/SHARE, the values supplied for the USER= and PASSWORD= options are valid for the duration of the remote host connection. Additional accesses of the remote host while the connection to that host is still in effect do not require re-supplying of the USER= and PASSWORD= options. For example, while the first connecting library assign to a SAS/SHARE server may require specification of the options, subsequent assigns to the same server will not need specification of these options as long as the original connection is in effect. A subsequent re-connect to the same server or connect to a different server would require re-supplying of the USER= and PASSWORD= options.
Here is a Version 8 example for SAS/SHARE:
libname test 'prog2 a' user=joeblue password="2muchfun" server=share1;
For SAS/CONNECT, these values are valid until SIGNOFF.
Here is a Version 8 example for SAS/CONNECT:
signon rmthost user=joeblack password=born2run;
As a security precaution, PASSWORD= field entries echoed in the log
are replaced with Xs. If _PROMPT_ was specified for entering the password,
the entry would not be displayed on the screen as it is typed.
Both the environment variable and SAS macro variable forms are provided, as appropriate. Use the SAS macro variable for run-time specification.
Setting this value does not establish secure sessions for connecting SAS/CONNECT local hosts or SAS/SHARE clients.
_PROMPT_ specifies that SAS prompt the user for userid and password information. When prompted for a password, the input field is not displayed. Choosing to prompt for a userid and a password provides more security than assigning the userid and password to the environment variable or the macro variable.
This value specifies both the userid and password. Assigning the userid and the password directly to the APPCSEC variable at the SAS/CONNECT local host or at the SAS/SHARE client may inadvertently publicize this information and compromise the security of the SAS/CONNECT remote host or the SAS/SHARE server. Assigning the value to the variable in a file allows anyone to read it.
If the userid or the password contains numeric or special characters, enclose the entire userid.password in quotation marks.
Note: You must specify security for OS/390, CMS, and VSE remote hosts. However,
security is not required for OS/2 or Windows hosts unless session security
has been explicitly defined.
Macro variable examples:
%let appcsec=_none_; %let appcsec=_prompt_; %let appcsec='bass.time2go';
|SAS/CONNECT and SAS/SHARE Variables|
These variables specify the name of the peer-to-peer gateway that you will attach to.
The gateway provides the SNA stack for connecting to an SNA network.
If you are working in a stand-alone environment and your gateway has the same
name as your machine, do not specify this variable. By default, SAS uses
gethostname UNIX function to obtain the machine name
on which SAS is running and then uses that name as the gateway name.
In a SunLink SNA Peer-to-Peer configuration, specify the gateway name
either in a local
/etc/appcs file or in the NIS/NIS+ database.
These variables specify the name of the local LU alias to use.
This name must match an LU alias that is established during configuration. This variable is required unless a default local APPC LU has been defined.
These variables specify the communication mode that represents the set of networking characteristics that are defined during configuration.
The default communications mode name is SASAPPC. This name must be defined in both the local and remote environments regardless of whether you specify it explicitly or you allow it to default to SASAPPC.
These variables specify the network name that is used when forming the fully-qualified remote LU name in APPN environments.
This name is required to exploit APPN connections in the absence of explicitly configured remote LU profiles.
This variable specifies the number of simultaneous partners that this local session will have at one time. This estimate improves allocation of memory resources for internal control block usage.
|SAS/CONNECT Only Variable|
If this variable is not defined, the OS/390 remote session dynamically selects an LU from the pool of LUs that is defined on the OS/390 host for this purpose.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.