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 at the local host:

Optionally set a userid and a password to ensure security at the remote host.
Specify the communications access method.
Specify a 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 -SECURITY option, either you may be required to assign a valid remote host userid and a password to the SASUSER and SASPASS options or you must supply them to SAS, when prompted.

Set security at the local host using either of the methods explained in Setting Security for SAS/CONNECT and SAS/SHARE. For Version 8 security behavior, specify the USER= and PASSWORD= options to the SIGNON statement. For details, see Providing Client Identification in a Version 8 Session.

For Version 7 security behavior, if you set the SASPASS and SASUSER options at the local host, either specify a userid and a password that are valid on the remote host or specify _PROMPT_ to supply the userid and password when connecting to a remote host. For information about setting the SASUSER and SASPASS option, see Providing Client Identification in a pre-Version 8 Session.

See PC Spawner Program for information about starting the spawner on the remote host.

Specifying the NetBIOS or MNetBIOS Communications Access Method

You must specify the appropriate 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.

The access-method-id that you supply depends on whether you use the IBM NetBIOS 3.0 Interface or the LAN Manager 1.0 Submit Interface.

For IBM NetBIOS 3.0 Interface: use NETBIOS, which is an acronym for Network Basic Input/Output System.
For LAN Manager 1.0 Submit Interface: use MNETBIOS, which is an acronym for Microsoft Network Basic Input/Output System.

Examples:

options comamid=netbios;

options comamid=mnetbios;

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

Specifying the Network 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 option 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 PC Spawner Program for details about specifying the NETNAME argument when starting the PC spawner.

Example:

options remote=sasrem;

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_;

The USER= option in the SIGNON statement specifies that the local host be prompted for a userid and a password that are valid on the remote host. Sign-on script files are not needed on an OS/2 local host because the NetBIOS 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.

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 NetBIOS 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 an OS/2 local host SAS session to connect to a remote host with the NetBIOS access method.

options set=vqmlinks 3 set=vqmconvs 3;
options comamid=netbios remote=sasrem;
signon user=_prompt_;

This example assumes a connection to a PC spawner that is running in secure mode. Two options are set; see SAS/CONNECT and SAS/SHARE Options for details. The NetBIOS communications access method is declared with a connection to a remote host that is identified as SASREM, which is the name that is specified in the -NETNAME option at the PC spawner invocation. 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. The SIGNON statement performs the sign-on process.

Remote Host Tasks

System Administrator

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

Start the spawner program.
Set several remote host options, as necessary.

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 NetBIOS 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 or at SAS invocation.

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 SAS invocation.

See SAS Language Reference: Dictionary for details about this option.

NOXWAIT

applies to OS/2 or Windows remote hosts only.

NOXWAIT specifies whether you have to type EXIT at the OS/2 prompt before the OS/2 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.

NOXWAIT is valid as part of a configuration file, at a SAS invocation, in or 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 NetBIOS access method.

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

An example follows of how the PC spawner is invoked on an OS/2 remote host:

c:\sas\connect\sasexe\spawner -comamid netbios -netname sasrem 
                              -file mysas.cmd

The spawner is invoked, and the NetBIOS access method is specified. The -NETNAME option specifies the name 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 the remote host configuration file.

Chapter Contents
Previous
Next
Top of Page