 |
» |
|
|
|
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 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
Partner LU Configuration
Parameters | |
The following parameters are required for partner LU configuration: - Partner LU name
The fully qualified LU name of the
partner LU. 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. This field applies when you define partner LU on a specific
remote node or when you define a partner LU alias. - Wildcard partner LU name
A name that matches the fully
qualified LU names of multiple partner LUs. (This field applies
only if you define partner LUs using wildcards.) The wildcard partner
LU name consists of two strings, each of 1-8 characters: The first string can be a complete
SNA network name that matches the first part of the fully qualified
partner LU names exactly, or a wildcard prefix that matches the
beginning of the network name for the partner LUs. If you supply
a wildcard prefix as the value for the first string, leave the second
string blank. For example, a wildcard entry of A
would match all LUs in the SNA networks named A, ANT, or APPN (but
not BUFFALO or ZEBRA). If you supply a complete SNA network name for the
first string, you can also enter a value for the second string.
(You cannot specify the second string without supplying a valid
SNA network name for the first string.) The second string is treated
as a wildcard prefix, which must match the start of the second part
of the fully qualified partner LU names. For example, a wildcard
entry of A.F would match
partner LUs names A.FRED or A.FREDDY (but not APPN.FRED or A.B).
If you leave both strings blank, the wildcard partner LU definition
matches any partner LU name. - Alias
A
locally displayable alias for the partner LU. You do not have to
specify an LU alias if there is no local application that refers
to the partner LU using an LU alias. This field applies when you define partner LU on a specific
remote node or when you define a partner LU alias. - Uninterpreted Name
The uninterpreted name used by dependent
local LUs when requesting the host to start an LU-LU session between
the partner LU and the local LU. This name enables the partner LU
name configured locally (and used by applications) to differ from
the partner LU name configured on the host. The default uninterpreted name is the second part of the partner
LU name. This is correct in most cases. If in doubt, consult your
SNA network planner. This field applies when you define partner LU on a specific
remote node or when you define a partner LU alias. - 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 defined, 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.
Additional Configuration | |
After performing the
partner LU configuration, continue with the following configuration
tasks: |
Printable version
