You
must define a remote node (and the partner LUs on the node) in the
following situations:
If the local node is a LEN node, you
must define all of the remote nodes and any partner LUs on the remote
node with which it communicates using APPC. A LEN node is not able
to dynamically locate partner LUs; the remote node definition enables
it to do so.
If the local node is not part of an APPN network
(for example, if you have two end nodes directly connected, with
no network node server), LUs cannot be located dynamically. In this
case, you must configure each partner LU.
If the remote node is a LEN node and the local node
is a network node that acts as the LEN node's network node server,
you must define the LEN node (and its partner LUs) as a remote node
on the network node server. This definition enables nodes in the
rest of the APPN network to locate LUs on the LEN node.
If the remote node is in a different APPN network,
you must define the remote node because it cannot be dynamically
located.
If you need to define the remote node and did not do so when
you were defined the link station, you must do so before you can
use APPC communications over the link.
When you add a remote node definition, a partner LU with the
same name as the remote node is automatically added; this is the
control point LU for the remote node. If your application uses this
partner LU, you do not need to add another partner LU, although
you may want to add an LU alias for the partner LU. To add an alias,
double click on the partner LU and enter the alias in the Partner
LU Configuration dialog.
If both the local node and the remote node are end nodes or
network nodes and are part of an APPN network, partner LUs are located
dynamically when needed. In this case, do not define the remote
node where the LUs are located, because defining the node can cause
the protocols in APPN that dynamically locate LUs to malfunction.
To prevent this malfunction, SNAplus2 does not permit you
to define a remote node with which it has CP-CP sessions active
(or with which it has had CP-CP sessions in the past). Additionally,
if you have previously defined a remote node and SNAplus2 establishes
CP-CP sessions with it, the entry is temporarily converted into
a dynamic one. You should correct the fault by deleting the remote
node definition when the node is inactive.
To configure a remote node, use one of the following methods:
- Motif
administration program
Select APPC and New remote node from the Services menu on
the Node window.
- Command-line administration program
To define a remote node, issue the following command:
define_directory_entry
To define a partner LU, issue the following command:
define_partner_lu
Remote Node Configuration
Parameters |
 |
The following parameter is required for remote node configuration:
- Node's SNA network name
The fully qualified
CP name of the remote node. The value entered on this dialog must
match the CP name configured at that remote node.
Additional Configuration |
|
After performing the
remote node configuration, continue with the following configuration
tasks:
Printable version
