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

SAS/CONNECT

System Administrator or User

To use the EHLLAPI access method with an OS/2 host for SAS/CONNECT, perform these tasks:

Verify that you have met all your site and software requirements.
Verify that you know how to set options in SAS software.
Set the SAS/CONNECT options that you want.

System and Software Requirements for SAS/CONNECT

Ensure that the following conditions have been met:

The EHLLAPI software has been installed at both the local and remote hosts at your site.
SAS software has been installed on both the local and remote hosts.
A supported emulation package has been installed on the OS/2 host. The following emulation products are supported:
- the IBM CM/2 Version 1.11 or subsequent version.
- the eNetwork Personal Communications, Version 4.2 or higher.
- any OS/2 2.11 or subsequent release of an emulation program that supports the EHLLAPI standard.

Setting SAS Options

You may set specific options to establish the connections that you want with SAS/CONNECT when using the EHLLAPI communications access method.

You may specify an option in several forms, as follows:

in an OPTIONS statement in a SAS session or in an AUTOEXEC file:
OPTIONS SET=variable-name value;
Example:
```
options set=vqdllname pcshll32.dll;
```
in a SAS configuration file or at a SAS invocation:
-SET variable-name value
Example:
```
-set vqdllname pcshll32.dll
```
as a DOS operating system environment variable:
SET variable-name=value
Example:
```
set vqdllname=pcshll32.dll
```

Values for these options can contain up to eight characters, consisting of alphanumeric characters, the percent sign (%), the dollar sign ($), the pound sign (#), the at sign (@), and the underscore (_).

If you set multiple forms of the same option, here is the order of precedence that is followed:

OPTIONS statement

AUTOEXEC file

SAS invocation

SAS configuration file

DOS environment variable.

SAS/CONNECT VQDLLNAME Option

VQDLLNAME

assigns explicitly the Dynamic Link Library (DLL) name to the VQDLLNAME option if vendor module-naming presents conflicts or if your package's DLL is not in the default search list.

Example:

options set=vqdllname pcshll32.dll;

The PCSHLL32.DLL module is assigned explicitly to the VQDLLNAME option.

Local Host Tasks

System Administrator or User

Specify the name of the remote session identifiers when you configure the emulation package to communicate between the OS/2 host and the remote host.

See the documentation that accompanies the emulation software for information about remote session identifiers.

User or Applications Programmer

To connect an OS/2 local host to a remote host, perform these tasks:

Identify the DLL modules that are supplied with your emulation package, as necessary.
Specify the communications access method.
Specify a remote host.
Identify the script file to be used for signing on and signing off.
Sign on to the remote host.

Identifying the Dynamic Link Library (DLL) Modules

SAS/CONNECT looks for EHLLAPI standard DLL modules for the OS/2 host in this order:

PCSHLL32: the IBM 32-bit emulator API interface DLL
ACS3EHAP: the IBM/DCA 16-bit emulator API interface DLL. This is the default.

If your package's DLL is not in the default search list, you must assign the DLL name to the VQDLLNAME option.

Note: Do not specify a disk drive name or a full pathname in the DLL-library-file name. [cautionend]

Specifying the EHLLAPI Communications Access Method

Specify the EHLLAPI communications access method to make a remote host connection by 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.

EHLLAPI (an acronym for Extended High-Level Language Applications Programming Interface) is an example of access-method-id

Example:

options comamid=ehllapi;

Alternatively, you may specify this option at a SAS invocation, in a SAS configuration file, or in an AUTOEXEC.SAS 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 can be the short or the long session identifier of the remote session.

The system administrator specifies the names of the remote session identifier when configuring the emulation package to communicate between the OS/2 host and the remote host. Ask your system administrator for the appropriate session identifier.

For more information about remote session identifiers, see the documentation that accompanies the emulation software.

Example:

options remote=a;

Alternatively, you may specify this option at a SAS invocation, in a SAS configuration file, or in an AUTOEXEC.SAS file.

Identifying a Script File for Signing On and Signing Off

To use one of the sample script files that is supplied with SAS/CONNECT for signing on and signing off, assign the RLINK fileref to the appropriate script file, based on the remote host that you are connecting to. The sample scripts are installed in !SASROOT\CONNECT\SASLINK. The fileref format follows:

FILENAME RLINK '!sasroot\connect\saslink\script-name';

where script-name identifies the script that corresponds to the remote host that you want to connect to.

The following table lists the scripts that are supplied by SAS Institute:

OS/2 EHLLAPI SAS/CONNECT Sign-on Scripts
Type of Remote Host Script File

CMS CMS.SCR or LOGCMS.SCR

OS/390 TSO.SCR or LOGTSO.SCR

VSE VSE.SCR or VSECICS.SCR

***OS/2 EHLLAPI SAS/CONNECT Sign-on Scripts***
Type of Remote Host	Script File
CMS	CMS.SCR or LOGCMS.SCR
OS/390	TSO.SCR or LOGTSO.SCR
VSE	VSE.SCR or VSECICS.SCR

Each set of scripts for each host basically performs the same tasks. However, the first script assumes that you have already logged in to the remote host; the second script includes code that prompts for the userid and the password.

You must customize the sample scripts to accurately reflect your site's logon process. Failure to do so will produce errors.

Signing On to the Remote Host

To complete your sign on to the remote host, enter the sign-on command. An example of how you might sign on to a CMS host follows:

filename rlink '!sasroot\connect\saslink\cms.scr';
options comamid=ehllapi remote=a;
signon;

In the first line, the filename RLINK is assigned to a script that is appropriate to the remote host. In the second line, the EHLLAPI communications access method is declared with a remote connection to a host identified as A. The SIGNON statement makes a connection to the remote host.

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 EHLLAPI access method.

filename rlink '!sasroot\connect\saslink\logtso.scr';
options comamid=ehllapi remote=a;
signon;

The first line identifies the script file that you use to sign on to the remote host. The script file contains a prompt for a userid and a password that are valid on the remote host. The EHLLAPI communications access method is declared with a connection to a remote host that is identified as A, which is the remote session identifier that is specified when configuring the emulation package on your local host. The SIGNON statement performs the sign-on process.

Remote Host Example

SAS Institute does not provide support for connections to the OS/2 remote host with the EHLLAPI access method.

Connecting to a CMS or an OS/390 Remote Host

If you use the EHLLAPI access method to connect an OS/2 local host to either a CMS or an OS/390 remote host, you must also specify the PCLINK access method on the remote host.

An example of specifying PCLINK as the remote host access method is

options comamid=pclink;

Chapter Contents
Previous
Next
Top of Page

	OPTIONS statement
	AUTOEXEC file
	SAS invocation
	SAS configuration file
	DOS environment variable.