|Microsoft SNA Server v2.11
|Support for Attachmate EXTRA! Personal Client
Note: Screen snapshots are copyright Wall Data Incorporated
This document provides sample views of an 802.2 DLC connection for Wall Data Rumba Office 95/NT. We have validated the CCIAPPC component against Rumba Office 95/NT version 5.0. This document is arranged in a logical sequence for an new installation of the Rumba product.
The Rumba product requires the Microsoft 32-bit DLC protocol to provide support for a connection over 802.2. You should already have installed the 32-bit DLC driver for Windows 95 or Windows NT. If you have not yet done this, please follow the instructions for installing this driver in Configuring DLC over 802.2 on Windows 95 or Configuring DLC over 802.2 on Windows NT.
You should have already installed Rumba Office 95/NT. We suggest that you install using the custom install options to insure that the APPC Client, the 802.2 DLC Interface, and the Rumba Communications Monitor is installed. The APPC Client must be selected and would not normally be installed if using the express installation.
After successfully installing the Rumba Office 95/NT product, you can start to configure your APPC connection. You should have a VTAM definition of the connection you are attempting to configure available to you during the configuration. Select Start from the Taskbar, then Programs, then Rumba 95 NT Folder, then Rumba Administrative Tools, then APPC Configuration. The APPC Configuration window will be displayed. A sample window with a full configuration is displayed below for reference. Your window will have some default values filled in, you can override these and configure your own connection using the instructions below.
The first screen presented in the configuration tool allows you to enter a Network Name and Control Point Name. Enter the network name for this SNA network. This should be obtained from the network administrator of the host system. Enter the Control Point (CP) name assigned to this machine. This should be obtained from the network administrator of the host system. The CP Name should match the Physical Unit (PU) name assigned to this machine as specified in the PU definition in VTAM for this machine.
Select Connections by clicking in the Connections portion of the configuration window, then click the Add button. The Select a Connection window will appear. Select the type of physical network connection which will be used, in this case 802.2 DLC (Token Ring and Ethernet) and select OK. If you are using an alternative network connection type, such as SDLC or DFT Coax for instance, ensure that you have already installed a device driver for the network adapter.
In the 802.2 DLC Configuration dialog box, select the Advanced tab by clicking on it and enter the following parameter settings:
Before attempting to communicate using CCIAPPC you must define the local and remote LUs which will be used to communicate over the SNA connection you have configured. In this section we will describe the configuration of Independent LUs to be used to communicate over the host connection. When communicating with Host systems running VTAM (or NCP) the Remote LU is known as the APPLID (pronounced 'apple-id').
In order to verify the connection to the Mainframe it is wise to configure an LU to be used as a 3270 Terminal Session. In this section we will describe the configuration of a Dependent LU.
Now we will configure the Remote LU that will be used to communicate with the Mainframe Fileshare process.
A Mode is used to define the attributes of sessions used between a Local LU and a Remote LU.
If the default mode #INTER is not appropriate (because its settings are incompatible with the modes defined on the host system for the Remote LU, or perhaps because a larger number of sessions is required) then a new mode can be defined.
CCIAPPC uses a single APPC session for each CCI session between the client and the server (e.g. between the MFA client and Fileshare running on a mainframe). When CCIAPPC establishes a connection between the client and server the attributes of the Mode determine, amongst other things, the number of CCI sessions available between the Local LU and the Remote LU (APPLID in VTAM). Hence the Mode determines how many client sessions can be established using the same Local LU - Remote LU pairing.
The Session Limit and the Minimum Contention Winners values together determine how many sessions can be established by the Local LU (see below).
For example: if 10 client sessions are required, all using the same Local LU then the Mode session attributes might be:
Session Limit = 20 Minimum Contention Winners = 15
Alternatively the same number of client sessions could be attained by using multiple Local LUs with the client sessions divided between these LUs.
IMPORTANT NOTE: When a connection is established between a Local LU and a Remote LU the Mode characteristics are negotiated. This means that it is possible that the partner system (e.g. mainframe) will reduce the session limits to values which it can support. This may mean that fewer client sessions than expected will be supported. Hence it is important that the Mode characteristics, as defined for both the Local and Remote LUs, are compatible.
It is very important that the CCIAPPC module be able to determine the Local LU to use for communication with the Host application. You may have configured everything else correctly and all of your other APPC applications may work, but if you miss this final step you will fail to establish a CCI session with the host application. If the CCI-INITCLIENT call returns CCI error 9 and CCI_GETERROR returns the message "Transport failure, the client could not make a connection" it is likely that you have failed to complete this final step. When CCIAPPC attempts to allocate an LU 6.2 session with the remote system it must specify the Remote LU name which it requires a session with. This is the Remote LU name specified in the CCI Servername parameter (e.g. the /S parameter in FHREDIR.CFG). However, APPC needs to know the Local LU name as well as the Remote LU name when attempting to establish a session between the LUs. To enable APPC to retrieve the Local LU name to use when attempting to allocate APPC sessions set the Use As Default LU option in the Advanced window of the Configure Local LU's dialog box for the Local LU. This must be done prior to starting the CCIAPPC client.
Once the settings described above have been made the configuration must be saved before starting the RUMBA Engine. In the File menu select Save and then Exit the RUMBA APPC Configuration program.
Before Rumba can be used with CCIAPPC the system path must be updated so that the required Rumba run-time DLLs can be found by CCIAPPC. CCIAPPC on 32 Bit Windows uses the WCPIC32.DLL from the Rumba product to provide CPI-C APPC support.
Use one of the following methods to update the path:
This takes affect immediately, applications subsequently started will have the correct path setting.
Restart Windows 95 to adopt the new path setting.
The new path will now be set when MFENV is used to set the environment for Cobol.
In order to activate the configuration follow the steps outlined below.
Refer to the RUMBA Event Logger and Using the RUMBA Trace Console sections of the RUMBA Administrative Tools help topic in the RUMBA Help Desk. These sections will explain how to monitor error events and trace APPC within RUMBA.
Fileshare Error Reporting - Fileshare clients log messages returned from CCI in both the fhredir.msg and fhneterr.log files in the current directory. For Example: an entry from fhredir.cfg, "CCI: 970116 15183855 0009 07 CCIAPPC failed to allocate an APPC session, ensure that Local LU is defined". Column 2 and 3 gives the date and time stamp of the error. Column 4 (in this case 0009) gives the CCI error code Column 6 gives the CCI error message returned by CCI-GETERROR
Copyright © 2000 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.
|Microsoft SNA Server v2.11
|Support for Attachmate EXTRA! Personal Client