VARY ACT command


Activate an NCP major node:

>>-VARY-- --NET--,--ACT--,--ID--=--ncp_name--------------------->

>--+--------------------------------------+--------------------->
   '-,--DUMPSTA--=--+-------------------+-'   
                    '-link_station_name-'     

>--+------------------------------------------------------------+-->
   '-,--LOGON--=--appl_name--+--------------------------------+-'   
                             '-,--LOGMODE--=--logon_mode_name-'     

   .-,--LOAD--=--U--,--LOADFROM--=--HOST--,--DUMPLOAD--=--NO--,--SAVEMOD--=--NO-.   
>--+----------------------------------------------------------------------------+-->
   '-,--LOAD--=--+-NO-----------------------------+-----------------------------'   
                 '-+-U---+--| NCP Load Operands |-'                                 
                   '-YES-'                                                          

>--+-------------------------------------------+---------------->
   '-,--NEWPATH--=--+------------------------+-'   
                    +-dpu_name---------------+     
                    |    .-,--------.        |     
                    |    V          |    (1) |     
                    '-(----dpu_name-+--)-----'     

>--+----------------------------------------------+------------->
   '-,--RNAME--=--+-----------------------------+-'   
                  +-link_station_name-----------+     
                  |                         (2) |     
                  '-(--link_station_name--)-----'     

   .-,--SCOPE--=--COMP-----.   
>--+-----------------------+------------------------------------>
   '-,--SCOPE--=--+-ALL--+-'   
                  +-COMP-+     
                  +-ONLY-+     
                  '-U----'     

>--+-------------------------------+---------------------------->
   '-,--U--=--channel_unit_address-'   

   .-,--UPDATE--=--IMPLICIT-----.   
>--+----------------------------+------------------------------><
   '-,--UPDATE--=--+-IMPLICIT-+-'   
                   +-ADD------+     
                   '-ALL------'

Notes:

You can specify up to 3 dynamic path update member names on the NEWPATH operand.
You can specify up to 13 link station names on the RNAME operand.


LOADFROM Operand

   .-,--LOADFROM--=--HOST--,--DUMPLOAD--=--NO--,--SAVEMOD--=--NO----------------------.   
|--+----------------------------------------------------------------------------------+--|
   |                             .-,--DUMPLOAD--=--NO------.  .-,--SAVEMOD--=--NO-.   |   
   '-,--LOADFROM--=--+-EXTERNAL--+-------------------------+--+-------------------+-+-'   
                     |           '-,--DUMPLOAD--=--+-NO--+-'                        |     
                     |                             '-YES-'                          |     
                     |       .-,--DUMPLOAD--=--NO--,--SAVEMOD--=--NO--------------. |     
                     '-HOST--+----------------------------------------------------+-'     
                             |                       .-,--SAVEMOD--=--NO------.   |       
                             '-,--DUMPLOAD--=--+-NO--+------------------------+-+-'       
                                               |     '-,--SAVEMOD--=--+-NO--+-' |         
                                               |                      '-YES-'   |         
                                               '-YES--,--SAVEMOD--=--YES--------'


LOADSTA Operand

|--+--------------------------------------+---------------------|
   '-,--LOADSTA--=--+-------------------+-'   
                    '-link_station_name-'


NCP Load Operands

|--| LOADSTA Operand |--+---------------------------------+----->
                        '-,--LOADMOD--=--load_module_name-'   

>--| LOADFROM Operand |-----------------------------------------|


Activate a switched major node:

>>-VARY-- --NET--,--ACT--,--ID--=--major_node_name-------------->

   .-,--DWACT--=--NO------.   
>--+----------------------+------------------------------------->
   '-,--DWACT--=--+-NO--+-'   
                  '-YES-'     

>--+------------------------------------------------------------+-->
   '-,--LOGON--=--appl_name--+--------------------------------+-'   
                             '-,--LOGMODE--=--logon_mode_name-'     

   .-,--SCOPE--=--COMP-----.  .-,--UPDATE--=--IMPLICIT-----.   
>--+-----------------------+--+----------------------------+---><
   '-,--SCOPE--=--+-ALL--+-'  '-,--UPDATE--=--+-IMPLICIT-+-'   
                  +-COMP-+                    +-ADD------+     
                  +-ONLY-+                    '-ALL------'     
                  '-U----'


Activate the dynamic XCF local SNA major node:

>>-VARY-- --NET--,--ACT--,--ID--=--ISTLSXCF--------------------><


Activate a switched line:

>>-VARY-- --NET--,--ACT--,--ID--=--line_name-------------------->

>--+--------------------+--------------------------------------><
   '-,--ANS--=--+-OFF-+-'   
                '-ON--'


Activate a type 2.1 PU (adjacent link station) or a nonswitched line under an NCP:

>>-VARY-- --NET--,--ACT--,--ID--=--+-pu_name---+---------------->
                                   '-line_name-'   

                                                   (1)   
>--+---------------------+--+--------------------+-------------->
   '-,--CPCP--=--+-YES-+-'  '-,--HPR--=--+-NO--+-'       
                 '-NO--'                 '-YES-'         

>--+------------------------------------------------------------+-->
   '-,--LOGON--=--appl_name--+--------------------------------+-'   
                             '-,--LOGMODE--=--logon_mode_name-'     

   .-,--SCOPE--=--COMP-----.   
>--+-----------------------+------------------------------------>
   '-,--SCOPE--=--+-ALL--+-'   
                  +-COMP-+     
                  +-ONLY-+     
                  '-U----'     

                                     (2)   
>--+-------------------------------+---------------------------><
   '-,--U--=--channel_unit_address-'

Notes:

The HPR operand is valid for HPR-capable resources only.
The U operand is valid for a local SNA PU only.


Activate a dynamic XCF local SNA PU:

>>-VARY-- --NET--,--ACT--,--ID--=--name------------------------->

>--+---------------------+-------------------------------------><
   '-,--IDTYPE--=--XCFCP-'


Activate a control point (CDRSC minor node or application program minor node):

>>-VARY-- --NET--,--ACT--,--ID--=--name------------------------->

   .-,--IDTYPE--=--RESOURCE-----.  .-,--SCOPE--=--COMP-----.   
>--+----------------------------+--+-----------------------+---><
   '-,--IDTYPE--=--+-CP-------+-'  '-,--SCOPE--=--+-ALL--+-'   
                   '-RESOURCE-'                   +-COMP-+     
                                                  +-ONLY-+     
                                                  '-U----'

Activate an SSCP (CDRM minor node)


Activate an SSCP (CDRM minor node):

>>-VARY-- --NET--,--ACT--,--ID--=--name------------------------->

                          (1)  .-,--IDTYPE--=--RESOURCE-----.   
>--+--------------------+------+----------------------------+--->
   '-,--HPR--=--+-NO--+-'      '-,--IDTYPE--=--+-SSCP-----+-'   
                '-YES-'                        '-RESOURCE-'     

   .-,--SCOPE--=--COMP-----.                              (2)   
>--+-----------------------+--+-------------------------+------><
   '-,--SCOPE--=--+-ALL--+-'  '-,--VRTGCPCP--=--+-YES-+-'       
                  +-COMP-+                      '-NO--'         
                  +-ONLY-+                                      
                  '-U----'

Notes:

HPR and VRTGCPCP are valid only if VRTG=YES is coded for the CDRM, and the CDRM is in an inactive state.
HPR and VRTGCPCP are valid only if VRTG=YES is coded for the CDRM, and the CDRM is in an inactive state.


Warm start a major node:

>>-VARY-- --NET--,--ACT--,--ID--=--major_node_name--,--WARM----><


Activate a definition file (a major node with no subordinate resources):

