Identifying the communication controller

The communication controller into which the NCP is loaded is determined by the adjacent link stations specified for automatic activation with the NCP. These link stations in adjacent nodes locate the communication controller in the network.

If no link station is available, the load fails. In this case, specify RENAME=adjacent link station name on the command line.

Within its domain, VTAM® ensures that no more than one load or dump operation is attempted at one time for a given NCP through any adjacent link stations that might be available.

If you are activating an NCP in a communication controller that already contains a different NCP, you should first deactivate the current NCP and any active link stations in adjacent subarea nodes that are connected to that NCP. You can then enter the command to activate the new NCP, which causes the communication controller to be reloaded as described in Reloading an NCP (if LOAD=U is specified or assumed). If adjacent link stations are not deactivated, the activation of the new NCP might fail because one of the following occurred:

There are no link stations available. (VTAM does not automatically break the existing connections with the old NCP.)
The names of the old and new NCPs are the same, but their subarea addresses are different.
The subarea addresses of the old and new NCPs are the same, but their names are different.