Filter
Top Products
A pool is a logical group of LUs. These LUs can be from different PUs or the same
PU, different Host or same Host, etc. When a client specifies a specific pool name,
any LU from the pool may be selected.
There is always at least one implicit workstation pool. This pool is referred to as the
global default pool. The name of this Pool is defined via the TN3270E config> set
command. LUs must be added to this pool via the TN3270E config> add lu or
TN3270E config> add implicit-pool command.
Multiple TN3270E Ports
This enhancement allows users to define multiple TCP ports for the TN3270E
Server to ″listen″ on. This support allows clients to specify the SNA resource they
want using a port number.
When the ports are added, the user can define an LU pool to be associated with
that port number. Clients that connect to this port and do not specify an LU name
will be assigned an LU from this Pool.
TN3270E Server ports can also be defined for a particular type of TN3270 Server
(Base or TN3270E) support. Since some base TN3270 clients do not negotiate
properly with TN3270E Servers, a port can now be defined for these clients to
connect to.
There is always at least one port defined for use by the server. This port is
specified via the TN3270E config> set command. The Pool associated with this port
is always the global default pool.
TN3270E Server Client IP Address to LU Name Mapping
The TN3270E Server Client IP Address to LU Name Mapping function provides a
mechanism for administrators to control client access to the TN3270E Server’s
resources (ie LUs).
Mapping enhances central administration by allowing the administrator to configure
which SNA resources(LUs/Pool) client IP address/subnets will map to and use
without modifying client configurations.
Mapping removes the burden on the client of having to connect to a specific port or
request a specific LU/Pool on their connect request. These decisions are
maintained at the server.
When a client connects in while mapping is enabled, the Server will begin ANDing
the client’s IP address with the subnet mask of each map definition. The longest
match between the incoming Client IP address and the map definition determines
which map definition is tried first. If all eligible resources in the map definition are in
use, the map definitions are again searched for the next most specific match.
If a map definition contains a full subnet mask (255.255.255.255), indicating that the
entry is for a specific client, and a specific LU/Pool is not requested by the client,
any LU/Pool in the map definition that matches the connection type may be tried.
If a map definition does not contain a full subnet mask and a specific LU/Pool is not
requested, only Pool entries in the map definition will be tried. You must have the
subnet map to a Pool. For individual workstation LUs with associated printers, only
the workstation LU is required to be in the map definition.
APPN
22
MRS V3.2 Protocol Config Ref Vol 2
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|