Chapter Contents
Previous
Next
Communications Access Methods for SAS/CONNECT and SAS/SHARE Software

SAS/CONNECT

Local Host Tasks

User or Applications Programmer
To connect an OS/390 local host to a remote host, perform these tasks at the local host:
  1. Specify the communications access method.

  2. Specify the remote node name.

  3. 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. 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. APPC (an abbreviation for Advanced Program-to-Program Communication) is an example of access-method-id.

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

Example: 

options comamid=appc;

Specifying the Remote Host Name

To connect an OS/390 local host to a remote host, use the following syntax: 

OPTIONS REMOTE=remote-session-id;

where remote-session-id specifies the logical unit of the remote host that you are connecting to. Types of valid values for the REMOTE= option follow:

OS/390 APPC SAS/CONNECT REMOTE= Values
Type of Remote Host Remote Host Identifier
OS/390 (with ESA) logical unit name that is configured to the APPC (OS/390) scheduler
CMS name of the AVS gateway
OS/2 name of a control-point LU or other OS/2 locally defined LU
Windows NT, Windows 95 , and Windows 98 name of a control-point LU or other SNA Server locally defined LU
OS/390 (with TSO) for a scripted sign on to TSO, if the local host is OS/2, specify the 3270 EHLLAPI short or long session identifier of the remote 3270 session. (You define the short and long session identifiers in your emulation program.)
VSE name of the VTAM APPL ID (ACBNAME) that was set up for APPC LU6.2 communications

Example: 

options remote=NO2SV01;

The remote node NO2SV01 is the LU name of the remote host that you want to connect to.

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

Ask your network administrator for the remote-session-id .

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 an OS/390 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 the remote host REMOTELU. 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 a connection from a local host, perform these tasks at the remote host :
  1. Know the conditions under which an OS/390 host can be used as the remote host.

  2. Specify the remote host name.

  3. Optionally, set several remote options at the remote host.

Using the OS/390 Host as a Remote Host

To use the OS/390 host as a remote host, make sure that it meets the following requirements:

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, you specify an OPTIONS statement with 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 OS/390 APPC SAS/CONNECT REMOTE= Values for valid values.

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 remote host 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 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 recommended 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 as part of a SAS 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 an OS/390 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
luprefix=sascon
lufirst=1
lulast=10
lu62mode=appcmode
lupool=all
no$syntaxcheck
noterminal

The APPC communications access method is declared with a connection to REMOTELU, which is the LU name of the APPC/MVS scheduler. LUPREFIX SASCON is specified with the LUFIRST and LULAST values to form ACBNAME LU names ranging from SASCON01 to SASCON10. The LU62MODE name is APPCMODE, and an LUPOOL value of ALL specifies pool use for both local and remote OS/390 SAS sessions.

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


Chapter Contents
Previous
Next
Top of Page

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