Cisco 11.0 BT Manual de usuario Pagina 7

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 30
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 6
TN3270 Server Implementation 2-7
• The host issues a deactivate physical unit (DACTPU) or disconnects the link.
• The router console is instructed to deconfigure the PU.
Determining How LUs Will Be Named
There are several ways in which an LU can be named and assigned to a TN3270 client. It is important to
understand how LU naming and allocation work before designing a TN3270 Server network. The same LU can
be known to VTAM with one name and to the CIP/CPA with a different name. This can be by design, but also
can be accidental, leading to client connection problems and network management problems.
The LU name assigned within the TN3270 Server is created using one of several methods. The method depends
on the configuration of the TN3270 Server and the PU. PUs can be configured as either direct or DLUR-based.
Direct—With direct PUs, the TN3270 Server LU names do not necessarily match the LU names defined in
VTAM. To ensure that the LU name used in VTAM matches the LU name used by the TN3270 Server, ensure
that the configuration matches. With the introduction of the function INCLUD0E within the VTAM PU
definition, VTAM will pass information regarding the real LU names to the TN3270 Server. At this time, the
Network Control Program (NCP) does not support the 0E control vector. Remote TN3270 Servers will not get
the INCLUD0E information.
DLUR—With DLUR PUs, LU names on the TN3270 Server match names in VTAM. If you use DLUR PUs,
you always get the correct LUNAME information from VTAM. Therefore, you don’t need to specify an
LU-SEED on the router PUs.
In a multihost environment, hosts with DLUS/DLUR implemented require less configuration of the PUs and LUs
on the TN3270 Server.
Other factors that impact the LU naming process are:
• Whether the LU uses DDDLU
• How the LUGROUP is configured for dynamic LUs
• How the LUSEED is specified (if at all)
• Whether INCLUD0E is used
• Whether LU nailing is used
Dynamic Definition of Dependent LUs
Most of the current offerings of TN3270 server implementation use predefined pools ofLUs to support different
terminal types requested by the TN3270 clients. To simplify the management of such configurations, the Cisco
IOS software TN3270 Server feature supports a VTAM V3R4 feature, called DDDLU, which allows you to
dynamically request LUs using the terminal type provided by TN3270 clients. This feature eliminates the need
to define any LU configuration in the server to support TN3270 clients emulating a generic 3270 terminal. Only
thePUs needtobe configured.Configuration forLUsin theserveris necessaryonly forclientsthat requirespecific
LU names to be secured (such as printers) or use IP addresses for authorization or application selection.
Vista de pagina 6
1 2 3 4 5 6 7 8 9 10 11 12 ... 29 30

Comentarios a estos manuales

Sin comentarios