Chapter Contents

Previous

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

Tasks That Are Common to SAS/CONNECT and SAS/SHARE

System Administrator or User
To use the TCP/IP access method with an OS/390 host for SAS/CONNECT and SAS/SHARE, perform these tasks:
  1. Verify that you have met all your site and software requirements.

  2. Verify that the resources for the TCP/IP access method have been defined.

  3. Verify that you know how to set SAS options.

  4. Set the SAS/CONNECT and SAS/SHARE options that you want.


System and Software Requirements for SAS/CONNECT and SAS/SHARE

SAS/CONNECT and SAS/SHARE require the SAS/C Transient Library when running SAS Release 6.08 TS405 and subsequent releases. (The SAS/C Transient Library is provided with SAS/CONNECT and SAS/SHARE.)

Note:   If your site has installed Release 5.50 of the SAS/C Transient Library, you must replace it with the transient library that is included with SAS/CONNECT and SAS/SHARE. See Installing the SAS/C Transient Library for details.  [cautionend]

SAS/CONNECT and SAS/SHARE also require the Interlink SNSTCP, Version 4.1 or a subsequent release and IBM TCP/IP, Version 3.2 or a subsequent release.


Defining Resources for the TCP/IP Access Method

System Administrator, SAS Site Representative, Applications Programmer, or User
Before you can use SAS/CONNECT or SAS/SHARE with the TCP/IP access method, you must first define TCP/IP resources for the OS/390 system. See System Configuration for the TCP/IP Access Method for the tasks that you perform to define resources for SAS/CONNECT and SAS/SHARE.


Understanding TCP/IP Access Method Terminology

Familiarity with these terms will help you when you set SAS options:

name resolution
The process of mapping a host name to an address. The domain name system provides a facility for naming hosts in which programs use remote name servers to resolve host names into IP addresses for those hosts.

name server
The server program that supplies name-to-address translation, mapping from domain names to IP addresses. The server processor often runs on a dedicated processor, and the host itself is referred to as the name server.

name resolver
The client software that uses one or more name servers when translating a host name.

For a complete discussion of TCP/IP, see Internetworking with TCP/IP, Volume I: Principles, Protocols, and Architecture, Second Edition from IBM.


Setting SAS Options and Variables

You may need to set specific SAS options and variables to establish the desired connections with SAS/CONNECT and SAS/SHARE when using the TCP/IP communications access method.

Consult with your network administrator to determine what options must be set and what values to assign to them.

You may specify an option in several forms, as follows:

Values for these options 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 (_).

Note:   If you set the same option using different forms, typically the last option setting will take precedence and override an earlier option setting.  [cautionend]

Displaying SAS System Option Settings

To display the settings of the SAS system options in the SAS log, use the OPTIONS procedure. The following statement produces a list of options with a brief explanation of what each option does:

proc options;
run;


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 two sections outline the version-specific methods for specifying client identification for SAS/CONNECT and SAS/SHARE. The third section describes how to configure your SAS/SHARE server to either require or not require connecting clients to supply user identification.

Providing Client Identification in a Version 8 Session

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:

SIGNON
RSUBMIT
LIBNAME
PROC SQL
Connect to Remote
PROC OPERATE
(in the PROC statement)
set server
stop server
quiesce server
start server
display server

Specifying client identification in the TCPSEC option is still accepted but is not recommended in Version 8. The USER= and PASSWORD= options take precedence over the client TCPSEC option 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 TCPSEC option 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.

username
is a valid userid for the remote host and is thus host-dependent in form. If the value contains blanks or special characters, it must be enclosed in quotes.

password
is the password, if any, required for authentication of the supplied username. This value will not be echoed in the SAS log. If the value contains blanks or special characters, it must be enclosed in quotes.

_PROMPT_
specifies that the SAS System prompts the client for username and password.

Note:   The values provided when prompted must NOT be quoted.  [cautionend]

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.

Providing Client Identification in a pre-Version 8 Session

In Version 6 and Version 7, you provide client identification to a SAS/CONNECT remote host or a SAS/SHARE server using the TCPSEC option. TCPSEC must be defined on the local host before you connect to the remote host (using the SIGNON statement) or access a SAS/SHARE server (using the LIBNAME statement).

Here is the syntax and description of this option.

TCPSEC=userid.password | _PROMPT_

userid.password
specifies the remote host userid and password and is thus host-dependent in form. If either the userid or password contains blanks or special characters, it must be enclosed in quotes. A period (.) is used as a delimiter between the userid and password and, therefore, is not a valid character.

_PROMPT_
specifies that the SAS system prompt the client for the userid and password.

Note:   The values provided when prompted must NOT be quoted.  [cautionend]
This technique is especially useful when the configuration file specifying this option is shared among many users.

Examples:

TCPSEC=bass.time2go;
TCPSEC=_PROMPT_;

Providing Userid-Based Security for a SAS/SHARE Server

The TCPSEC option also specifies whether the TCP/IP access method performs user authentication before connecting to a SAS/SHARE server. The TCPSEC option must be set on the server before you start the SAS/SHARE server.

Here is the syntax and description of this option.

TCPSEC=_SECURE_ | _NONE_

_SECURE_
The _SECURE_ value for the TCPSEC option causes the TCP/IP access method to attempt to authenticate connecting SAS/SHARE clients. Each client connecting using TCP/IP is required to supply a userid and password valid for the host on which the server is running.

