HP (Hewlett-Packard) HP-UX SNAplus2 Network Card User Manual


 
162 Chapter 5
Defining Connectivity Components
Defining Link Stations
slightly, so if you do know the type it is better to specify
it. This also helps to ensure network configuration
consistency.
You cannot choose Discover if the link station is
activated on demand.
If the local node is a LEN node, this field does not
apply.
Parameters for Dependent LU Traffic
Configuring a link station for dependent LU traffic automatically creates
an appropriate PU with the same name as the link station.
You need the following information to configure a link station for use by
dependent LUs (LUs of type 0–3 for 3270, RJE, or LUA applications):
Local node ID
A value to identify the local node in the SNA network.
You can usually use the same node ID (the default
value) for all the links on the same node. However, if
you need more than 255 dependent LUs to access a
specific host, you must configure multiple link stations
to the host, each with up to 255 dependent LUs, and
each with a different local node ID.
To ensure that the remote node is configured to
recognize the local node ID, contact your SNA network
planner.
In a VTAM configuration, the first three digits should
match the IDBLK parameter in the PU definition, and
the last five should match the IDNUM parameter.
On an AS/400 system, the node ID is configured in the
EXCHID parameter.
Remote node ID
The node ID for the remote link station (optional; only
applicable if you need to restrict access to this link
station). If you specify the remote node ID, the link is
activated only if the node ID of the remote node
matches the value specified in this definition. This can
be useful if you have several link stations configured on
a switched port, because it enables the link stations to
be distinguished when they are activated by the remote
nodes. Link stations can also be distinguished by the