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

SAS/CONNECT

Local Host Tasks

User or Applications Programmer

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

Specify the APPC communications access method.
Specify the remote host name.
Sign on to the remote host.

Specifying the APPC Communications Access Method

You must specify the APPC communications access method to make a remote host connection, using 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. APPC (an abbreviation for Advanced Program-to-Program Communication) is an example of access-method-id.

Example:

options comamid=appc;

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

Specifying the Remote Host Name

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

OPTIONS REMOTE=remote-LU-alias;

where remote-LU-alias specifies the logical unit of the remote host that you are connecting to. Ask your network administrator for the remote-LU-alias. Types of valid values follow:

Windows APPC SAS/CONNECT REMOTE= Values
Type of Remote Host Remote Host Identifier

OS/390 name of APPC/MVS scheduler LU

CMS name of AVS (APPC/VM VTAM Support) private gateway LU for VM system

VSE name of VTAM APPL ID (ACBNAME) that was set up for APPC LU6.2 communications

OS/2 name of control-point LU or other OS/2 locally defined LU

Windows NT, Windows 95, and Windows 98 name of control-point LU or other SNA Server locally defined LU

***Windows APPC SAS/CONNECT REMOTE= Values***
Type of Remote Host	Remote Host Identifier
OS/390	name of APPC/MVS scheduler LU
CMS	name of AVS (APPC/VM VTAM Support) private gateway LU for VM system
VSE	name of VTAM APPL ID (ACBNAME) that was set up for APPC LU6.2 communications
OS/2	name of control-point LU or other OS/2 locally defined LU
Windows NT, Windows 95, and Windows 98	name of control-point LU or other SNA Server locally defined LU

Example:

options remote=remotelu;

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

Signing On to the Remote Host

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

signon user=_prompt_;

Sign-on script files are not used on a Windows local host that uses the APPC access method because APPC has the ability to communicate directly with the remote host. 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.

Although no errors are produced if you specify a script file, you do waste processing time. If you defined the RLINK fileref before establishing a connection, when you sign on, SAS/CONNECT processes and loads the script file identified by the fileref, but the APPC access method ignores the script.

If you do not want to omit the RLINK fileref but you want to avoid wasting processing time, use the NOSCRIPT option in the SIGNON and SIGNOFF statements, shown as follows:

signon noscript;
.
.
.
signoff noscript;

Local Host Example

The following example illustrates the statements that you specify in a Windows local host configuration file to connect to a remote host with the APPC access method:

-set appc_luname locallu
-set appc_lu62mode appcmode

LOCALLU is the name of the local-LU-alias that is defined at the Windows NT SNA Server. APPCMODE is the mode-name that is defined in the Windows NT SNA server.

The following example shows the statements that you specify in a local SAS session:

options comamid=appc;
options remote=remotelu;
signon user=_prompt_;

The APPC communications access method is declared with a connection to the remote host REMOTELU. In this example, REMOTELU identifies a local LU that is defined at the Microsoft SNA Server. The SIGNON statement performs the sign-on process. 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 Tasks

System Administrator

To allow the local host to make a remote host connection, perform these tasks at the remote host:

Specify the remote host name.
Optionally, set several remote host options.

Specifying the Remote Host Name

You must declare a remote host name at both the local host and the remote host in a SAS/CONNECT session. At both hosts, specify an OPTIONS statement, using the following syntax:

OPTIONS REMOTE=remote-host-id;

where the remote-host-id that you specify at the remote host is based on the type of remote host that you are connecting to. See Windows APPC SAS/CONNECT REMOTE= Values for valid values.

The remote host identifiers that you specify at both the local and remote hosts must be identical.

Example:

options remote=remotelu;

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

Setting Options at the Remote Host

Although sign-on script files are not used for the APPC access method, you may set remote host options at the remote host. It is recommended that you set these options:

NO$SYNTAXCHECK

allows the continuation of statement processing at the remote host regardless of syntax error conditions.

NO$SYNTAXCHECK is valid as part of a configuration file, at a SAS invocation, or in an OPTIONS statement.

NOTERMINAL

specifies whether a terminal is attached at a SAS invocation. If NOTERMINAL is specified, requestor windows are not displayed.

Setting NOTERMINAL at the remote host is advisable so that no terminal is associated with the remote session. NOTERMINAL prevents SAS from displaying error messages and dialog boxes on the remote host, which requires user intervention.

NOTERMINAL is valid as part of a configuration file or at a SAS invocation.

See SAS Language Reference: Dictionary for details about this option.

NOXWAIT

specifies whether you have to type EXIT at the DOS prompt before the DOS shell closes. Setting NOXWAIT at the remote host is recommended to prevent SAS from displaying a dialog box on the remote host. Such a display requires that you explicitly type EXIT at the remote host, and the display gives the appearance that the REMOTE SUBMIT command is hung.

NOXWAIT is valid as part of a configuration file, at a SAS invocation, or in an OPTIONS statement.

See SAS Companion for the Microsoft Windows Environment for details about this option.

Remote Host Example

The following example illustrates the statements that you specify in a Windows NT, a Windows 95, or a Windows 98 remote host's configuration file to prepare for a connection from a supported local host with the APPC access method:

-dmr
-comamid appc
-remote remotelu
-icon
-sasdmr msgqueue
-no$syntaxcheck
-noterminal
-noxwait

The APPC communications access method is declared with a connection to a local-LU-alias REMOTELU.

Note: The value for the REMOTE option that is specified in both the local and remote sessions must be identical. [cautionend]

Chapter Contents
Previous
Next
Top of Page