Chapter Contents
Previous
Next
|
Chapter Contents |
Previous |
Next |
| Communications Access Methods for SAS/CONNECT and SAS/SHARE Software |
| Local Host Tasks |
| 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 OS/2 local host to connect to 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 set this option at a SAS invocation or in a SAS configuration file.
| Specifying the Remote Host Name |
To make a connection from an OS/2 local host to a remote host, use the following syntax:
OPTIONS REMOTE=remote-session-id;
where remote-session-id specifies the remote host that you are connecting to. Types of valid values are shown in the following table.
| Type of Remote Host | Remote Session Identifiers |
|---|---|
| OS/390 | name of APPC/MVS scheduler LU |
| OS/390 (with TSO) | long or short 3270 terminal emulation session identifier |
| CMS | name of 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 |
Ask your network administrator for the remote-session-id.
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 needed on an OS/2 local host that connects to an OS/390 remote host that uses the APPC access method. APPC has the ability to communicate with the APPC/MVS subsystem to initiate the remote session. 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.
If you specify a script file through the RLINK fileref before establishing a connection, when you sign on, SAS/CONNECT processes and loads the script file that is identified by the fileref. The APPC access method attempts to use the script file but fails, leading to undesirable results.
If you do not want to free the RLINK fileref but want to prevent failure, you must 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 an OS/2 local host SAS session to connect to a remote host with the APPC access method.
options comamid=appc remote=remotelu; options set=appc_lu62mode appcmode; signon user=_prompt_;
The APPC communications access method is declared with a connection to the remote host REMOTELU, which uses a mode name of APPCMODE. 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 |
| Specifying the Remote Host Name |
Specify the remote host name in the configuration file of the OS/2 remote host. Use the following syntax:
-REMOTE remote-host-id
where remote-host-id takes the form of the control-point-LU-of-the-OS/2-remote-host.
You must specify the remote host identifiers at both the local and remote hosts. These remote host identifiers must be identical.
Example:
-remote rmtnode;
| 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 is valid as part of a configuration file, at a SAS invocation, or in an OPTIONS statement.
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.
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 gives the appearance that the REMOTE SUBMIT command is hung and requires that you explicitly type EXIT at the remote host.
This option is valid as part of a configuration file, at a SAS invocation, or in an OPTIONS statement.
See SAS Companion for the OS/2 Environment, Second Edition for details about this option.
| Remote Host Example |
The following example illustrates the statements that you specify in an OS/2 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 -no$syntaxcheck -noterminal
The APPC communications access method is declared with a connection to an OS/2 remote host that is identified as control-point LU REMOTELU.
Note: The value of the REMOTE= option that is specified in
both the local and remote sessions must be identical. ![[cautionend]](../common/images/cautend.gif)
|
Chapter Contents |
Previous |
Next |
 Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.