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

SAS/CONNECT

Local Host Tasks

User or Applications Programmer

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

If connecting to a spawner that is running secured, set a userid and a password to ensure security at the remote host, as required.
Specify the communications access method.
Specify a remote network name.
Sign on to the remote host.

Setting the Remote Host Userid and Password

If you are connecting to an OS/2 remote host by means of a PC spawner program with the -PROTECTION option, you must either assign a valid remote host userid and a password to the SASUSER and SASPASS options or supply them to SAS, when prompted. Set the userid and the password in the following form:

OPTIONS SET=SASUSER userid;
OPTIONS SET=SASPASS password;

Consult with the system administrator of the remote host at which the spawner is invoked for a valid userid and a password.

The SASUSER and the SASPASS options store the userid and the password of the remote host that, when passed to the remote host, allows a local host connection.

Specifying the SPX Communications Access Method

You must specify the SPX 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. SPX (an abbreviation for the Novell Sequenced Packet Exchange protocol) is an example of an access-method-id.

Example:

options comamid=spx;

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=network-name;

where network-name is the NETNAME argument to the PC spawner program that you start on the remote host. The values for the REMOTE= option and the NETNAME argument to the PC spawner must be identical. See Starting the PC Spawner Program for details about specifying the NETNAME argument when starting the PC spawner.

Example:

options remote=mynet;

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;

Note: Sign-on script files are not needed on an OS/2 local host because the SPX access method connects to the spawner program that runs on the remote host. The spawner program then invokes the remote SAS session. This process replaces the need for a script file. [cautionend]

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 identified by the fileref but the SPX access method will ignore the script.

If you do not want to omit the RLINK fileref but want to prevent wasted 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 an OS/2 local host SAS session to connect to a remote host with the SPX access method.

options set=sasuser userid set=saspass password;
options set=spxmsgsize 4202;
options comamid=spx remote=sasrem;
signon;

This example assumes a connection to a PC spawner that is running in secure mode. The SASUSER and SASPASS options allow the userid and the password to be passed to the remote PC spawner, which permits a connection. The SPXMSGSIZE option is set. See SAS/CONNECT and SAS/SHARE SPXMSGSIZE Option for more information. The SPX access method is declared with a connection to the remote host SASREM, which is the name of the network that is specified in the -SPXNAME option at the PC spawner invocation. The SIGNON statement performs the sign-on process.

Remote Host Tasks

System Administrator

To allow a connection from a local host, perform these tasks at the remote host:

Start the PC spawner.
Set several remote host options.

Starting the PC Spawner Program

You must invoke the PC spawner program on the OS/2 remote host to enable local hosts to connect to it. The spawner program resides on a remote host, listening for SAS/CONNECT client requests for connection to the remote host. After the spawner program receives a request, it invokes the remote SAS session. See Starting the PC Spawner Program for more information.

Setting Options at the Remote Host

Although sign-on script files are not used for the SPX access method, you may set remote host options at the remote host. It is recommended that you set these options:

NO$SYNTAXCHECK

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

NO$SYNTAXCHECK 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 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 requires that you explicitly type EXIT at the remote host and gives the appearance that the REMOTE SUBMIT command is hung.

NOXWAIT is valid as part of a configuration file, SAS invocation, or in an OPTIONS statement.

See the SAS Companion for the OS/2 Environment 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 SPX access method:

-dmr
-comamid spx
-no$syntaxcheck
-noterminal
-noxwait

An example for invoking the PC spawner on an OS/2 remote host follows:

c:\sas\connect\sasexe\spawner -comamid spx 
  -protection -spxname sasrem -file mysas.cmd

The spawner is invoked and the SPX access method is specified. The -PROTECTION option verifies the userids and the passwords of connecting clients. The -SPXNAME option specifies the name of the network that the PC spawner program uses to communicate with the local host. The -FILE option executes the MYSAS.CMD file, which invokes a SAS session.

See Starting the PC Spawner Program for information about the contents of a command file and about executing the PC spawner. Options that are set through the spawner override options that are set in a remote host configuration file.

Chapter Contents
Previous
Next
Top of Page