HP-UX SNAplus2 R7 Administration Guide

Configuring APPC Communication
Defining Partner LUs
Supports parallel sessions
Whether the partner LU can support more than one session at a time. In most cases, the partner LU supports
many sessions at one time, but some LEN nodes do not support parallel sessions.
This field applies when you define partner LU on a specific remote node or when you define a partner LU
alias.
Location
The fully qualified CP name of the node on which the partner LU resides, or of a node that can provide
access to the partner LU. If you supply the name of a remote node that has not yet been de
fined, you need
to define it if you cannot discover the node dynamically.
This field applies only if you define a partner LU on a specific remote node.
7.3.2 Defining Link Station Routing for a Partner LU
You can use link station routing to identify the location of a partner LU by the link station that is used to reach it.
Notes
1. Link station routing is not required in an APPN network, where resources can be located
dynamically. You are not recommended to use link station routing in an APPN network
because it bypasses the normal APPN routing mechanisms.
2. You cannot use link station routing with an Enterprise Extender (HPR/IP) link station.
This is because all traffic on this link type must flow over an RTP connection, which
is not fixed to a particular link station and can switch to a different path.
To configure link station routing for a partner LU, use one of the following methods:
Motif administration program
Select
APPC, New partner LUs
, and
Partner LU on link station
from the Services
menu on the Node window.
Command-line administration program
Issue the following command:
define_ls_routing
Link Station Routing Parameters
The following parameters are required for link station routing configuration:
LU name
The name of the local LU that controls the link station (if the partner LU is to be located through a specific
link station).
LS name
The name of the link station.
Partner LU name
Either the fully qualified LU name of the partner LU or a wildcard name:
• A fully qualified LU name consists of two strings, each of 1–8 characters.
This name must match the name that is configured at the remote node for this LU. If you do not know
what that name is, consult your SNA network planner.
• A wildcard partner LU name matches the fully qualified LU names of multiple partner LUs. The wildcard
partner LU name consists of two strings, each of 1–8 characters:
109