Cisco 11.0 BT Manual de usuario descargar pdf (Pagina 11)

TN3270 Server Implementation 2-11

The client LU nailing feature associates particular LU names to particular client IP addresses or IP subnets. The

LU nailing is used to:

• Control (from a central location) the clients that can connect to certain LUs.

• Allow non-TN3270E clients to access a speciﬁc LU or pool of LUs.

• Provide guaranteed ownership for printers that need a predeﬁned name.

• Provide guaranteed ownership for applications that use terminal based security.

• Control which group of users, based on IP address, is associated with a certain pool of LUs.

The CLIENT command nails client IP addresses to speciﬁc LUs. The parameter is conﬁgured using the “client

ip” or “client printer” statement under a TN3270 Server PU. Each client statement is conﬁgured on a per PU

basic. A client statement can specify one IP address or a group of IP addresses within a subnet. A speciﬁc IP

address can be included in more than one client statement.

DHCP with Client Nailing

Some clients may require the use of client LU nailing but belong to a Dynamic Host Conﬁguration Protocol

(DHCP) group. Therefore, their speciﬁc IP address is not going to vary. The client LU nailing feature works with

DHCP by using the subnet parameter. This means that a DHCP group that is part of a particular subnet can be

speciﬁed to access a single LU or a group of LUs based upon the subnet address.

TN3270E and Statically Deﬁned LUs with Client Nailing

Consider the situation where a TN3270E client requests an LU that is statically deﬁned in the PU. If neither the

LU nor the client are subjects of nailing statements, the client will get the LU that it requested. If the client is

nailed and the requested LU is available and in the set to which the client is nailed, the client will get the LU that

is requested. Otherwise the request is refused.

LU Assignment and Naming Summary

Table 2-1 discusses the factors that impact how an LU name is assigned and explains the result.

Table 2-1 LU Naming Summary

Factors How the Name Is Assigned

Static LU with DLUR PU The LU-SEED parameter on the channel-attached router cannot be

conﬁgured under DLUR. Therefore, the LU names must be hardcoded in

VTAM. The TN3270 Server learns the LU names from VTAM.

Static LU on direct PU with

INCLUD0E

The LU names are hardcoded in VTAM. The TN3270 Server learns the LU

names from VTAM.

Static LU on direct PUwithout

INCLUD0E

If you use the LU-SEED parameter on the channel-attached router, the LU

names on the router are created according to the LU-SEED parameter. If you

want the LU names to be identical on the router and in VTAM, you must

create the VTAM LU names according to the naming convention established

by the router’s LU-SEED parameter.

If you do not use the LU-SEED parameter on the channel-attached router, the

LU names on the router default to the ﬁrst 6 characters of the conﬁgured PU

followed by the 2-byte hexadecimal number of the respective LOCADDR of

this LU. If you want the LU names to be identical on the router and in

VTAM, you must create the VTAM LU names according to the naming

convention described above.

1 2 ... 6 7 8 9 10 11 12 13 14 15 16 ... 29 30

Comentarios a estos manuales

Sin comentarios

Cisco 11.0 BT Manual de usuario Pagina 11

Comentarios a estos manuales

Relacionado con productos y manuales para Servidores Cisco 11.0 BT