(1) .-DYNADJCP--=--YES-------. >>-+------------------------+---------------------------------->< '-DYNADJCP--=--+-YES-+---' '-NO--'
Notes:
- DYNADJCP is meaningful only if the NODETYPE start option is also used.
Specifies whether adjacent control point (ADJCP) minor nodes are allowed to be created dynamically and placed in ISTADJCP. The ADJCP minor node provides control and management of connections between this node and an adjacent APPN type 2.1 node. This option can be overridden at the connection level (that is, on a link station).
By specifying this option as NO and overriding its value
on specific link stations, you can limit connections to a specific
set of CPs over some link stations, and allow connections to any CP
over other link stations.
- DYNADJCP=NO
- ADJCP minor nodes are not created dynamically. When a connection is established, the adjacent control point minor node must be defined and active or the connection is discontinued.
- DYNADJCP=YES
- ADJCP minor nodes are created as needed. Because some VTAM® LEN implementations do not have an ADJCP major node, this option defaults to YES to provide compatibility for all type 2.1 connections.
Restrictions:
- If an HPR pipe is to be brought up, the DYNADJCP option is ignored.
- When you define a PU with CPNAME, the ADJACENT CP will automatically be built and stored in ISTADJCP when the PU is activated, even when still in CONCT status. When the first link to the CPNAME is activated, the DYNADJCP=NO option does not take effect for pipes towards that CPNAME. With DYNADJCP=NO, the links from unknown CPNAMEs require a VBUILD TYPE=ADJCP major node that defines every CPNAME you want to link with.