HP-UX SNAplus2 R7 Administration Guide

Defining Connectivity Components
Defining Link Stations
The type of link to the remote node that is accessed through this link station (only applicable if the local
node is a branch network node).
If the remote node is a network node within the main APPN backbone, choose
Uplink (to backbone).
If the remote node is an end node within the branch, choose Downlink (within branch).
If the remote node is configured to be a network node, the branch link type is automatically set to Uplink
(to backbone) and you cannot change it.
Parameters for Dependent LU Traffic
These parameters do not apply to an Enterprise Extender (HPR/IP) link, because this link type supports only
independent 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 CP name of the remote node, but for remote
nodes that do not send their CP name when activating a link, the remote node ID must be used instead.
If you do not specify the remote node ID, the node ID of the remote node is not checked when the link is
activated.
Remote node role
The role of the remote (adjacent) node:
Host
The link station supports dependent LUs (such as 3270 LUs) that are used for sessions with a host
computer (the most common case). If the link is to a node that provides host connectivity using PU
concentration or DLUR, the adjacent node role should still be set to Host, even though the link is not
directly to a host computer.
Downstream (PU concentration)
The link station is to a downstream node that will communicate with a host using the PU concentration
capabilities of the local node (to the host, the LUs on the downstream node appear to reside on the
local node).
Downstream (DLUR)
96