Chapter Contents


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 APPC access method with an OS/2 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 APPC access method have been defined.

  3. Verify that you know how to set environment variables in SAS software.

  4. Set the desired SAS/CONNECT and SAS/SHARE environment variables that you want.

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

Ensure that the following conditions have been met:

  1. APPC has been installed at both the local and remote hosts at your site.

  2. SAS is installed on both the local and remote hosts.

  3. Release 2.11 or a subsequent release of OS/2 has been installed.

  4. One of the following packages has been installed:

Defining Resources for the APPC Access Method

Network Administrator

Note:   The following describes how to configure an IBM Communications Server. However, other communication products may be used and configured according to their documentation.  [cautionend]

An IBM communications network enables an OS/2 host to provide client and server functionality for both SAS/CONNECT and SAS/SHARE using the APPC communications access method. Before you can use SAS/CONNECT and SAS/SHARE with the APPC access method, you must configure the network through the IBM Communications Manager utility or by editing directly the Network Description File (NDF). Regardless of the configuration method that you use, in this chapter, we refer to the Communications Manager utility. See System Configuration for the APPC Access Method for the procedures to define network resources.

Note:   At present, only a single SAS/CONNECT remote session or a single SAS/SHARE server may be running on an OS/2 workstation at a time because of the global characteristics in the RECEIVE_ALLOCATE interface with Communications Manager.  [cautionend]

Understanding IBM Network Terminology

Familiarity with these terms will help you when you talk to your network administrator about option settings.

LU (logical unit)
a device or program by which a user (LU6.2 applications program) gains access to a network.

local LU
a named LU that is associated with a local host that connects to a SAS/CONNECT remote host or with a client that accesses a SAS/SHARE server.

remote LU
a named LU that is associated with the SAS/CONNECT remote host or with a SAS/SHARE server to which a local host or a client will attach.

LU alias
an alternative name assigned to an LU (local or remote).

For more information about this terminology, see System Configuration for the APPC Access Method.

Setting SAS Options and Variables

You may need to set specific options to establish the connections that you want with SAS/CONNECT and SAS/SHARE when using the APPC access method.

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

Values for these options can 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 option, here is the order of precedence that is allowed:
OPTIONS statement
SAS invocation
SAS configuration file
DOS 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.

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:

Connect to Remote
(in the PROC statement)
set server
stop server
quiesce server
start server
display server

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

Here is the syntax and definitions for these options:



Specifying these options allows a user on the local host whose username and password have been verified to access the remote host.

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.

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.

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

The APPC_SECURE variable passes a remote host userid and password to a remote SAS/CONNECT host or to a SAS/SHARE server for verification. After the userid and the password have been verified, the connection to the remote SAS/CONNECT host or the SAS/SHARE server can proceed.

APPC_SECURE=_NONE_ | _PROMPT_ | userid.password | UPM

must be set at the SAS/CONNECT local host or the SAS/SHARE client. This is the default. Not setting the APPC_SECURE option also selects the default.

Setting _NONE_ does not establish secure sessions for connecting SAS/CONNECT local hosts or SAS/SHARE clients.

must be set at the SAS/CONNECT local host or the SAS/SHARE client.

_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 password provides more security than assigning the userid and password to the system option.

must be set at the SAS/CONNECT local host or the SAS/SHARE client.

userid.password specifies both the userid and password. Assigning the userid and password directly to the APPC_SECURE option at the SAS/CONNECT local host or 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 option in a file allows anyone to read it.

sets the userid and the password through the User Profile Management (UPM) facility, which is included in the APPC access method configuration process. See Security Configuration for details about setting up this profile.

Ensure that the APPC_SECURE option is set before a server is started.


options set=appc_secure _none_;
options set=appc_secure _prompt_;
options set=appc_secure bass.timego;
options set=appc_secure upm;

See Setting SAS Options and Variables for examples of the forms you can use to specify APPC_SECURE.


specifies the name of the local logical unit (LU) to use when connecting to a remote LU. An OS/2 local host may have multiple dependent LUs defined by means of the Communications Manager to support multiple concurrent remote sessions to which it can connect. You may use this option to override the default LU that was defined through the configuration utility.

Ask your network administrator for the name of the local LU that you can use to assign to this option or for the default local LU value.

specifies the communications mode to use. The default mode name is SASAPPC. Whether you assign a mode name to the option or you accept the default SASAPPC, you must identify the mode and use the same mode name value in both the local and remote environments for SAS/CONNECT and SAS/SHARE.

Ask your network administrator for advice about setting this option.

applies only when connecting to an OS/390 remote host.

APPC_SURROGATE_LUNAME specifies an LU to use for a SAS/CONNECT remote session on an OS/390 host. If this option 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.

Ask your network administrator for the name of the remote LU for the OS/390 host that you can use to assign to this option.

Note:   Do not use this option's value for the value of the REMOTE= option in SAS/CONNECT .  [cautionend]

SAS/SHARE Option Only

identifies individual output in the server's output log.

Chapter Contents



Top of Page

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