|Communications Access Methods for SAS/CONNECT and SAS/SHARE Software|
Perform the following tasks to set up the Wall Data APPC engine:
After you have completed the installation and configuration of this product, users of SAS/CONNECT can make connections from their SAS/CONNECT local hosts transparently by means of the SNA network to the selected remote host.
This section highlights the general procedures that you must perform to connect to an SNA network. For details about how to install and configure the Wall Data APPC Engine with the Rumba APPC Configuration Utility, see Wall Data product literature.
|Configuring Network Properties|
Define the network properties using the Rumba APPC Configuration Utility.
device=dxme0mod.sys device=dxmt0mod.sys ES=X EST=X
Be sure to specify the appropriate path.
|Configuring Connections, Logical Units, and Modes|
Perform these tasks using the Rumba APPC Configuration Utility:
Connection properties are the software components of the SNA server that communicate by means of the device driver to a particular communications adapter.
Specify the connection name (for example, Token Ring, SDLC) and other
properties that are appropriate to your configuration.
Configure the local logical units (LUs) to be used.
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 that is established by the local session. A single independent LU allows multiple concurrent SAS/CONNECT sessions.
When using Remote Library Services (RLS), SAS/CONNECT requires
an independent LU.
You must specify a remote LU to connect to a SAS/CONNECT remote session. You may define a remote LU using any of the following three forms:
For example, to specify a fully
qualified remote LU in a SAS/CONNECT session,
specify the partner LU name in the REMOTE= option and specify the network
identifier in the CPIC_NET option (see SAS/CONNECT Options).
After you have configured and paired local LUs and remote LUs, specify the properties of the communications mode that is to be used between each pair.
If site-naming conventions permit, specify the mode name SASAPPC. The CPIC access method uses this mode name if CPIC_LU62MODE has not been defined. See SAS/CONNECT Options for information about setting the CPIC_LU62MODE option.
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 through a specific SAS/CONNECT remote host.
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 by using SAS/CONNECT, 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, a loop or no response from SAS), the underlying APPC layer is waiting for a session to become available.
|Optionally Configuring CPIC Properties|
Properties include a remote host's symbolic name, a partner LU, a partner
LU alias, a mode, and security features. You may select these properties instead
of setting the CPIC_LU62MODE and CPIC_SECURE options. See SAS/CONNECT Options for more information.
For complete details about how to install and configure the APPC system, see the following documents:
|IBM SNA: Technical Overview (GC30-#073)|
|IBM SNA: Formats (GA27-3136)|
|IBM: Multiplatform APPC Configuration Guide (GG24-4485-00)|
Contact IBM for information about obtaining this documentation.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.