>>-VARY-- --NET--,--ACT--,--ID--=--major_node_name-------------><


Check the syntax of a definition file (major node):

>>-VARY-- --NET--,--ACT--,--ID--=--major_node_name-------------->

>--,--SCOPE--=--SYNTAX--+---------------------------------+----><
                        '-,--LOADMOD--=--load_module_name-'

Note: For an NCP major node, follow the syntax diagram for Activate an NCP major node: and specify the UPDATE operand.


Dynamically reconfigure resources in a major node:

>>-VARY-- --NET--,--ACT--,--ID--=--major_node_name-------------->

   .-,--SCOPE--=--COMP-----.  .-,--UPDATE--=--IMPLICIT-----.   
>--+-----------------------+--+----------------------------+---><
   '-,--SCOPE--=--+-ALL--+-'  '-,--UPDATE--=--+-IMPLICIT-+-'   
                  +-COMP-+                    +-ADD------+     
                  +-ONLY-+                    '-ALL------'     
                  '-U----'


Dynamically reconfigure TRLEs in a TRL major node:

>>-VARY-- --NET--,--ACT--,--ID--=--trl_major_node_name---------->

   .-,--UPDATE--=--ADD--------------.   
>--+--------------------------------+--------------------------><
   |                          (1)   |   
   '-,--UPDATE--=--+-IMPLICIT-----+-'   
                   +-ADD----------+     
                   '-ALL----------'

Notes:

Specifying UPDATE=IMPLICIT is the same as UPDATE=ADD.


Activate a group under an Enterprise Extender XCA major node:

>>-VARY-- --NET--,--ACT--,--ID--=--group_name------------------->

   .-,--SCOPE--=--COMP-----.   
>--+-----------------------+-----------------------------------><
   '-,--SCOPE--=--+-ALL--+-'   
                  +-COMP-+     
                  +-ONLY-+     
                  '-U----'


Activate other resources:

>>-VARY-- --NET--,--ACT--,--ID--=--name------------------------->

   .-,--DWACT--=--NO------.   
>--+----------------------+------------------------------------->
   '-,--DWACT--=--+-NO--+-'   
                  '-YES-'     

>--+------------------------------------------------------------+-->
   '-,--LOGON--=--appl_name--+--------------------------------+-'   
                             '-,--LOGMODE--=--logon_mode_name-'     

   .-,--SCOPE--=--COMP-----.   
>--+-----------------------+------------------------------------>
   '-,--SCOPE--=--+-ALL--+-'   
                  +-COMP-+     
                  +-ONLY-+     
                  '-U----'     

                                     (1)   
>--+-------------------------------+---------------------------><
   '-,--U--=--channel_unit_address-'

Notes:

The U operand is valid for a local SNA PU or a channel link.


Activate a model CDRSC and, optionally, all the clone CDRSCs created from it:

>>-VARY-- --NET--,--ACT--,--ID--=--model_cdrsc_name------------->

   .-,--SCOPE--=--COMP-----.   
>--+-----------------------+-----------------------------------><
   '-,--SCOPE--=--+-ALL--+-'   
                  +-COMP-+     
                  +-ONLY-+     
                  '-U----'

Abbreviations

Operand	Abbreviation
VARY	V
CPCP=NO	CPCP=N
CPCP=YES	CPCP=Y
DUMPLOAD=NO	DL=NO or DL=N
DUMPLOAD=YES	DL=YES or DL=Y
DUMPSTA	DST
DWACT=NO	DWACT=N
DWACT=YES	DWACT=Y
EXTERNAL	EXT
LOADFROM	LF
LOADFROM=EXTERNAL	EXT
LOADFROM=HOST	HOST
LOADMOD	LM
LOADSTA	LST
LOGMODE	LOG
SAVEMOD=NO	SM=NO or SM=N
SAVEMOD=YES	SM=YES or SM=Y
SCOPE=ALL	ALL
SCOPE=COMP	COMP
SCOPE=ONLY	ONLY
SCOPE=SYNTAX	SYNTAX
VRTGCPCP=NO	VRTGCPPC=N
VRTGCPCP=YES	VRTGCPPC=Y

When using an abbreviation in place of an operand, code the abbreviation exactly as shown in the table. For example, when coding the abbreviation for LOADFROM=EXTERNAL, code only EXT.

Purpose

The VARY ACT (activate) command activates VTAM® resources. Figure 1 shows each resource type for which the command is valid, and which operands can be used for that resource type. A large dot means that the operand can be specified for the resource, and an S means that the operand can be specified to sift down to subordinate resources.

If any of the DUMPLOAD, SAVEMOD, or LOADFROM operands are coded on a VARY ACT command, the target of the command is assumed to be an IBM® 3720 or 3745 Communication Controller with the hard disk option, and the following default values apply:

LOADFROM=HOST
SAVEMOD=NO
DUMPLOAD=NO

If all three are omitted, the target of the command is assumed not to be an IBM 3720 or 3745 Communication Controller and these operands do not apply.

Note: The combination LOADFROM=HOST,DUMPLOAD=YES,SAVEMOD=NO is not valid.

Figure 2 shows operands that are mutually exclusive for this command. To read the table, you:

Look at the operand name on the right of the table.
Read across the table to the left to find an X (to see the operands that cannot be coded with the operand named in the right list). If the X appears in another operand's vertical column, the two operands are mutually exclusive.
Match any number found at a row and column junction with the list of numbered notes that accompany the table to get information about unique restrictions or interactions.

The numbered fields in Figure 2 identify unique requirements and restrictions as follows:

LOAD=YES or LOAD=U is required if DUMPLOAD=YES, SAVEMOD=YES, or LOADFROM is coded. The converse is not true.
This combination is not valid if SAVEMOD=NO is coded or assumed by default.
SAVEMOD=YES is required if DUMPLOAD=YES is coded, but only when LOADFROM=HOST is also specified. The converse is not true.
LOADMOD is required if it differs from the ID (that is, if NEWNAME on the BUILD statement differs from the PUNAME).
LOADFROM=HOST is required if SAVEMOD=YES is coded. The converse is not true.
This combination is not valid if LOADFROM=HOST is coded.

Note: Specification of WARM and SCOPE together causes the command to fail.

NO is the default for both SAVEMOD and DUMPLOAD (DUMPLD on the PCCU definition statement). If a value is specified on the PCCU definition statement, it overrides the default. If a value is specified on the VARY ACT command, it overrides both the PCCU definition statement value and the default value. This is shown in Table 1.

Figure 1. Valid resource types for VARY ACT

Table that shows the valid resource types and their valid operands for the VARY ACT command.

Figure 2. Mutually exclusive (X) operands for VARY ACT

Table that shows the matrix of mutually exclusive operands for the VARY ACT command.

Table 2 and Table 3 show the relationships between the SAVEMOD and DUMPLOAD operands as they relate to the LOADFROM=HOST ( Table 2) and LOADFROM=EXT ( Table 3) operands. SAVEMOD and DUMPLOAD (DUMPLD on PCCU) can be specified on either the PCCU definition statement or the VARY ACT command. See the z/OS Communications Server: SNA Resource Definition Reference for information about the PCCU definition statement.

In Table 2, Table 3, and Table 4, the following situations are assumed:

DUMPLOAD refers to both DUMPLOAD on the VARY ACT command and DUMPLD on the PCCU. The value to be used is determined by Table 1.
SAVEMOD refers to both SAVEMOD on the VARY ACT command and SAVEMOD on the PCCU. The value to be used is determined by Table 1.
Hard disk refers to the hard disk on the IBM 3720 or 3745 Communication Controller.

