
2-10 TN3270 Design and Implementation Guide
solution to this problem is to use DLUR PUs or direct PUs with INCLUD0E so that VTAM passes all LU names
(static and dynamic LUs) to the CIP/CPA. As an alternative, you can code LU-SEED in the CIP to match VTAM’s
static LU names, if possible.
INCLUD0E
INCLUD0E is a VTAM parameter that can be used with direct PUs to instruct the XCA to allow the LU name
to be included in the ACTLU. If the TN3270 Server receives the LU name as part of the ACTLU, it uses this LU
name and does not relearn the name from the Bind.
The INCLUD0E is available and supported in VTAM Version 4.4. If you use INCLUD0E, you must also apply
the PTFs for the following authorized program analysis reports (APARs):
• APAR OW25501
• APAR OW31436
• APAR OW31805
LU Nailing
DDDLU and LU pooling are increasing in popularity and can be used for most LU needs. The exception,
however, isif a clientmust usea specificLU name becauseof applicationrequirements. For example,Information
ManagementSystem (IMS) applicationsuse asecurity mechanism to control accessthat isbased on theLU name.
These clients are often groupssuch as personnel departmentsor office branches. Forthese clients therequirement
is to lock their LU to an IP address. There are two methods of locking an LU to an IP address. The first method
is forthe client to usethe TN3270E function, which allowsthe client to specifythe LU name. Thesecond method
is to use the client LU nailing feature of the Cisco IOS software TN3270 Server feature.
LU address mapping allows a client IP address to be mapped, or “nailed,” to one or more LU local addresses on
one or more PUs. You can then control the relationship between the TN3270 client and the LU. Clients from
traditional TN3270 (non-TN3270E) devices can connect to specific LUs, which overcomes a limitation of
TN3270 devices that cannot specify a CONNECT LU. LU nailing is also useful for TN3270E clients because it
allows you to perform the configuration of the client at the router, providing central control, rather than at the
client.
The “model matching” feature of the TN3270 Server is designed for efficient use of dynamic LUs. Each client
specifies a terminal model type at connection. When a non-nailed client connects and does not request a specific
LU, the LU allocation algorithm attempts to allocate an LU that operated with that terminal model the last time
it was used. If no such model is available, the next choice is an LU that has not been used since the PU was last
activated. Failing that, any available LU is used. For dynamic LUs, however, there is a short delay in connecting
the session.
Where a clientor set of clients is nailed to more than one LU, the same logic applies. If the configured LU nailing
maps a screen client to a set of LUs, the LU nailing algorithm attempts to match the client to a previously used
LU that was most recently used with the same terminal model type as requested by the client for this connection.
Ifa match isfound, that LUis used. Ifa match isnot found, any LU in theset that isnot currently inuse is chosen.
If there is no available LU in the set, the connection is rejected.
Comentarios a estos manuales