_NONE_
The _NONE_ value for the TCPSEC option causes the TCP/IP access method to NOT attempt to authenticate connecting SAS/SHARE clients. This is the default action when TCPSEC has not been set.

Examples:

TCPSEC=_SECURE_; 
TCPSEC=_NONE_;


SAS/CONNECT and SAS/SHARE Options

You may set these options at the SAS/CONNECT local and remote hosts and at the SAS/SHARE client and server.

ICSRSLV = ONLY | FIRST | LAST | NEVER

Specifies when or if the ICS name resolver is called to resolve an Internet address to a host name.

Note:   This option is available for Interlink TCP/IP sites only.  [cautionend]

ONLY
specifies that only the ICS name resolver is called.

FIRST
specifies that the ICS name resolver is called first. If an error occurs, then the SAS/C resolver is called.

LAST
specifies that the SAS/C resolver is called first. If an error occurs, then the ICS name resolver is called.

NEVER
specifies that the ICS name resolver is never called. The SAS/C resolver is always called.

See Understanding the Search Order for Locating Host Names and Internet Addresses for details about the resolver.

Note:   You may set ICSRSLV in a SAS configuration file, at a SAS invocation, or in a CLIST variable.  [cautionend]

TCPIPMCH=value
identifies which version of TCP/IP to use at sites that simultaneously run multiple versions of TCP/IP.

If the TCPIPMCH option is not defined, SAS uses the name of the address space that is running TCP/IP. If the Interlink TCP/IP is used, then SAS uses the value ACSS. For all other versions of TCP/IP, SAS uses the value TCPIP.

Note:   You may set TCPIPMCH in a SAS configuration file, at a SAS invocation, or in a CLIST variable.  [cautionend]

TCPIPPRF=name
allows you to devise a naming convention for a data set at your site by attaching a descriptive prefix to data set names. For example, to attach the descriptive prefix SYS2.VER2.TCP to the configuration file ETC.HOSTS set the TCPIPPRF option as follows:
TCPIPPRF=SYS2.VER2.TCP

This option setting produces the data set name SYS2.VER2.TCP.ETC.HOSTS.

Note:   The TCPIPPRF option initializes a data set prefix for the current SAS session. You must set this option each time you invoke a SAS session on the local and the remote hosts in a SAS/CONNECT session and at the SAS/SHARE server and client.  [cautionend]

Note:   You may set TCPIPPRF in a SAS configuration file, at a SAS invocation, or in a CLIST variable.  [cautionend]


SAS/CONNECT Only Options and Variables

TCPPORTFIRST
TCPPORTLAST

The TCPPORTFIRST and TCPPORTLAST SAS options restrict the range of TCP/IP ports through which local hosts can remotely connect to remote hosts.

These options must be set at the SAS/CONNECT remote host.

Define the range of TCP/IP ports by assigning a beginning range value to TCPPORTFIRST and an ending range value to TCPPORTLAST, within the range of 0 through 32767.

Consult with your network administrator for advice about these settings.

Use the following syntax for the configuration file:

TCPPORTFIRST=n
TCPPORTLAST=n
Use the following syntax for the AUTOEXEC file:
OPTIONS TCPPORTFIRST=n;
OPTIONS TCPPORTLAST=n;

In the following example, the local host is restricted to TCP/IP ports 4020 through 4050 when making a remote host connection:

options tcpportfirst=4020;
options tcpportlast=4050;

To restrict the range of ports to only one port, you may set the TCPPORTFIRST and TCPPORTLAST options to the same number.

Note:   At the remote host, you may set TCPPORTFIRST and TCPPORTLAST in an OPTIONS statement, at a SAS invocation, in the configuration file, or in the AUTOEXEC file.   [cautionend]

TCPTN3270

TCPTN3270 is an environment variable that is set on the local host to support connections to CMS and OS/390 remote hosts that use the full-screen 3270 TELNET protocol. The following sample script files are provided:
CMS TCPCMS32
OS/390 TCPTSO32

See Identifying a Script File for Signing On and Signing Off for more information.

To set the TCPTN3270 variable, perform the following tasks at the OS/390 local host:

Example CLIST:

tcptn3270(1)

If you do not set this variable, the TCP/IP access method uses the TELNET line mode protocol by default.


SAS/SHARE Only Option

By default, a secure server accepts userids and passwords from clients in either encrypted or plain text form. The option to accept either form ensures compatibility with client sessions running older releases of SAS/SHARE.

To require only encrypted userids and passwords, you must set the AUTHENCR option as an environment variable or a SAS macro variable. Requiring encryption ensures that all clients have been upgraded to Release 6.11 or the 6.09 Enhanced Release of SAS.

Setting this option in a server session enables encryption for clients connecting to a secured server. The values for this option follow:

AUTHENCR=OPTIONAL | REQUIRED

OPTIONAL
means that a client can optionally encrypt the username and the password that it sends to the server. This is the default. When using the default, the server allows connections from clients that are capable of encryption and from clients that are incapable of using encryption because they are running earlier releases of SAS (releases prior to the 6.09E and 6.11) that do not support encryption.

REQUIRED
means that each client must encrypt the username and password that it sends to the server.

For examples of the forms you can use to specify the AUTHENCR option, see Setting SAS Options and Variables.


Chapter Contents

Previous

Next

Top of Page

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