Table 4 shows how AUTODMP and AUTOIPL relate to the IBM 3720 or 3745 hard disk.

AUTODMP: If the NCP abends, an attempt to put the NCP dump on the hard disk is made if the dump/load switch is set. If there is an NCP dump on the hard disk for this CCU, a request is made to dump the NCP to the host. The value of the AUTODMP operand on the PCCU definition statement determines whether this request is automatically implemented.
AUTOIPL: If the NCP abends, and there is an NCP dump on the hard disk for this CCU, or if the automatic dump/load switch is set to NO, the value of the AUTOIPL operand on the PCCU definition statement determines how the NCP is reloaded.

If DUMPLOAD=YES (as determined in Table 1), the communication controller attempts to dump and load the NCP. If the dump and load are not successful, the action to be taken depends on the values of AUTODMP and AUTOIPL as shown in Table 4.

Note: For the DUMPSTA and LOADSTA operands, the operator must determine from the person who defined the VTAM system, the system programmer, whether a name has been given in the system definition statements for the link station. If a name has been defined already, then that name should be used for the DUMPSTA and LOADSTA operands. Otherwise, the operator can use the name automatically defined by VTAM.

Table 1. Precedence of values when SAVEMOD and DUMPLOAD are specified. These rules of precedence apply in both the VARY ACT command and PCCU definition statement.
VARY ACT	PCCU
VARY ACT	YES	NO	Not specified¹¹
YES	YES	YES	Yes
NO	NO	NO	NO
Not Specified	YES	NO	NO
Note: NO is the default for both SAVEMOD and DUMPLOAD (DUMPLD on PCCU).

Table 2. Results when LOADFROM=HOST or LOADFROM is not specified
DUMP- LOAD	SAVEMOD
DUMP- LOAD	YES	NO or not specified
YES	The NCP is loaded from the host into the CCU and saved on the hard disk. If the NCP abends: If there is no NCP dump on the hard disk for this CCU, the NCP dumps automatically to the hard disk and the CCU is reloaded automatically from the hard disk. If there is an NCP dump on the hard disk for this CCU, a request is made to dump the NCP to the host. If AUTOIPL=YES is coded on the PCCU definition statement, VTAM automatically reloads the NCP into the CCU by transferring the load module from the host. If AUTOIPL=NO is coded on the PCCU definition statement, the operator must request to reload the NCP into the CCU. This is done in one of the following ways: To transfer the load module from the host, enter the VARY ACT, LOADFROM=HOST command (see Table 4). To transfer the load module from the hard disk, enter the VARY ACT, LOADFROM=EXT command (see Table 4).	This is an incorrect specification or ignored if on the PCCU definition statement. The dump/load switches cannot be manipulated without saving the load module onto the hard disk unless the load module exists on the hard disk and is being reloaded with LOADFROM=EXT.
NO or Not Specified	The NCP is loaded from the host into the CCU and saved on the hard disk. The dump and reload of NCP into the CCU must be transferred to or from the host. If AUTOIPL=YES is coded on the PCCU definition statement, VTAM automatically reloads the NCP into the CCU by transferring the load module from the host. If AUTOIPL=NO is coded on the PCCU definition statement, the operator must request to reload the NCP into the CCU. To transfer the load module from the host, enter the VARY ACT, LOADFROM=HOST command (see Table 4). To transfer the load module from the hard disk, enter the VARY ACT, LOADFROM=EXT command (see Table 4).	The NCP is loaded only from the host into the CCU. The dump and reload of NCP into the CCU must be transferred to or from the host. If AUTOIPL=YES is coded on the PCCU definition statement, VTAM automatically reloads the NCP into the CCU by transferring the load module from the host. If AUTOIPL=NO is coded on the PCCU definition statement, the operator must request to reload the NCP into the CCU. To transfer the load module from the host, enter the VARY ACT, LOADFROM=HOST command (see Table 4).

Table 3. Results when LOADFROM=EXT is specified
DUMP- LOAD	SAVEMOD
DUMP- LOAD	YES	NO or not specified
YES	This is an incorrect specification or ignored if on the PCCU definition statement. It cannot be specified to load the CCU from the hard disk (LOADFROM=EXT) and to save the load module on the hard disk at the same time (SAVEMOD=YES).	The NCP is loaded into the CCU from the hard disk. If the NCP abends: If there is no NCP dump on the hard disk for this CCU, the NCP is automatically dumped to the hard disk and the CCU is automatically reloaded from the hard disk. If there is an NCP dump on the hard disk for this CCU, a request is made to dump the NCP to the host. If AUTOIPL=YES is coded on the PCCU definition statement, VTAM automatically reloads the NCP into the CCU by transferring the load module from the host. If AUTOIPL=NO is coded on the PCCU definition statement, the operator must request to reload the NCP into the CCU. This is done in one of the following ways: To transfer the load module from the host, enter the VARY ACT, LOADFROM=HOST command (see Table 4). To transfer the load module from the hard disk, enter the VARY ACT, LOADFROM=EXT command (see Table 4).
NO or Not Specified	This is an incorrect specification or ignored if on the PCCU definition statement. It cannot be specified to load the CCU from the hard disk (LOADFROM=EXT) and to save the load module on the hard disk at the same time (SAVEMOD=YES).	The NCP is loaded into the CCU from the hard disk. The dump and reload of NCP into the CCU must be transferred to or from the host. If AUTOIPL=YES is coded on the PCCU definition statement, VTAM automatically reloads the NCP into the CCU by transferring the load module from the host. If AUTOIPL=NO is coded on the PCCU definition statement, the operator must request to reload the NCP into the CCU. To transfer the load module from the host, enter the VARY ACT, LOADFROM=HOST command (see Table 4).

Table 4. Actions to be taken for unsuccessful DUMP and LOAD
DUMP- LOAD	AUTODMP on PCCU		AUTOIPL on PCCU
DUMP- LOAD	YES	NO	YES	NO
YES	NCP dump is automatically transferred to the host.	The operator must decide whether to dump the NCP. The operator indicates whether to dump the NCP in response to the prompt shown.	The NCP is automatically loaded into the CCU from the host even though the NCP load module is on the hard disk.	The operator must reload the NCP by issuing either the VARY ACT, LOADFROM=EXT command to reload the NCP from the hard disk or the VARY ACT, LOADFROM=HOST command to reload the NCP from the host.
NO or Not Specified	NCP dump is automatically transferred to the host.	The operator must decide whether to dump the NCP. The operator indicates whether to dump the NCP in response to the prompt shown.	The NCP is automatically loaded into the CCU from the host.	The operator must reload the NCP by issuing the VARY ACT, LOADFROM=HOST command to reload the NCP from the host.

Operands

ANS

Specifies whether VTAM should put a switched SDLC line in answer mode. The VARY ACT command with the ANS operand has the same effect as the VARY ANS command with the ACT operand. See the VARY ANS command for more information about the VARY ANS command.

ANS=ON: Specifies that VTAM should put the switched SDLC line in answer mode. When the line is in answer mode (and active), the NCP answers incoming calls from dial-in devices and notifies VTAM of the calls so that sessions can be established.
ANS=OFF: Specifies that VTAM should not put a switched SDLC line in answer mode. If there is an existing session for the line, ANS=OFF does not break the session, but no further calls are accepted after the session ends.

CPCP

Applies for adjacent link stations and indicates whether the connection is to support CP-CP sessions. Using this operand, you can override the value of the CPCP operand on the PU definition statement. You can also specify CPCP for an NCP nonswitched line to indicate whether PUs under the line are to support CP-CP sessions. If CPCP is not specified on the VARY ACT command, CP-CP session capability on the connection is determined from the PU definition statement or from the CPCP start option. If CPCP is specified on the VARY ACT command, the value affects only a single activation instance. Subsequent activations use the predefined values for that PU.

