| statement: | ADJCP |
| dependencies: | APPN only |
The network identifier of the adjacent CP.
If NETID is specified, then the network identifier is validated when a connection is established to the adjacent node. If the NETIDs do not match, the session setup is based on the value of the DYNADJCP start option. If DYNADJCP=YES, the session is established dynamically; if DYNADJCP=NO, the session is not established.
If NETID is not specified, the network identifier of the adjacent node is acknowledged at connection establishment. When an ADJCP is defined without a NETID, any NETID with that ADJCP name is considered to be predefined, so the session is always established dynamically, even if DYNADJCP=NO is specified in the start options.
Tip: For ADJCP minor nodes that specify the NETID operand, you can dynamically change the ALIASRCH, AUTHNETS, and RTPONLY operands without stopping and restarting CP-CP sessions to these adjacent CPs. If you do not specify the NETID operand on the ADJCP minor node, then you must stop all the links (at the same time) to this adjacent node and restart them for the updated definitions to be used.