|Communications Access Methods for SAS/CONNECT and SAS/SHARE Software|
Central to the SNA network is the SNA server, which is responsible for performing connections between local and remote hosts on a local area network (LAN).
Note: An unqualified reference to Windows means all Windows platforms
- Windows NT, Windows 95, Windows 98, and Windows 32s.
You install and configure the SNA server on a Windows NT computer, and you configure SNA clients on any of three Windows platforms: Windows NT, Windows 32s, Windows 95, and Windows 98. After the SNA server and the SNA clients are installed and configured, users of SAS/CONNECT and SAS/SHARE can make connections transparently from their local hosts to the remote hosts that they want by using the SNA server.
The following figure shows an SNA network.
Typical SNA Network Configuration
|Installing the SNA Server|
It is assumed that you already have completed installation of the SNA server product. Before you can configure the SNA server, verify that the following tasks have been completed.
Link services define the protocol that is used between the SNA Server software and the communications adapters installed in your computer (for example, 802.2 Token Ring, Ethernet, SDLC, or X.25).
If the setup program detects more than one network operating system on your computer, you must specify which systems you are using (for example, Microsoft LAN Manager, Novell Netware, or both).
|Configuring the SNA Server|
After you have installed the SNA server and link supports, use the SNA Server Administration Program (SNA Server Admin) to perform the following tasks:
Configure the SNA server by specifying the local Network Name and Control
Specify the connection name (for example, 802.2 Token Ring, SDLC, or X.25) and other properties that are appropriate to your configuration.
Connection properties are the software components of the SNA server
that communicate through the device driver to a particular communications
Perform the following steps to configure the desired number of logical units:
An LU may be dependent or independent. An LU's ability to perform dependently or independently in a SAS/CONNECT remote host session is based on the communications software that your network uses.
SAS/CONNECT can use either a dependent or an independent LU. If you are using dependent LUs, you must have one dependent LU defined for each concurrent remote session established by the local session. A single independent LU allows multiple concurrent SAS/CONNECT sessions.
SAS/SHARE requires an independent LU. When using Remote Library Services (RLS), SAS/CONNECT also requires an independent LU.
You must define all remote LUs to the SNA Server because the Microsoft SNA Server does not support end node (EN) Advanced Peer-to-Peer Networking (APPN) capabilities. You must also define remote (or partner) LUs to connect to a remote host with SAS/CONNECT or to access a SAS/SHARE server.
When defining a remote LU for an MVS remote host in a SAS/CONNECT session, you must also account for the LU pooling capabilities of the remote MVS SAS session so that appropriate surrogate LUs are defined to the SNA Server.
Your options for defining remote LUs follow:
Define the local LU-remote LU pairs, and specify the properties of the communications mode to be used between each pair.
If site-naming conventions permit, specify the mode name SASAPPC. The APPC access method uses this mode name if the APPC_LU62MODE variable has not been defined. See SAS/CONNECT and SAS/SHARE Options for information about setting APPC_LU62MODE.
Specify the minimum contention-winner parameter, which is relevant for SAS software because only contention-winner sessions are used for locally initiated communication.
Communication between SAS/CONNECT local and remote hosts requires only one contention-winner session. However, this limit affects the number of data sets that can be accessed concurrently by means of the SAS/CONNECT Remote Library Services or a SAS/SHARE server.
When defining session limits, define enough sessions so that session limits will never be reached. If session limits are reached, the next time a user attempts to connect to a remote host with SAS/CONNECT or a client host attempts to access a SAS/SHARE server, the APPC layer will not return to the application layer until a session is available. Although a lengthy wait may seem like an error condition (such as no response from SAS or a loop), the underlying APPC layer is waiting for a session to become available.
You have completed the configuration of a Windows NT SNA server.
|Configuring a Windows SNA Client|
Client configuration tasks are based on the platform on which the client is running:
Tasks for configuring a Windows NT, a Windows 95, and a Windows 98 client
Use the SNA Server Client Setup Program to configure Windows NT, Windows 95, and Windows 98 clients.
This section highlights the general tasks that you perform to configure an SNA client. For complete details, see the Microsoft SNA Server Installation Guide and the Microsoft SNA Server Administration Guide. (Contact the Microsoft Corporation for information about this documentation.)
Perform the following tasks:
If you intend to use the Windows
NT, Windows 95, or Windows 98 computer
strictly as a local host connecting to a remote host in a SAS/CONNECT session
or as a client accessing a SAS/SHARE server,
you have successfully completed the configuration process.
If you intend to use either of these computers as a remote host for a SAS/CONNECT session or as a SAS/SHARE server, you must perform additional configuration tasks.
You may execute a program named TPSETUP.EXE, which was supplied by Microsoft and enhanced by SAS Institute, to configure and modify TP properties. Running the program automatically adds entries to the registry, which is a configuration file.
For Windows NT, the TPSETUP.EXE program is located at !sasroot\CORE\WINNT\TPSETUP.EXE. For Windows 95 and Windows 98, the TPSETUP.EXE program is located at !sasroot\CORE\WIN95\TPSETUP.EXE.
The TPSETUP.EXE command with arguments follows:
For Version 7 and later, the APPC access method performs dynamic TP naming which automatically generates the SASTP62 TP definition for you.
Note: Dynamic TP naming is only available when communicating between
two Version 7 (or later) sessions.
For Version 6.12 and earlier, you must still define a SASTP62 transaction program at the host where a SAS/SHARE server will be executing or where a remote SAS/CONNECT session will be established.
To define the SASTP62 transaction program in the registry, specify the following command:
TPSETUP -TP SASTP62
You must define a SASRMT transaction program at the host where a remote SAS/CONNECT session will be established.
To define the SASRMT transaction program in the registry, specify the following command:
TPSETUP -TP SASRMT
Note: For Windows NT, you must run the SASRMT transaction program as
an application, not as an NT service. Therefore, make sure that you start
the Microsoft program TPSTART.EXE before allowing users to establish SAS/CONNECT sessions
with remote hosts.
You have completed the configuration of the Windows NT, Windows 95,
or Windows 98 host as a SAS/CONNECT remote
host or a SAS/SHARE server.
Use the SNA Server Client Setup Program to configure a Windows 32s client.
This section highlights the general tasks that you perform to configure an SNA client. For complete details, see the Microsoft SNA Server Installation Guide and the Microsoft SNA Server Administration Guide.
Note: A Windows 32s host is supported only as a local host that connects to
a remote host in a SAS/CONNECT session.
Perform the following tasks:
You either may edit the WIN.INI file directly, or you may execute a program named TPSETUP.EXE, which is supplied by Microsoft, that automatically updates the configuration file.
The appropriate entries to the WIN.INI file follow:
Define the local-LU that you configured at the SNA server by inserting the following variable assignments in the [sastp62] section of the WIN.INI file:
[sastp62] LocalLU=local-LU-alias Queued=operator
The assignment of a local-LU-alias to a specific Windows 32s client allows the SNA server to route the incoming request for attachment (ATTACH) to the appropriate Windows 32s computer by an alias name. The SNA server checks each Windows 32s client's configuration file for its local-LU-alias to determine where to route the request.
You have completed the configuration of the Windows 32s client.
For details about how to install and configure the SNA server and SNA clients using the SNA Server Setup Program, see the Microsoft SNA Server Installation Guide and the Microsoft SNA Server Administration Guide.
For details about configuring Windows NT Host Security Integration features, see Microsoft SNA Server Getting Started and Installing and Configuring Host Security Integration.
Contact the Microsoft Corporation to obtain information about this documentation.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.