The resource must be in an inactive or connectable state; otherwise the command fails and an error message is issued. CP-CP session capability is determined during XID exchange and cannot be changed after a connection is established.

CPCP=YES: Indicates that the connection is to support CP-CP sessions.
CPCP=NO: Indicates that the connection is not to support CP-CP sessions.

DUMPLOAD

Applies only if LOAD=YES is specified or if LOAD=U is specified or assumed by default. Specifies whether the automatic dump/load switch in the IBM 3720 or 3745 Communication Controller should be set to on or off. The switch controls automatic dumping and reloading of an NCP to or from the hard disk in the event of an NCP abend.

See Table 2 and Table 3 for additional information about DUMPLOAD specifications.

Existing automatic IPL settings for a load module are retained by the IBM 3720 or 3745 Communication Controller (that is, DUMPLOAD does not default) if the following situations are true:

DUMPLD is not specified in the PCCU definition statement
DUMPLOAD, SAVEMOD, and LOADFROM are not specified in the VARY ACT command
A copy of the load module is already stored on the IBM 3720 or 3745 Communication Controller hard disk

DUMPLOAD=YES: Turns the automatic dump/load switch on. When the NCP abends, the switch is tested. If the switch is on, and if there is no NCP dump on the hard disk for this CCU, a dump of the NCP is stored on the IBM 3720 or 3745 Communication Controller hard disk. If the dump slot is full and AUTODMP=YES on the PCCU definition statement, the dump is transferred to the host. Otherwise, the network operator is prompted as specified in Table 4.
After a dump has been stored, the controller is reloaded with the active NCP load module from the IBM 3720 or 3745 Communication Controller. The automatic load takes place only if the automatic dump has successfully occurred.
DUMPLOAD=NO: Turns off the automatic dump/load switch in the communication controller. The controller is not automatically dumped and reloaded from the hard disk.

DUMPSTA=link_station_name

Applies only to the first activation of an NCP. (That is, DUMPSTA does not apply if the NCP is already active or is in the process of being activated.)

DUMPSTA specifies the name of a link station in an adjacent subarea node through which any later static dump operations for this NCP are to be carried out. The VTAM-generated link station name (a 3-digit or 4-digit hexadecimal device number followed by -S) can be specified. The link station can be either a channel link station or an SDLC link station in an NCP major node. The link station cannot be an SDLC link station in a channel-attachment major node. The link station identified for DUMPSTA should also be identified in the device number (U) or RNAME specifications for this NCP, either in the NCP definition or in this VARY ACT command.

Note: DUMPSTA does not support switched, X.25, or token-ring link stations.

The DUMPSTA operand, if specified, overrides any NCP definition value of DUMPSTA. If DUMPSTA is not specified in either the NCP definition or this command, VTAM selects (at the time of each dump operation) an available adjacent link station, giving preference to a channel link station. Similarly, if DUMPSTA is specified without a value (that is, if DUMPSTA= is specified), DUMPSTA assumes that a null value and VTAM selects an available adjacent link station as previously described.

Note: All references to NCP definition should be "NCP PCCU definition".

DWACT

Specifies whether to dial the PUs that are activated as a result of the activation of the switched major node or switched PU named on the ID operand.

Activation of PUs subordinate to the switched major node is determined by the ISTATUS value coded on the PU definition statement and the SCOPE value on the VARY ACT command. Specifying DWACT=YES on the major node activation prevents you from having to issue a VARY DIAL command for each PU individually after the PU is activated. For more information about the use of DWACT with a switched physical PU and associated logical hierarchy, see the z/OS Communications Server: SNA Network Implementation Guide.

DWACT=YES: Dials the PUs that are activated as a result of the switched major node or switched PU activation.
Note: For switched PU activation, the PU is dialed on initial activation only; DWACT=YES has no affect on VARY INACT,R command processing. This command causes the PU to be deactivated and then activated, but no dial operation is performed.
DWACT=NO: Does not dial the PUs that are activated as a result of the switched major node or switched PU activation. Specifying DWACT=NO on the VARY ACT command does not override DWACT=YES specified on the PU definition statement.

HPR

Specifies HPR capability at the link level. The use of the HPR operand on this command overrides what is coded for HPR on the CDRM, GROUP, LINE, or PU definition statements. HPR is valid on activation of a CDRM, GROUP, LINE, or PU in an HPR-capable node. For information about HPR capability for various node and connection types, see the z/OS Communications Server: SNA Network Implementation Guide.

Note: For a CDRM, this operand is valid only if VRTG=YES is specified for the CDRM, and the CDRM is in an inactive state; otherwise, the command fails and an error message is issued.

HPR=YES: Specifies that the GROUP, LINE, PU, or VR-based TG to the CDRM being activated is HPR-capable.
HPR=NO: Specifies that the GROUP, LINE, PU, or VR-based TG to the CDRM being activated is not HPR-capable.

ID=name

Specifies the name of the resource to be activated. The name can be a network-qualified name. It cannot be a USERVAR or LUALIAS name. If the name specified on the ID operand is network-qualified, this name is considered to be the real name of the resource. The name can be an ACB name or an alias name, provided that it is not network-qualified.

The following example of an APPL major node definition shows how application names can be network-qualified:

x      APPL ACBNAME=y,...

In the above example, x (the application name) can always be network-qualified. y (the ACB name) can be network-qualified only if y is the same as x.

To activate the dynamic local SNA major node for XCF connections, specify ID=ISTLSXCF.

To reactivate a dynamic XCF local SNA PU representing the connection to another VTAM, you can specify one of the following names:

The name of the PU
The CP name of the other VTAM with IDTYPE=XCFCP

For a CDRM, you can specify a network-qualified name, but this does not remove the restriction that the non-network-qualified CDRM name must be unique across networks.

If the resource is a TRL major node, specify the VTAMLST member name as the ID value. The command builds the TRL major node using the set of TRLE definition statements that are defined in the TRL major node. ISTTRL is the name of the VTAM internal table that is used for dynamic TRLEs, and should not be used as the VTAMLST member name of a predefined TRL major node. ISTTRL is not allowed as the resource name in a VARY ACT command. The issuance of the command VARY ACT,ID=ISTTRL always results in error message IST607I VARY ACT FOR ISTTRL FAILED -- INVALID NODE TYPE OR STATE.

If the resource is an NCP:

If PUNAME is specified in the BUILD definition statement, the ID operand must specify that PUNAME value.
If PUNAME is not specified in the BUILD definition statement, the ID operand can specify any name that you want (that is not already known to this VTAM), and use the LOADMOD operand to identify the actual NCP major node. After the NCP is active, the name specified on the ID operand is the name used to identify the NCP (not the load module name specified on LOADMOD).

If the resource is a switched major node containing PUs supported by a dependent LU requester (DLUR), the CPSVRMGR session is not activated until a VARY DIAL command is issued for the physical unit. See the VARY DIAL command for more information.

If the resource is a model CDRSC, the state of the model CDRSC becomes active. This means that the model CDRSC is available to build clone CDRSCs.

If the resource is a model application program, the state of the model application program becomes connectable (CONCT). This means that the model application program definition is available to build dynamic application programs.

You cannot activate dynamic application programs with the VARY ACT command. Dynamic application programs are activated only by opening their ACBs. For a dynamic application program to successfully open its ACB, a model definition must exist to build the dynamic application program, and that model definition must be connectable.

The following restrictions apply to VARY ACT depending on whether VTAM has been defined to support APPN function:

