Across the Boards
Communications Device Drivers
Section 5 - General Configuration and Usage Information
Page 211
cfSOFTWARE Confidential,
2000
5.16 LU6.2 Configuration (continued)
CPI-C Side Information Definitions
Side information is used to provide default settings for an application program, although in many cases the
application allows the settings configured in side-info to be overridden. A minimal side-info record is required.
Side-info usually contains a default mode name, a default partner LU name and a default transaction program
name. Side-info is only used by CPI-C drivers (and not by APPC drivers).
Transaction Program Definitions
For use with host-initiated transactions (e.g., pcMAINFRAME host-init or CFXINIT), transaction programs
need to be defined. In general the transaction program name (TPN) is defined along with the command line
used to start the application program on the PC. The TPN will be referenced by the host application, and the
command line should be formatted as appropriate for the PC application.
NOTE
: For PC-initiated transactions, it is not necessary to define TPNs on the PC.
Configuring a Shared PU for the Emulator (Gateway)
If the PC is accessing the mainframe via a gateway, the host will have it’s (SNA) sessions with the gateway, and
not with the individual PC. The gateway will redistribute the SNA sessions over the LAN to the individual PCs.
In the gateway scenario, the host definitions will usually be the same as described in the previous section
(although they will refer to the gateway, and not to the individual PCs), and the session limits will often need to
be larger, since there will likely be more active sessions on the gateway than there would be on an individual
PC.
In many cases, there will be existing LU6.2/APPC definitions that provide for sessions between the SNA Server,
VTAM and the target CICS’s. It would generally be desirable to use the preexisting definitions.
To set up a new PU definition for the gateway, follow the procedures in the prior section using the gateway as
the target instead of an individual PC, then proceed to the “Gateway” section below.
To make use of an existing set of definitions, the following needs to be done:
VTAM
The required PU definitions should be in place and should not require any changes.
CICS
Ensure that the VTAM, CICS Startup and CONNECTION and SESSION definitions are in place (as defined in
the prior section), if not follow the procedures in the prior section. Ensure that those SESSIONs are authorized
to invoke the required transactions. Ensure that the session limits are adequate to handle both the existing traffic
and the new traffic.
pcMAINFRAME Host-Init (CFXINIT)
The procedures in the previous section should be followed.
Gateway
The PC that will make use of the LU6.2 session will need to be added to the gateway’s access list, and the
correct default local LU defined. The session limits on the modes to be used should be reviewed. The client PC
will then need to be configured to access the gateway.
(24 strony)
(26 strony)
(16 strony)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji