|Communications Access Methods for SAS/CONNECT and SAS/SHARE Software|
|Local Host Tasks|
|Remote Host Sign-on Considerations|
If you are connecting to a Windows 95 remote host, you must connect by means of a spawner program that is already running on the remote host. If you are connecting to a Windows NT, an OS/2 or a UNIX remote host, you optionally, may connect by means of a spawner program that is already 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, you must set the TCPSEC option at the local host. The TCPSEC option stores the userid and the password of the remote host that, when passed to the remote host, allows a local host connection.
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.
If you sign on to a host that is not a Windows NT, a Windows 95, an OS/2, or a UNIX host, you will sign on with a script.
|Configuring the UNIX Spawner Service in the CONFIG.SAS File|
Before connecting to a UNIX remote host with the UNIX spawner program, configure the spawner service in the CONFIG.SAS file on the local host. See Configuring Services in the CONFIG.SAS6xx File for more information.
|Setting the TCPSEC Variable|
If you are not using a script file to sign on to the remote host, you must set the TCPSEC option at the local host. See SAS/CONNECT TCPSEC Option information about setting TCPSEC.
|Specifying the TCP/IP Access Method|
Note: TCP/IP is the default communications
access method on the CMS platforms. You may omit specifying the access method
in a COMAMID option and the TCP/IP access method is assumed, by default.
If you specify the TCP/IP communications access method to make a remote host connection, use the following syntax:
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 in the SAS configuration file.
|Specifying the Remote Node Name|
To make a connection from a Macintosh local host to a remote host, use the following syntax:
The value of node-name that you specify depends on the type of remote host that you are connecting to.
See Starting the UNIX Spawner Program for more information about the UNIX spawner program. See Configuring the SERVICES File for information about configuring the UNIX spawner service in the SERVICES file.
The value of the REMOTE= option must be a valid SAS name. See SAS Language: Reference, Version 6, First Edition for details about SAS naming rules.
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.
%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 the following example, MYNODE).
%let mynode=172.20.10.200; 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 fileref format follows:
filename rlink '!sasroot:misc:script-name';
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:
|Remote Host||Script Name|
|CMS (using full-screen 3270 TELNET protocol)||TCPCMS32.SCR|
|TSO under OS/390||TCPTSO.SCR|
|OS/390 (without TSO)||TCPMVS.SCR|
|OS/390 (using full-screen 3270 TELNET protocol)||TCPTSO32.SCR|
|Windows NT, Windows 95||TCPWIN.SCR|
You must customize the sample scripts to accurately reflect your site's logon process; failure to do so will produce errors. (Your SAS Software Consultant may have altered the sample sign-on scripts as needed.) If someone has altered an automatic logon sample script for users at your installation, you need to load a copy of the modified file onto your local host.
|Signing On to the Remote Host|
To complete your sign on to the remote host, enter the SIGNON statement, as follows:
The following example illustrates the statements that you specify in a Macintosh local host SAS session to connect to a remote host with the TCP/IP access method.
filename rlink '!sasroot:misc:tcpos2.scr'; options comamid=tcp remote=rmtnode; signon;
The first line identifies the script file that you use to sign on to a remote host. The script includes a prompt for a userid and a password that are valid on the remote host. The TCP/IP access method is declared with a connection to the remote host RMTNODE. The SIGNON statement performs the sign-on process.
SAS Institute does not provide support for connections to the Macintosh remote host with the TCP/IP access method.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.