If VTAM has been defined as an APPN-only node, you cannot activate the following resources:
- NCP
- CDRM
- Path definition set
- Adjacent SSCP
If VTAM has been defined as a subarea-only node, you cannot activate the following resources:
- Adjacent CP
- Transmission group profile
- APPN Class of Service table
If VTAM has been defined as a migration data host, you cannot activate an NCP.
If VTAM has been defined as a network node, you cannot activate a network node server list. (The list can be activated only at an end node.)

If the named resource has subordinate resources (for example, logical units subordinate to a physical unit), those subordinate resources can also be activated using the SCOPE or WARM operands.

Independent LUs are not subordinate to any PU. Therefore, the sift-down to subordinate LUs does not affect independent LUs unless the ID value is a CDRSC major node.

You can individually activate multiple adjacent SSCP table definitions. Each new set of definitions is added to the internal table used by VTAM. New definitions for destinations already in the internal table replace the current adjacent SSCP list for those destinations, but you cannot deactivate existing adjacent SSCP lists. If a new table replaces an existing one, VTAM issues a message informing the operator.

To activate an APPN-to-subarea or subarea-to-APPN Class of Service mapping table, issue the VARY ACT command at the APPN-capable host that will use the table.

To activate a subarea mapping table, issue the VARY ACT command at the ICN host that will use the table.

To activate a network node server list, issue the VARY ACT command at the end node which will use the list. Note that this command activates the list, but the list is not used until the existing CP-CP session is terminated. If the end node has no CP-CP session when you issue this command, and an active link is available to one of the servers in the list, this command will activate a CP-CP session and activate the server list. If you choose not to activate your own network node server list at end node initialization, a network node server list consisting of a single nameless NETSRVR definition statement is automatically activated by default.

You can dynamically replace a network node server list by creating a new list, issuing VARY ACT to activate the new list, and issuing VARY TERM to terminate the existing CP-CP session. VTAM will automatically drive a new CP-CP session using the new list. A network node server list cannot be deactivated.

To activate a SAW sense filter, issue the VARY ACT command at the host node that will use the table.

To activate a generic resources preferences table, issue the VARY ACT command at the nodes that will perform generic resource resolution. Only one GRPREFS table can be active at a node at one time. The most recently activated GRPREFS table replaces any previously active GRPREFS table. If you do not activate your own generic resources preferences table, a generic resource preference table with a single default GRPREFS definition statement is automatically activated.

IDTYPE

Specifies the type of resource that the ID operand names. If several types of resources share the same name, IDTYPE can be used to identify which resource the command should act on.

IDTYPE=CP

Specifies that the name on the ID operand is a CP. If an APPN connection exists, VTAM attempts to activate a CP-CP session between the host CP and the resource named on the ID operand.

Note: You cannot activate a CP-CP session to an adjacent CP running VTAM V4R1 if the link is already active.

IDTYPE=RESOURCE

Activates the resource specified on the ID operand.

If the resource VTAM finds is a CP and if an APPN connection exists, VTAM attempts to activate a CP-CP session between the host CP and the resource named on the ID operand.

If the resource VTAM finds is a host CP or an adjacent CP, VTAM searches for a CDRM with the name specified on the ID operand and activates the CDRM, as well.

If a CP and an SSCP are found with the specified name, VTAM activates both the CP and the SSCP simultaneously.

IDTYPE=SSCP

Specifies that the name on the ID operand is an SSCP. VTAM activates the CDRM by the name specified.

IDTYPE=XCFCP

Activates the dynamic XCF local SNA PU representing the connection to another VTAM, when the ID operand specifies the CP name of the other VTAM.

LOAD

Applies only to the first activation of an NCP. (That is, LOAD does not apply if the NCP is already active or is in the process of being activated.)

LOAD specifies whether the communication controller associated with the specified NCP is to be reloaded with the appropriate NCP load module.

A communication controller is associated with an NCP for the purposes of this command if any of the following conditions are met:

It is already known to contain the named NCP.
It is attached through one or more of the adjacent link stations identified by the NCP's device number (U) or RNAME specifications, or both.
It is attached through the adjacent link station identified by the LOADSTA specification for the NCP.

LOAD=YES: Unconditionally loads the communication controller associated with the specified NCP, regardless of the current state or contents of the communication controller.
Note: If the NCP is being loaded by another host when this command is issued, the command fails.
LOAD=NO: Prevents the communication controller associated with the specified NCP from being loaded during the processing of this VARY ACT command, regardless of the current state or contents of the communication controller. (The communication controller is still subject to possible reload operations during error recovery procedures subsequent to the activation of the NCP.) If the communication controller does not contain the expected NCP load module, the VARY ACT command fails.
LOAD=U: Lets VTAM determine whether the communication controller associated with the specified NCP should be loaded during the processing of this VARY ACT command (based on the current contents of the communication controller and on the NCP definition statements), as it was before the availability of the LOAD operand.
For additional information about what VTAM does when LOAD=U is specified, see the z/OS Communications Server: SNA Network Implementation Guide.

Note: If this command is issued while another host is loading the NCP, you are notified, and VTAM waits until the load is complete from the other host. VTAM then loads the NCP as appropriate.

LOADFROM

Applies only if LOAD=YES or LOAD=U. It specifies whether VTAM loads the NCP module from the host or from the communication controller hard disk. See the z/OS Communications Server: SNA Resource Definition Reference for a complete description of the LOADFROM operand on the PCCU definition statement.

LOADFROM=HOST is not supported for loading an NCP attached by a token-ring, X.25 PVC or SVC, or X.21 switched, or frame relay connection. Specify LOADFROM=EXTERNAL for those line types.

See Table 2 and Table 3 for additional information about LOADFROM specifications.

LOADFROM=HOST: Loads the NCP from the host, using the SSP as the interface to the NCP load library.
Note: The combination LOADFROM=HOST,DUMPLOAD=YES,SAVEMOD=NO is not valid.
LOADFROM=EXTERNAL: Loads the NCP from the IBM 3720 or 3745 Communication Controller hard disk.

LOADMOD=load_module_name

Specifies the name of the load module to load. The load module name is the member name specified in the NCP LOADLIB. This name must match the major node name (the member name in VTAMLST).

The LOADMOD operand must be specified if the name of the PU specified in the BUILD definition statement is not the same as the load module name. Failure to code LOADMOD when the PU name and load module name differ prevents VTAM from locating the specific definition program you now want to activate. If NEWNAME is specified, the LOADMOD value must match the NEWNAME value specified in the BUILD definition statement.

LOADSTA=link_station_name

Applies only to the first activation of an NCP. (That is, LOADSTA does not apply if the NCP is already active or is in the process of being activated.)

LOADSTA specifies the name of a link station in an adjacent subarea node through which any load operations for this NCP are to be carried out. The VTAM-generated link station name (a 3-digit or 4-digit hexadecimal device number followed by -S) can be specified. The link station can be either a channel link station or an SDLC link station in an NCP major node. The link station identified for LOADSTA should also be identified in the device number (U) or RNAME specifications for this NCP, either in the NCP definition or in this VARY ACT command.

The link station cannot be an SDLC link station in a channel-attachment major node.

The LOADSTA operand, if specified, overrides any NCP definition value of LOADSTA. If LOADSTA is not specified in either the NCP definition or on this command, VTAM selects (at the time of each reload operation) an available adjacent link station, giving preference to a channel link station. Similarly, if LOADSTA is specified without a value (that is, if LOADSTA= is specified), LOADSTA assumes that a null value and VTAM selects an available adjacent link station from the NCP link station queue in the following order:

Channel
Active leased
Active dial-out switched
Active dial-in switched
Pending active leased
Pending active dial-out switched
Pending active dial-in switched
Dummy (undefined)

