YES, the IST664I indicated REAL DLU and
the NETID is different from this NETID:
An ADJCLUST table must be coded for that NETID
in order for VTAM to send a
search to that NETID.
Issue a D NET,ADJCLUST,NETID=NETID_from_ist664I_for_dlu
If a table is not found with this display then code an ADJCLUST for
that NETID
on this host or code BNDYN=FULL. BNDYN=LIMITED may work for this host.
See the Resource Definition Reference for explanations of these options
to see which
is best in this case.
For these options VTAM will build a limited ADJCLUST table but may or
may not
add the needed Border Node to this table for resources in other NETIDs.
See the
rules in the Resource Definition Reference under BNDYN=LIMITED .It is
still
recommended that you code a NETID specific ADJCLUST tables for
resources in
other NETIDs if you are not using BNDYN=FULL.
Issue a D NET,ADJCLUST,NETID=NETID_from_ist664I_for_dlu
If a table is not found with this display then code an ADJCLUST for
that NETID
on this host or code BNDYN=FULL.
For these options VTAM should dynamically add all active Border Nodes
to the
ADJCLUST table. No coding of tables are required.
An active Border node is an adjacent Border Node that actually has a
connection to
another NETID.