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

SAS/CONNECT

Local Host Tasks

User or Applications Programmer

To connect a CMS local host to a remote host, perform these tasks at the local host:

Consider the requirements of the remote host that you are connecting to.
Configure the Alpha/VMS, the UNIX, or the OS/390 spawner in the SERVICES file, as necessary.
Set security for local hosts.
Specify the communications access method.
Specify a remote host to connect to.
Identify the script file to be used for signing on and signing off, as necessary.
Sign on to the remote host.

Remote Host Connection Considerations

If you are connecting to a Windows 95, Windows 98, or Windows NT remote host, you must connect by means of a spawner program that is already running on the remote host. If you are connecting to an OS/2 , a UNIX, an OS/390, or an Alpha/VMS remote host, you optionally may connect by means of a spawner program, which also must already be running on the remote host. A spawner program allows the encryption of userids and passwords when passed through the network. Without a spawner, readable userids and passwords are passed through the network, which may present a security risk. See Spawner Programs for information about starting the spawner on the remote host.

You may also sign on to the remote host with a script file. If you do not sign on with a script file, as a security measure, set the USER= and PASSWORD= options in the SIGNON statement, which is passed to the remote host, allowing a local host connection.

Note: Setting the Version 7 TCPSEC variable at the local host also works. [cautionend]

If the -NOSCRIPT option is set at the spawner invocation, sign on with a script is prohibited. Ask your network administrator whether the -NOSCRIPT option is set at the spawner invocation.

For all other hosts , you will sign on with a script.

Configuring the Spawner Service in the SERVICES File

Before connecting to either a UNIX, an OS/390, or an Alpha/VMS remote host through a spawner program, configure the spawner service in the SERVICES file on the local host. See Configuring the SERVICES File for more information.

Setting Security for Local Hosts

If you are not using a script file to sign on to the remote host, set security at the local host using either of the methods explained in Setting Security for SAS/CONNECT and SAS/SHARE. For Version 8 security behavior, specify the USER= and PASSWORD= options in the SIGNON statement. For details, see Providing Client Identification in a Version 8 Session.

For Version 7 security behavior, if you set the TCPSEC option at the local host, either specify a userid and a password that are valid on the remote host or specify PROMPT to supply the userid and password when connecting to a remote host. For information about setting the TCPSEC option, see Providing Client Identification in a pre-Version 8 Session.

Specifying the TCP/IP Access Method

You must specify the TCP/IP communications access method to make a remote host connection. Use the following syntax:

OPTIONS COMAMID=access-method-id;

where COMAMID is an acronym for Communications Access Method Identification. access-method-id identifies the method used by the local host to communicate with the remote host. TCP (short for TCP/IP, which is an abbreviation for Transmission Control Protocol/Internet Protocol) is an example of an access-method-id.

Alternatively, you may set this option at a SAS invocation or in the SAS configuration file.

Example:

options comamid=tcp;

Specifying the Remote Node Name

To make a connection from a CMS host to a remote host, use the following syntax:

OPTIONS REMOTE=node-name.service-name;

The value that you specify for node-name is based on the type of remote host that you are connecting to.

If you are connecting to a Windows NT, a Windows 95, a Windows 98, or an OS/2 remote host that is running the PC spawner program, use the name of the node on which the PC spawner is running. See PC Spawner Program for information.
If you are connecting to a UNIX host or an OS/390 host that is running a spawner program, use a two-level name in the form of
```
node-name.service-name
```
where node-name specifies the node on which the spawner program is running and service-name specifies the port on which the spawner is listening for a connection request. See Spawner Programs for more information. See Configuring the SERVICES File for information about configuring the spawner service.
If you are connecting to a remote host platform that uses a sign-on script, use the node name of the remote host. The remote host must be defined in a local HOSTS file or in a domain name server.
The value of the REMOTE= option must be a valid SAS name. See SAS Language Reference: Dictionary for details about SAS naming rules.
Example:
```
options remote=node-name;
```
If you use an Internet address (or some other invalid SAS name), you must assign the address to a macro variable and specify the macro variable as the value of the REMOTE= option.
Example
```
%let node=Internet-address;
options remote=node;
```
Do not choose a macro name that is also a valid host name on your network. SAS first attempts to reach a network host with the value of the REMOTE= option (in this example, MYNODE).
Example:
```
%let mynode=149.999.228.6;
options remote=mynode;
```

Identifying a Script File for Signing On and Signing Off

To use one of the sample script files that is supplied with SAS/CONNECT for signing on and signing off, assign the RLINK fileref to the appropriate script file, depending on the remote host that you are connecting to. The sample scripts are installed at SASCONNE MACLIB. You must customize the sample scripts to accurately reflect your site's logon procedures; failure to do so will produce errors.

The fileref format follows:

filename rlink 'sasconne maclib';

These commands save the script file in the local host's environment.

On the command line in the PROGRAM EDITOR window, enter the following commands:

inc rlink(script-name)
file 'script-name SCR'

Then enter the following statement:

filename rlink 'script-name SCR';

where script-name identifies the script that corresponds to the remote host that you want to connect to.

The following table lists the scripts that are supplied by SAS Institute:

CMS TCP/IP SAS/CONNECT Sign-on Scripts
Remote Host Script Name

CMS TCPCMS

CMS (using fulls-creen 3270 TELNET protocol) TCPCMS32

TSO under OS/390 TCPTSO

OS/390 (without TSO) TCPMVS

OS/390 (using full-screen 3270 TELNET protocol) TCPTSO32

OpenVMS TCPVMS

OS/2 TCPOS2

UNIX TCPUNIX

Windows NT, Windows 95 , and Windows 98 TCPWIN

***CMS TCP/IP SAS/CONNECT Sign-on Scripts***
Remote Host	Script Name
CMS	TCPCMS
CMS (using fulls-creen 3270 TELNET protocol)	TCPCMS32
TSO under OS/390	TCPTSO
OS/390 (without TSO)	TCPMVS
OS/390 (using full-screen 3270 TELNET protocol)	TCPTSO32
OpenVMS	TCPVMS
OS/2	TCPOS2
UNIX	TCPUNIX
Windows NT, Windows 95 , and Windows 98	TCPWIN

Signing On to the Remote Host

To complete your sign on to the remote host, enter the SIGNON statement, as follows:

signon user=_prompt_;

To set security at the remote host, specify valid values for the USER= and PASSWORD= options in the SIGNON statement. For details, see Providing Client Identification in a Version 8 Session.

Local Host Example

The following example illustrates the statements that you specify in a CMS local host SAS session in order to connect to a remote host running the spawner program configured for the TCP/IP access method.

These commands save the script file in the local host's environment. The fileref format follows:

filename rlink 'sasconne maclib';

Issue the following commands from the command line:

inc rlink(tcpunix)
file 'tcpunix scr'

The following statements are issued in the CMS local host SAS session:

filename rlink 'tcpunix scr a';
options comamid=tcp remote=rmthost.unxspawn;
signon user=_prompt_;

The first line identifies the script file that you use to sign on to the UNIX remote host by means of the UNIX spawner program. The script file contains a prompt for a userid and a password that are valid at the remote host. The TCP/IP communications access method is declared with a connection to a remote UNIX spawner, which is identified by the two-level name RMTHOST.UNXSPAWN. The USER= option in the SIGNON statement specifies that the connecting local host be prompted for a userid and a password that are valid on the remote host.

Remote Host

You do not perform any tasks at the CMS remote host for the TCP/IP access method.

Chapter Contents
Previous
Next
Top of Page