If the NCP is on a communication controller that is attached to VTAM by a serial optical channel (SOC), and you are reloading the NCP with a new load module, the LOADSTA operand is required and the link station name that you specify must be defined as an IPL port in the Telecommunication Service Processor (TSP). This is because ESCON support allows up to 16 SOC link stations to be defined as parallel TGs, and only one or two of these link stations are defined as IPL ports. The NCP load will fail if the link station is not defined as an IPL port in the TSP. (Because a maximum of eight VRs can be active at a time, only eight of the 16 parallel TGs can be attached between the host and the NCP at a time.)

LOGMODE=logon_mode_name

Specifies the logon mode name to be used for any logon initiated for a logical unit as a result of this command (see the description of the LOGON operand). This logon mode name also becomes the logon mode name for all future automatic logons performed by VTAM for logical units within the scope of this command and for their controlling primary LUs (if any).

LOGMODE is valid only if LOGON is specified. If LOGMODE is specified without LOGON, the command fails and an error message is issued.

If LOGMODE is not specified, the LOGMODE value specified in any previous command applicable to a logical unit also within the scope of this VARY ACT command is used. If no LOGMODE value was ever specified for a given logical unit within the scope of this command, the logical unit's default value is used.

LOGON=appl_name

Specifies the name of an application program (primary LU) to which any secondary LUs within the scope of this command are to be logged on. The application name can be network-qualified. If it is, the network identifier is considered to be real, but the resource name is considered to be generic (that is, the resource name can be either the real application name or a USERVAR name).

If the application name is an ACB name, and the ACB name matches the name on the APPL definition statement, then you can use a network-qualified ACB name.

If a USERVAR is found, VTAM resolves its name to the name of the VTAM application with which it is currently associated. If a USERVAR with this name is not found, VTAM searches for an application program with this name.

If the primary LU is an application program in this domain, the name must be that of an application program minor node within an active application program major node.

If the primary LU is a predefined CDRSC, the CDRSC must be active.

If the primary LU is a device-type LU, it must be attached to the same NCP as the secondary LU.

See also the VARY LOGON command for more information about the operator-initiated logon function.

NEWPATH=name

Specifies the dynamic path update member names in the VTAM definition library. When the NCP is successfully activated, VTAM processes and sends path table update specifications to the NCP. The NEWPATH operand is valid only when an NCP major node is being activated.

Up to three member names can be specified; if more than three member names are specified, the VARY command is rejected, and you must issue a new path command to activate the NCP. If more than one member name is specified, the names must be enclosed in parentheses and separated by commas.

VTAM sends the path table update specifications with the SSCP-PU session before any links, other than the link for the SSCP-PU session, are activated. If you attempt to change or delete the explicit route being used for the SSCP-PU session, the NCP rejects the request (because the explicit route is currently operative), and VTAM displays a warning message.

This operand overrides NEWPATH specifications on the PCCU definition statement in the NCP's generation file (see the z/OS Communications Server: SNA Resource Definition Reference ). For example, if the PCCU NEWPATH operand specifies three member names and the VARY ACT NEWPATH operand specifies one member name, only the one member specified in the VARY ACT command is processed. If you specify "NEWPATH=," or "NEWPATH= " in the VARY ACT command, the NEWPATH operand coded in the PCCU definition statement is nullified.

NEWPATH processing does not affect NCP activation in any way. For example, if the member specified with the NEWPATH operand cannot be processed because of a shortage of VTAM storage, an appropriate message is displayed and no further recovery processing is attempted.

When a dynamic path update member is processed as a result of a NEWPATH operand, any path table update specifications for VTAM subareas and other NCP subareas are discarded. However, VTAM checks the validity of PATH statements and issues warning messages if errors are detected.

RNAME=name

Applies to the activation of an NCP or, in certain migration cases, to the activation of a link station.

For an NCP, the RNAME operand is described in the following paragraphs and applies only to the first activation of the NCP. (That is, RNAME does not apply if the NCP is already active or is in the process of being activated.)

Note: When activating NCPs, if the RNAME is referring to a switched link station, activate the switched major node before issuing the VARY ACT command for the NCP. Otherwise, the NCP activation might fail.

RNAME specifies the names of up to 13 SDLC or channel link stations in adjacent subarea nodes through which the specified NCP is attached to the network. It also specifies which link stations (and associated links) in adjacent subarea nodes are to be automatically activated as part of the activation of the specified NCP. Therefore, these RNAME values identify the location of the communication controller in the network and enable VTAM to establish the necessary connectivity to the specified NCP (if such connectivity does not exist).

If more than one link station name is specified, the names must be enclosed in parentheses and separated by commas.

The RNAME operand, if specified, overrides any NCP definition RNAME values or the checkpointed RNAME values for the specified NCP. For a list of the checkpointed parameters for each major node and for a general description of the configuration restart facility, see the z/OS Communications Server: SNA Network Implementation Guide.

If RNAME values are specified on this command, VTAM uses those values to determine the link stations to be used. If the RNAME operand is not specified on this command, VTAM uses the checkpointed RNAME values for the specified NCP (if the WARM operand is specified). If neither the RNAME nor the WARM operand is specified, VTAM uses the NCP definition values for RNAME, if any. If RNAME is not specified in the NCP definition, RNAME assumes a null value, and no SDLC link stations are automatically activated. If the RNAME operand is specified without a value (that is, RNAME= is specified), RNAME assumes a null value.

If both the RNAME and the device number specifications have null values, no automatic link station activations are performed, and there must be link stations already active in adjacent subarea nodes to provide the required connectivity. If this is not so, the VARY ACT command fails.

SAVEMOD

Applies only if LOAD=YES or LOAD=U. It specifies whether the NCP load module is saved on the communication controller hard disk after the NCP is loaded from the host.

See Table 2 and Table 3 for additional information about SAVEMOD specifications.

SAVEMOD=YES

Saves the NCP on the communication controller hard disk after the NCP is loaded from the host.

If both load module data sets are full for this CCU, and:

The name specified matches the name of a load module already stored, the load module with that name is replaced.
The name specified does not match the name of a load module already stored, the oldest load module is replaced.

SAVEMOD=NO

Does not save the NCP load module on the IBM 3720 or 3745 Communication Controller hard disk after the NCP is loaded from the host.

SCOPE

Specifies the scope of the command.

WARM and SCOPE cannot be specified on the same command. If both are specified, the command fails.

The only SCOPE value applicable to model major node, LUGROUP major node, path definition set, or adjacent SSCP tables is SCOPE=SYNTAX.

SCOPE has no effect for a TRL major node. If the SCOPE value is specified for this resource, VTAM issues message IST1275I to indicate that the operand was ignored and continues processing.

For configuration restart, the checkpoint data set is updated with information about these resources, unless SCOPE=SYNTAX is specified. No information is stored in the checkpoint data set if the SYNTAX option is used.

SCOPE=ALL

Specifies that the resource named in the ID operand and all of the appropriate subordinate resources are to be activated (regardless of their defined ISTATUS values). When the ID operand specifies a model CDRSC for the VARY ACT command, any existing inactive clone CDRSCs created from the model CDRSC are activated again.

SCOPE=COMP

Specifies one of the following actions:

For the initial activation of a major node, activates all subordinate minor nodes according to the ISTATUS specification. (This is the same as SCOPE=U.)
For a major node that is already active:
- If UPDATE=ADD|ALL is specified on the same command, VTAM updates the current configuration to match the VTAMLST definition and activates minor nodes based on the ISTATUS value.
- If UPDATE=IMPLICIT is specified or assumed by default, VTAM activates all subordinate minor nodes that were not previously active. (Logical units are activated according to their ISTATUS specification if the PU was not previously active. Otherwise, they are not activated.)
For a minor node, the action depends on the node type, as follows:
Node Action

