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:

Set security for local hosts.
Specify the communications access method.
Specify the remote host name.
Sign on to the remote host.

Setting Security for Local Hosts

Set security 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 APPCSEC 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 APPCSEC option, see Providing Client Identification in a pre-Version 8 Session.

Specifying the APPC Communications Access Method

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

OPTIONS COMAMID=access-method-id;

access-method-id identifies the method used by the local host to communicate with a 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 specify the COMAMID option at the SAS invocation or in a SAS configuration file.

Specifying the Remote Host Name

To connect a CMS local host to a remote host, use the following syntax:

OPTIONS REMOTE=remote-session-id;

where remote-session-id specifies an entry in a communications directory file.

The following example shows a connection to an MVS/ESA remote host. The remote node N02SV01 is the LU name that is defined in a communications directory file.

Example:

options remote=N02SV01;

Alternatively, you may set this option at a SAS invocation or in the 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_;

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.

You do not need to use a script file because APPC has the ability to interface with the APPC/CMS subsystem to initiate a remote session. If you previously identified a script file in an RLINK fileref statement, you will receive an error message when you attempt to make a connection. If you do not want to omit the RLINK fileref but want to prevent the error, use the NOSCRIPT option in the SIGNON and SIGNOFF statements, as shown here:

signon noscript;
.
.
.
signoff noscript;

Local Host Example

The following example illustrates the statements that you specify in a CMS local host SAS session to connect to a remote host with the APPC access method.

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

The APPC communications access method is declared with a connection to a remote host that is identified by the LU name REMOTELU. The SIGNON statement performs the sign-on process to the remote host. The USER= option to SIGNON 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 a connection from a local host, perform this task 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 the local host and the remote host in a SAS/CONNECT session. At both hosts, specify an OPTIONS statement. Use 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.

The remote host identifiers that you specify at both the local and the 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 these options at the remote host:

NO$SYNTAXCHECK

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

This option is valid when used as part of a configuration file, at a SAS invocation, or in an OPTIONS statement.

NOTERMINAL

specifies whether a terminal is attached at 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. This option prevents SAS from displaying error messages and dialog boxes on the remote host, which requires user intervention.

This option is valid when used as part of a configuration file or at a SAS invocation.

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

Remote Host Example

The following example illustrates the statements that you specify in a CMS remote host's configuration file to prepare for a connection from a local host to a remote host with the APPC access method.

dmr
comamid=appc
remote=remotelu
no$syntaxcheck
noterminal

The APPC communications access method is declared with a connection to a remote host that is identified as the LU name that is configured to the name of the AVS private gateway. In this example, REMOTELU identifies the AVS private gateway.

Chapter Contents
Previous
Next
Top of Page