Across the Boards
Communications Device Drivers
Section 5 - General Configuration and Usage Information
Page 210
cfSOFTWARE Confidential,
2000
5.16 LU6.2 Configuration (continued)
Emulator Configuration
The emulator or gateway must be configured with definitions that match the VTAM and CICS definitions. The
exact way this is accomplished is dependent on the emulator or gateway in question, so only the general points
are listed here. See the device specific sections for more information about configuring emulators for LU6.2
support.
Node Information
The emulator will require the specification of some information related to the entire APPN node. These will
include the NETID, IDBLK, IDNUM and the CPNAME settings. Using the above configuration samples, the
following settings should be made:
NETID=USCFSW01
CPNAME=PC001001
IDBLK=05D
IDNUM=01001
In addition, various link specific setting will have to be made (for example, the MAC address of the host, if a
LAN connection is being used).
Partner LU Information
The mainframe LU’s (APPLs) that the PC application will start connections with will need to be defined. For
example, if a CICS region with an APPLID of CICSPROD is to be accessed, a partner LU definition defining
USCFSW00.CICSPROD should be added. In most implementations this definition will be given an alias name,
which is what will actually be used on the PC to reference the host LU. For simplicity, consider setting the alias
name to the LU name.
Ensure that the LU definition is enabled for parallel sessions (usually the default).
Mode Names
The mode names that will be used must be defined. Typically modes #INTER or #BATCH are used. In
addition the mode SNASVCMG is required. In most cases standard definitions for these modes are provided by
default.
These modes may be changed to increase or decrease session limits and to alter the pacing parameters for the
sessions established using that mode.
Local LU Definitions - Stand-alone PCs
In addition to the local LU defined via the CP name, it is possible to define additional LUs. These alternate LUs
may be used for incoming sessions, but then will require corresponding CICS definitions. In general use of
alternate local LUs on a stand-alone PC should be avoided.
Local LU Definitions - Gateways
In addition to the local LU defined via the CP name, it is possible to define additional LUs. Gateways usually
provide some function for associating a given LU definition with a particular user accessing that gateway. The
actual LUs assigned to the user running the application is the one that will need to be defined to CICS.
(24 Seiten)
(26 Seiten)
(16 Seiten)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern