Filter
Top Products
After the temporary list is built, it is always ordered so that configured next-hop CPs
are first followed by CPs associated with similarly named known resources.
Additional reordering may be performed. Once all the reordering is complete, the
extended border node starts searching for the target resource one CP after another.
Note that once the extended border node actually locates a resource it will
remember the next hop CP and always use that next hop CP for that particular
resource, ignoring the routing lists. Entries from this table of located resources can
be quite long lived. They are discarded if the table reaches its maximum size, a
later search to that CP fails to locate the resource, or if search from that LU comes
from a different CP.
The list dynamics parameter is set to one of the following values. It is possible to
respecify this value for individual routing lists when, and if, you configure individual
routing lists.
None The LU name of the destination resource is compared to the LU name(s)
configured in the routing list(s). The routing list with the best LU name
match is selected, and the next hop CP name(s) from that configured list
are placed in the dynamically built list. This is the only source of possible
next hop CP names when list dynamics is set to none.
Note that if an LU name does not appear in a routing list the LU will not be
reachable by the extended border node when this list dynamics parameter
is set to none.
Limited
This augments the list of next hop CP names obtained from the best match
configured routing list with CP names obtained from the extended border
node’s knowledge of existing resources and topology. These additional CP
names are obtained by:
v Adding all native extended border nodes
v Adding all non-native, adjacent extended border nodes and network
nodes with NETIDs that match the NETID of the destination resource.
v Examining the table of resources already known to the extended border
node due to the receipt of a find or found GDS variable. These resources
are cached in the Directory Services database. For any entries where the
Netid of the cached LU is the same as the destination of the current
search, add the NNs of the cached LU to the list of next-hop CPs.
None of these dynamically obtained next-hop CP names are permanently
saved with the configuration data. The list is recreated whenever a
resource needs to be located.
Full This functions the same as
limited
, except the restriction on matching
NETIDs is removed when adding all non-native, adjacent extended border
nodes and network nodes.
If
List optimization
is enabled, the reordering process described in 31 is repeated a
second time and the CP names obtained from configured data are also eligible to
be reordered.
Add port
If extended border node is enabled, two additional prompts are presented when you
invoke the add port menu item. Both of these new items establish the default for
analogous parameters at the link level. The values of these parameters at the link
level determine link station behavior.
APPN
32
MRS V3.2 Protocol Config Ref Vol 2