Group, PU Same as SCOPE=U

Line, LU, APPL, CDRSC, link station Same as SCOPE=ONLY

LU activation varies according to the owning PU status when processing a SCOPE=COMP on an active major node. A previously inactive PU is activated and its subordinate LUs are activated according to their ISTATUS specification. The LUs of a previously active PU are ignored.

SCOPE=ONLY

Specifies that only the resource named in the ID operand is to be activated; none of its subordinate resources are to be activated (regardless of their defined ISTATUS values).

SCOPE=SYNTAX

Node	Action
Group, PU	Same as SCOPE=U
Line, LU, APPL, CDRSC, link station	Same as SCOPE=ONLY

Specifies that the major node named on the ID operand is to have its VTAMLST definition file checked for syntax errors. This validation does not include user-replaceable tables, such as USS tables and ALS tables. The error checking consists of validation of syntax, definition statements, operands, and the type of the operands. This checking is the same as is done when the VARY ACT command is used to activate a resource. When SCOPE=SYNTAX is specified, no resource activation takes place.

The ID operand is required. The LOADMOD operand must be used if the name specified on the PUNAME operand in the NCP BUILD definition statement is not the same as the load module name. See the description of the ID operand for more information. All other operands are ignored if SCOPE=SYNTAX is specified.

All major node types (including path definition set and adjacent SSCP tables) shown in Figure 1 can be specified using SCOPE=SYNTAX.

Note: SCOPE=SYNTAX builds an internal representation of the resources in the file being checked, and might have an impact on storage until the command completes. VTAM uses approximately 600 bytes of storage for each definition statement included in the definition file. See the z/OS Communications Server: SNA Resource Definition Reference for more information about definition statements.

SCOPE=U

Specifies that the resource named in the ID operand, and all the appropriate subordinate resources defined with ISTATUS=ACTIVE, are to be activated.

U=channel_unit_address

Specifies the hexadecimal device number by which a channel attachment to a communication controller, to an adjacent host, or to an SNA physical unit is known to the operating system and through which VTAM is to establish connectivity to the specified NCP, VTAM, or physical unit. A device number must be supplied for a channel-attached physical unit because the physical unit can communicate only through the channel. Likewise, a device number must be supplied for a channel-attached host because the adjacent host can communicate directly only through the channel attachment. A device number is optional for an NCP because an NCP can also communicate across SDLC links. This operand has no effect if the node is being activated or is currently active.

For a channel-attachment major node, the U operand overrides any previous device number specifications, including the ADDRESS operand on the LINE definition statement of the channel-attachment major node definition.
Omit the U operand if you are activating a channel-attachment major node that has LNCTL=MPC in its definition. Otherwise, the activation of resources in the multipath channel (MPC) group will fail.

If the U operand is omitted and there is no current device number specification for VTAM, the VARY ACT command fails. The VARY ACT command also fails if the U operand is specified without a value (that is, if U= is specified).
For an SNA physical unit, the U operand, if specified, overrides any previous device number specifications for the physical unit, including the CUADDR operand on the PU definition statement.
The U operand, if specified, overrides any specification maintained by configuration restart.

If the U operand is omitted and there is no current device number specification for the physical unit, the VARY ACT command fails. The VARY ACT command also fails if the U operand is specified without a value (that is, if U= is specified).
For an NCP, the U operand, if specified, overrides any NCP definition CUADDR values or the checkpointed device number values for the specified NCP. If a U value is specified on this command, VTAM uses the value to determine the link station to be used. If the U operand is not specified on this command, VTAM uses the checkpointed device number values for the specified NCP (if the WARM operand is specified). If neither the U nor the WARM operand is specified, VTAM uses the NCP definition value for CUADDR, if any. If CUADDR is not specified in the NCP definition, the device number specification assumes a null value, and no channel link station is automatically activated. If the U operand is specified without a value (that is, if U= is specified), the device number specification assumes a null value.
If both the RNAME and the device number specifications have null values, no automatic link station activations are performed, and there must be link stations already active in adjacent subarea nodes to provide the required connectivity. If this is not so, the VARY ACT command fails.

UPDATE

Using this operand, you can dynamically implement changes that you have made in a VTAMLST definition file. You can use the UPDATE operand to make the following kinds of dynamic reconfiguration changes:

Cross Domain Resource (CDRSC) major node: add and delete CDRSCs; dynamically change certain operand values on CDRSC definition statements.
Local SNA major node: add and delete LUs; dynamically change certain operand values on LU definition statements.
NCP major node: add, delete, and move PUs and LUs; dynamically change certain VTAM-only operand values on PU and LU definition statements.
Switched major node: add and delete PUs and LUs; dynamically change certain operand values on PU, LU, and PATH definition statements.
Transport resource list (TRL) major node: add, delete, or replace TRLEs; dynamically change operand values on TRLE definition statements.
Enterprise Extender (EE) XCA major node: add, delete, or dynamically change GROUP, LINE, and connection network definitions on the PORT definition statements.
Application program (APPL) major node: add, delete, or dynamically change GROUP and APPL definition statements.

VTAM reads the VTAMLST definition file for the major node and updates the current configuration to match the definition. The affected minor nodes must be inactive (except for PATH definition statements in the switched major node), but the major node can remain active. For more information about dynamic reconfiguration, see the z/OS Communications Server: SNA Network Implementation Guide. For information about which operands in PU and LU definition statements can be dynamically changed, see the z/OS Communications Server: SNA Resource Definition Reference.

Requirement: For an active QDIO TRLE, the TCPIP devices using this TRLE must be stopped and 2 minutes must pass before the TRLE can be updated.

If you have used the VARY LOGON command to establish an automatic logon relationship that was not coded on the LOGAPPL operand of a definition statement, or if you have used the VARY NOLOGON command to terminate an automatic logon relationship that was coded on the LOGAPPL operand of a definition statement, the VARY ACT,UPDATE=ALL command might undo the effects of these commands. This is because the LOGAPPL operand in the definition file overrides these commands. Even if no LOGAPPL is coded in the definition file, VTAM assumes a null value for LOGAPPL and the null value overrides the VARY LOGON value. To avoid undoing the effects of the VARY LOGON command, code the LOGAPPL definition statement with the required value. To avoid undoing the effects of the VARY NOLOGON command, delete the LOGAPPL operand from the definition statement. VARY ACT,UPDATE=ALL can undo the effects of the MODIFY DEFAULTS command in the same way.

VTAM issues an error message if a VARY ACT,UPDATE=ALL command is attempted for an active resource. For example, you might have activated an NCP, then issued a VARY LOGON command for some of the LUs under the NCP. (The VARY LOGON command overrides the LOGAPPL value that was used during NCP activation.) If you later issue a VARY ACT,UPDATE=ALL command to make some other kind of change, such as moving a PU from one line to another, and meanwhile the LUs are active that have the new LOGAPPL value, VTAM will issue an error message. This is because the VARY ACT,UPDATE=ALL command overrides the VARY LOGON command; that is, VTAM encounters a defined LOGAPPL value that is different from the current value, so it attempts an operand change, but the operand change fails because the LUs are active.

Dynamic reconfiguration for an NCP:

For an NCP, this command performs the following functions without regenerating the NCP:

