|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:
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 specify this option at a SAS invocation or in a SAS configuration file.
|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, use the following syntax:
where the remote-host-id that you specify at the local host is based on the type of UNIX system that you are running. The following table lists what the remote host identifiers mean on each of the supported UNIX local host types.
|Type of UNIX Local Host||Remote Host Identifier|
|AIX||value of partner LU name if APPC_NET is defined. Otherwise, remote LU alias.|
|HP-UX||partner LU alias.|
|Solaris||unique session name that is defined in the MODE definition and is a combination of mode name, partner LU, and local LU.|
The following table lists what the remote host identifiers mean on each of the supported remote hosts.
|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|
remote host identifiers that are provided at both
the local and remote hosts must be identical.
The remote host identifier that you use is based on the remote host that you connect to.
Alternatively, you may specify the remote-host-id in the REMOTE= 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:
Sign-on script files are not needed on a UNIX local host that uses the APPC access method because APPC has the ability to initiate a 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.
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 that is identified by the fileref, but the APPC access method will ignore 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 UNIX AIX local host configuration file to connect to a remote host with the APPC access method.
-set appc_gateway mygate -set appc_mode appcmode
The APPC_GATEWAY environment variable specifies MYGATE as the name of the peer-to-peer gateway to which the local host will attach. The APPC_SECURE variable specifies that connecting local hosts be prompted for a userid and a password that are valid on the remote host. The APPC_MODE variable specifies the communications mode APPCMODE.
The following example shows the statements that you specify in a local SAS session:
options comamid=appc remote=remotelu; signon user=_prompt_;
The APPC communications access method is declared with a connection to the remote host REMOTELU. 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.
Note: The value for the REMOTE= option that is specified in both
the local and remote sessions must be identical.
|Remote Host Example|
SAS Institute does not provide support for connections to the UNIX remote host with the APPC access method.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.