Dynamic change of operands for network control program major node

You can dynamically change the following NCP major node operands by editing the VTAMLST data set and then issuing the VARY ACT,UPDATE=ALL command. You can specify the new operand value on a higher-level definition statement for sifting, if applicable.

PU	LU
CAPACITY COMRATE COSTBYTE COSTIME CPCP DISCNT DLCI DYNADJCP DYNLU DYNWIND HPRQLIM INNPORT INTFACE IPQLIM ISTATUS LADDR LIMRES LUGROUP LUSEED MAXSESS NN PDELAY SECNET SECURITY SNETMASK T1TIMER T2TIMER TGP TOPO UPARM1 UPARM2 UPARM3 VERALSID VPACING	ASLENT ASLTAB CLRSESSQ DLOGMOD ENCR ENCRTYPE FASTPASS FEATUR2 ISTATUS LOGAPPL LOGTAB MDLENT MDLTAB MODETAB REGISTER SSCPFM TERM USSTAB VPACING

For information about the following NCP operands, from the preceding list, see NCP, SSP, and EP Resource Definition Reference.

COMRATE
DLCI. DLCI has a VTAM® restriction. See DLCI for details.
DYNWIND
HPRQLIM
INTFACE
IPQLIM
LADDR
SNETMASK
T1TIMER
T2TIMER

To dynamically change the operand, the resource to which it applies must be inactive. For instance, an operand on an LU definition statement which receives its value from a PU definition statement can be dynamically changed only when the LU is inactive; the PU can remain active.

You can dynamically change the operands associated with tables (ASLTAB, LOGTAB, MDLTAB, MODETAB, and USSTAB) at any time without deactivating resources.

VTAM cannot recognize dynamically changed ADDRs or LOCADDRs on the first activation of an NCP, even when VARY ACT,UPDATE=ALL is used. (Warm starts are considered initial activations.)

The resource resolution table (RRT) from the NCP generation does not contain ADDR or LOCADDR information, so VTAM cannot recognize that the ADDR and LOCADDR values have been changed on the first activation of the NCP. However, on changes to ADDR and LOCADDR after the first activation, VTAM can compare the value in the definition statements to the value previously coded and recognize the change.

See z/OS Communications Server: SNA Network Implementation Guide and z/OS Communications Server: SNA Operation for more information about the VARY ACT,UPDATE=ALL command.

Note: For an NCP major node, you cannot add APPN capability or SDDLU support to a PU with the dynamic change function. If a PU has not been coded as APPN-capable, you cannot add the APPN operands to it. Likewise, if you have not coded LUGROUP (which allows SDDLU support) on a PU definition statement, you cannot add it with dynamic change.