Adds a nonswitched physical unit and its subordinate LUs to a line
Adds a logical unit to a nonswitched physical unit
Passes the GP3174 and RETRIES operands to NCP when dynamically adding a PU
Moves a nonswitched physical unit and its subordinate LUs from one line to another
Moves a logical unit to another physical unit
Changes a nonswitched physical unit link station address (except on the initial activation of the NCP)
Changes the LOCADDR for an LU (except on the initial activation of the NCP)
Deletes a nonswitched physical unit and its subordinate LUs from a line
Deletes a dependent logical unit from a nonswitched physical unit
Changes certain operand values in PU and LU definition statements
Adds or deletes frame relay PUs and their associated FRSESET definition statements

The active and inactive requirements for the reconfiguration operations are shown in Table 5.

Table 5. Active and inactive status requirements for dynamic reconfiguration of an NCP
Operation	Major node	LINE	PU	LU
Add LU	Active	Either	Either	N/A
Add PU	Active	Either	N/A	N/A
Delete PU¹	Active	Either	Inactive	Inactive
Delete LU¹	Active	Either	Either	Inactive
Move PU	Active	Either	Inactive	Inactive
Move LU	Active	Either	Either	Inactive
Note: The current state and desired state of the resource must be inactive.

To prepare another host for backup and takeover, you can issue a VARY ACT command with the UPDATE operand at a VTAM that does not own selected NCP resources to prepare that VTAM for a future takeover of those resources. The command fails if UPDATE is specified on the same command with the LOGON, LOGMODE, WARM, or ACQ (as in VARY ACQ) operands. UPDATE has no meaning on the initial activation of major nodes other than an NCP major node.

Conflicts can arise between the NCP source file and the generated NCP load module. If you modify the NCP source, moving PUs and LUs, use UPDATE=ALL when activating an inactive NCP. Otherwise VTAM and NCP will not agree on the location of the PUs and LUs. It is recommended that you always use UPDATE=ALL for the initial activation of an NCP if you are using (or plan to use) dynamic reconfiguration with that NCP. If the source file has changed, VTAM will change and start the NCP correctly. If the source file has not changed, VTAM will start the NCP as usual.

You can use VARY ACT with the UPDATE operand to dynamically reconfigure a frame relay switching equipment set (FRSESET). In order to modify an FRSESET, you need to know whether the FRSESET was statically or dynamically defined. If you are not sure, you can issue a DISPLAY NET,ID=frseset_name command to find out. Statically means that the FRSESET was included in the NCP generation. Dynamically means that the FRSESET was not included in the NCP generation. Statically and dynamically defined PUs cannot be specified in the same FRSESET; the PUs must be all static or all dynamic.

If the FRSESET was dynamically defined, you can dynamically add and delete PUs from the set. You can delete PUs with the MODIFY DR, VARY DRDS, or VARY ACT,UPDATE=ALL commands. You can add PUs only with the VARY ACT,UPDATE=ADD or VARY ACT,UPDATE=ALL command.

If the FRSESET was statically defined, you can delete PUs from the set, but you cannot add PUs. In practical terms, this means you need to delete the entire FRSESET and then add it back dynamically in order to make changes. For example, if you have a statically defined FRSESET containing two primary PUs and you want to add two backup PUs, follow these steps:

Delete the two primary PUs, deleting the FRSESET itself (because it is empty).
Edit the VTAMLST source file to add the PU definitions for the backup PUs and add the backup PUs to the FRSESET.
Use the VARY ACT command with UPDATE=ADD or UPDATE=ALL. The VARY ACT command causes the FRSESET to be dynamically defined.

If you delete one or more PUs (using MODIFY DR or VARY DRDS) from a statically defined FRSESET without deleting the whole FRSESET, VARY ACT will cause the deleted PUs to be added back, but they will not be part of the FRSESET.

The first PU under a frame relay line (the LMI) cannot be deleted and it cannot be part of an FRSESET.

For more information about how to define frame relay lines, frame relay PUs, and FRSESETs, see the z/OS Communications Server: SNA Resource Definition Reference.

Dynamic reconfiguration for local SNA major nodes:

This command adds and deletes LUs for local SNA major nodes.

The active and inactive requirements for the reconfiguration operations are shown in Table 6.

Table 6. Active and inactive status requirements for dynamic reconfiguration for a local SNA major node
Operation/ resource	Major node	LINE	PU	LU
Add LU	Active	Either	Either	N/A
Delete LU	Active	Either	Either	Inactive

UPDATE=IMPLICIT

Has meaning only on the initial activation of an NCP. Otherwise UPDATE=IMPLICIT has no effect. For the initial activation of an NCP, UPDATE=IMPLICIT dynamically adds resources. If you specify UPDATE=IMPLICIT for a TRL major node, it is changed to UPDATE=ADD.

UPDATE=ADD

You can add resources. The major node must be active, unless it is an NCP major node, which can be either active or inactive. VTAM reads the VTAMLST definition file for the major node and adds any new resources to the current configuration. For a TRL major node, this is the default.

UPDATE=ALL

You can add, move, and delete resources in certain major nodes, and to add, delete, and replace existing TRLEs in an active TRL major node. TRLEs that are in use, however, are not deleted and remain in the TRL major node along with the new TRLEs.

Note: Moving resources requires that you issue the VARY ACT,UPDATE command twice. Resource deletions occur during the first processing of the command, and resource additions occur during the second processing of the command. See the z/OS Communications Server: SNA Network Implementation Guide for more information about dynamic reconfiguration changes.

The UPDATE=ALL operand also enables you to change certain operands in PU, LU, GROUP, LINE, PORT, APPL, and CDRSC definition statements in the following active nodes:

Cross-domain resource major node
Local SNA major node
NCP major node (VTAM-only operands)
Switched major node
TRLE major node
Enterprise Extender XCA major node
Application program major node

See the major node descriptions in the z/OS Communications Server: SNA Resource Definition Reference for more information about the operands that you can change for each major node.

VRTGCPCP

Applies for cross-domain resource managers (CDRM) and indicates whether the virtual-route-based transmission group is to support CP-CP sessions. Using this operand, you can override the value of the VRTGCPCP operand on the CDRM definition statement. If VRTGCPCP is not specified on the VARY ACT command, CP-CP session capability over the virtual-route-based transmission group connection is determined from the CDRM definition statement or from the VRTGCPCP start option. If VRTGCPCP is specified on the VARY ACT command, the value affects only a single activation instance. Subsequent activations use the predefined values for that CDRM.

This operand is valid only if VRTG=YES is specified for the CDRM, and the CDRM is in an inactive or connectable state; otherwise the command fails and an error message is issued.

VRTGCPCP=YES: Specifies that the virtual-route-based transmission group is to support CP-CP sessions.
VRTGCPCP=NO: Specifies that the virtual-route-based transmission group is not to support CP-CP sessions.

WARM

Applies only to certain major nodes (as shown in Figure 1) and specifies that the major node named in the ID operand is to be activated to the status it had when it was last active. That is, those minor nodes that were active the last time the major node was active are reactivated, and other operator-modified values applicable to the major node or its minor nodes (such as controller application name and logmode name for a logical unit) are restored. By recording changes in a configuration restart file, VTAM tracks the status of the minor nodes and also operator changes to other checkpointed parameters. For a list of the checkpointed parameters for each major node and for a general description of the configuration restart facility, see the z/OS Communications Server: SNA Network Implementation Guide.

The WARM operand is not allowed and the VARY ACT command fails in the following circumstances:

WARM and SCOPE are specified on the same command.
WARM is specified for a major node that is already active.
WARM is specified when activating a major node that has no associated VSAM configuration restart file or whose configuration restart file has not been used (that is, contains no checkpointed information).

If you used a VARY ACT,UPDATE=ALL command for dynamic reconfiguration of the major node at some time before the warm start, the dynamic reconfiguration changes stay in effect after the warm start. This is because VTAM takes a checkpoint during the VARY ACT,UPDATE=ALL processing.