Filter
Top Products
Chapter 7 183
Configuring APPC Communication
Defining Partner LUs
Defining Partner LUs
If both the local node and the remote node are end nodes or network
nodes and your application uses an LU name to refer to the partner LU,
there is no need to define the partner LU, because it can be dynamically
located using APPN.
If both nodes are end nodes or network nodes, but your application uses
an LU alias to refer to its partner LU, you should add a partner LU alias
definition.
If either the local node or the remote node is a LEN node, you must
define the partner LU as a child of the remote node, because a LEN node
cannot take part in dynamic location of LUs. If your application uses the
control point LU of the remote node as its partner LU, the control point
LU was defined automatically when you defined the remote node.
You can use wildcards to configure multiple partner LUs that are all
located on the same remote node and whose names start with the same
characters. Using wildcards means that you do not need to configure
each partner LU individually.
To configure a partner LU, use one of the following methods:
Motif administration program
You can use the Motif administration program to add a
partner LU alias, add a definition of a partner LU on a
specific remote node, or define multiple partner LUs
using wildcards. Select APPC, New partner LUs, and
one of the following from the Services menu on the
Node window.
• Partner LU alias
• Partner LU on remote node
• Wildcard partner LU on remote node
Command-line administration program
To define a partner LU, issue the following command:
define_partner_lu
To define a LEN node as a partner LU, issue the
following commands:
define_adjacent_len_node
define_directory_entry