
154
Chapter 5
Defining Connectivity Components
Defining Link Stations
Defining Link Stations
To communicate with other nodes in an SNA network, you must
configure the characteristics of a link station (LS) to an adjacent node in
the SNA network. Before you can define a link station, you must define a
port for the adapter (and link protocol) you are using. Most of the
information needed to configure a link station is the same, whatever
protocol is being used.
A link station represents the logical path through the SNA network
between the SNAplus2 local node and a remote computer. The remote
computer can be any of the following:
• A host computer, on which SNAplus2 accesses a host program using
3270, RJE, or LUA communications (or uses APPC or CPI-C for
program-to-program communications)
• A peer computer, with SNAplus2 and the remote computer
communicating as equal partners (the typical arrangement in an
APPN network)
• A downstream computer that uses the SNAplus2 PU concentration
feature or DLUR feature in order to access a host
A link station is associated with a specific port; you can define one or
more link stations on each port.
Each link station that supports dependent traffic has an associated PU
(physical unit). Because PUs are associated with link stations, SNAplus2
does not treat them as separate resources; they are configured as part of
link station configuration, and are started and stopped as part of
starting and stopping link stations. Link stations are shown in the
connectivity section of the Node window; PUs are not shown in any
window.
NOTE
In most circumstances, you need to add a link station to the port.
However, if you want to use a dynamically created link station for APPC
traffic only, for situations in which the link is always activated from the
remote node, you do not need to explicitly configure one.
If a remote node attempts to connect to the local node, but no link station
is defined that matches the address specified on the incoming call,
SNAplus2 can define one implicitly if a suitable port has been defined on
Summary of Contents for HP-UX SNAplus2
Page 4: ...4 ...
Page 14: ...14 Contents ...
Page 22: ...22 ...
Page 23: ...23 1 SNA Terms and Concepts ...
Page 65: ...65 2 Introduction to SNAplus2 ...
Page 107: ...107 3 Administering SNAplus2 ...
Page 132: ...132 Chapter3 Administering SNAplus2 Using the Command Line Administration Program ...
Page 133: ...133 4 Basic Configuration Tasks ...
Page 142: ...142 Chapter4 Basic Configuration Tasks Configuring Logging ...
Page 143: ...143 5 Defining Connectivity Components ...
Page 167: ...167 6 Configuring Dependent LUs ...
Page 174: ...174 Chapter6 Configuring Dependent LUs Defining LU Pools ...
Page 175: ...175 7 Configuring APPC Communication ...
Page 208: ...208 Chapter7 Configuring APPC Communication Configuring APPC Security ...
Page 209: ...209 8 Configuring User Applications ...
Page 222: ...222 Chapter8 Configuring User Applications Configuring RJE Workstations ...
Page 223: ...223 9 Configuring Passthrough Services ...
Page 235: ...235 10 Managing SNAplus2 from NetView ...
Page 248: ...248 Chapter10 Managing SNAplus2 from NetView Using UCF ...
Page 249: ...249 11 Managing SNAplus2 Clients ...
Page 300: ...300 Chapter11 Managing SNAplus2 Clients Managing HP UX Clients ...
Page 301: ...301 A Configuration Planning Worksheets ...
Page 337: ...337 B APPN Network Management Using the Simple Network Management Protocol ...
Page 343: ...343 C Configuring an Invokable TP Using snaptpinstall ...
Page 353: ...353 D Using SNAplus2 in a High Availability Environment ...