VARY INACT command


Deactivate an NCP major node:

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

   .-,--CDLINK--=--ACT-------.  .-,--RMPO--=--NO------.   
>--+-------------------------+--+---------------------+--------->
   '-,--CDLINK--=--+-ACT---+-'  '-,--RMPO--=--+-NO--+-'   
                   '-INACT-'                  '-YES-'     

>--+------------------------+----------------------------------><
   '-,--TYPE--=--+-FORCE--+-'   
                 +-IMMED--+     
                 +-REACT--+     
                 '-UNCOND-'


Deactivate an NCP line:

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

>--+--------------------------+--------------------------------><
   '-,--TYPE--=--+-FORCE----+-'   
                 +-GIVEBACK-+     
                 +-IMMED----+     
                 '-UNCOND---'


Deactivate a CDRM major node:

>>-VARY-- --NET--,--INACT--,--ID--=--node_name------------------>

>--+-------------+--+------------------------+-----------------><
   '-,--SAVESESS-'  '-,--TYPE--=--+-FORCE--+-'   
                                  +-IMMED--+     
                                  '-UNCOND-'


Deactivate a CDRM minor node:

>>-VARY-- --NET--,--INACT--,--ID--=--node_name------------------>

>--+--------------------+--+-------------+---------------------->
   '-,--IDTYPE--=--SSCP-'  '-,--SAVESESS-'   

>--+------------------------+----------------------------------><
   '-,--TYPE--=--+-FORCE--+-'   
                 +-IMMED--+     
                 '-UNCOND-'


Deactivate a CDRSC minor node:

>>-VARY-- --NET--,--INACT--,--ID--=--node_name------------------>

   .-,--DELETE--=--NO------.                         
>--+-----------------------+--+------------------+-------------->
   '-,--DELETE--=--+-NO--+-'  '-,--IDTYPE--=--CP-'   
                   '-YES-'                           

>--+------------------------+----------------------------------><
   '-,--TYPE--=--+-FORCE--+-'   
                 +-IMMED--+     
                 '-UNCOND-'


Deactivate the dynamic XCF local SNA major node:

>>-VARY-- --NET--,--INACT--,--ID--=--ISTLSXCF------------------->

>--+------------------------+----------------------------------><
   '-,--TYPE--=--+-FORCE--+-'   
                 +-IMMED--+     
                 '-UNCOND-'


Deactivate a dynamic XCF local SNA PU:

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

>--+---------------------+--+------------------------+---------><
   '-,--IDTYPE--=--XCFCP-'  '-,--TYPE--=--+-FORCE--+-'   
                                          +-IMMED--+     
                                          '-UNCOND-'


Deactivate a dynamic switched PU:

>>-VARY-- --NET--,--INACT--,--ID--=--pu_name-------------------->

>--+------------------------+----------------------------------><
   '-,--TYPE--=--+-FORCE--+-'   
                 +-IMMED--+     
                 '-UNCOND-'


Deactivate a dependent LU requester (DLUR):

                                               (1) (2)   
>>-VARY-- --NET--,--INACT--,--ID--=--dlur_name------------------>

   .-,--FINAL--=--NO------.                                 
>--+----------------------+--+--------------------------+------><
   '-,--FINAL--=--+-NO--+-'  '-,--TYPE--=--+-FORCE----+-'   
                  '-YES-'                  +-GIVEBACK-+     
                                           +-IMMED----+     
                                           '-UNCOND---'

Notes:

Depending on the value of the VARYWLD start option, wildcard values can be used for this operand.
Depending on the value of the GVBKDLY start option, GIVEBACK commands generated for DLURs using wildcard values might be paced by VTAM®.


Deactivate a PU supported by a DLUR:

>>-VARY-- --NET--,--INACT--,--ID--=--pu_name-------------------->

>--+--------------------------+--------------------------------><
   '-,--TYPE--=--+-FORCE----+-'   
                 +-GIVEBACK-+     
                 +-IMMED----+     
                 +-REACT----+     
                 '-UNCOND---'


Deactivate RTP PUs:

>>-VARY-- --NET--,--INACT--,--ID--=--rtp_pu_name---------------->

>--+----------------------+--,--TYPE--=--FORCE-----------------><
   '-,--FINAL--=--+-NO--+-'                      
                  '-YES-'


Deactivate other PUs:

>>-VARY-- --NET--,--INACT--,--ID--=--pu_name-------------------->

   .-,--FINAL--=--NO----------------------------------.   
>--+--------------------------------------------------+--------><
   '-,--FINAL--=--+-NO--+------------------------+--+-'   
                  |     '-,--TYPE--=--+-FORCE--+-'  |     
                  |                   +-IMMED--+    |     
                  |                   +-REACT--+    |     
                  |                   '-UNCOND-'    |     
                  '-YES--+------------------------+-'     
                         '-,--TYPE--=--+-FORCE--+-'       
                                       +-IMMED--+         
                                       '-UNCOND-'


Deactivate a model application and all the APPLs created from it:

>>-VARY-- --NET--,--INACT--,--ID--=--model_appl_name------------>

>--+------------------------+--+------------------+------------><
   '-,--TYPE--=--+-FORCE--+-'  '-,--SCOPE--=--ALL-'   
                 +-IMMED--+                           
                 +-REACT--+                           
                 '-UNCOND-'


Deactivate a group under an Enterprise Extender XCA major node:

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

>--+------------------------+----------------------------------><
   '-,--TYPE--=--+-FORCE--+-'   
                 +-IMMED--+     
                 '-UNCOND-'


Deactivate other resources:

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

>--+------------------------+----------------------------------><
   '-,--TYPE--=--+-FORCE--+-'   
                 +-IMMED--+     
                 +-REACT--+     
                 '-UNCOND-'


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

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

>--+------------------------+--+------------------+------------->
   '-,--TYPE--=--+-FORCE--+-'  '-,--SCOPE--=--ALL-'   
                 +-IMMED--+                           
                 '-UNCOND-'                           

   .-,--DELETE--=--NO------.   
>--+-----------------------+-----------------------------------><
   '-,--DELETE--=--+-NO--+-'   
                   '-YES-'


Deactivate a clone CDRSC:

>>-VARY-- --NET--,--INACT--,--ID--=--clone_cdrsc_name----------->

>--+------------------------+----------------------------------->
   '-,--TYPE--=--+-FORCE--+-'   
                 +-IMMED--+     
                 '-UNCOND-'     

   .-,--DELETE--=--value_of_DELETE_operand_on_model_CDRSC-.   
>--+------------------------------------------------------+----><
   '-,--DELETE--=--+-NO--+--------------------------------'   
                   '-YES-'

Abbreviations

Operand	Abbreviation
VARY	V
DELETE=YES	DELETE or DELETE=Y
FINAL=YES	FINAL or FINAL=Y
NO	N
RMPO=YES	RMPO or RMPO=Y
SAVESESS	S
TYPE=FORCE	F or FORCE
TYPE=GIVEBACK	G or GIVEBACK
TYPE=IMMED	I or IMMED
TYPE=REACT	R or REACT
TYPE=UNCOND	U or UNCOND
YES	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 TYPE=IMMED, code only I or IMMED. Do not code TYPE=I.

Purpose

The VARY INACT command deactivates VTAM resources. For SDLC switched and nonswitched links in a multiple-domain network, it can also return ownership of the line and its associated resources to the original SSCP without disrupting LU-LU sessions. This is done as part of error recovery procedures after one SSCP has taken over a failed SSCP's resources. For information about the deactivation of links and link stations, see the z/OS Communications Server: SNA Network Implementation Guide.

Figure 1 shows each resource type for which the command is valid and which operands can be used on the command. A large dot means that the operand applies to that resource. An I or F in the table shows what value is substituted if an IMMED, UNCOND, FORCE, or REACT operand is specified for a resource to which it does not apply.

Figure 1. Valid resource types for VARY INACT

Operands

CDLINK

Applies only to the deactivation of an NCP. It specifies whether active, leased, cross-domain links and link stations are to remain active after the NCP major node is deactivated.

This option is effective only on the VARY INACT or VARY REL command that begins the deactivation of an NCP. For example, if a second VARY INACT (perhaps with the IMMED operand specified) is entered before the first VARY INACT command completes, CDLINK does not apply to the second command and is ignored if specified.

For information about the deactivation of links and link stations, see the z/OS Communications Server: SNA Network Implementation Guide.

CDLINK=ACT: Specifies that active cross-domain links and link stations are to remain active after the NCP major node is deactivated, so that sessions routing information through the NCP over such links can continue without disruption.
CDLINK=INACT: Specifies that cross-domain links and link stations are to be deactivated as part of the NCP deactivation. Any session traffic over such links might be disrupted, depending on whether such links and link stations are also owned by some other host. See the z/OS Communications Server: SNA Network Implementation Guide for information about how shared ownership affects the results of deactivating a link or link station.

DELETE

Applies only to deactivation of cross-domain resources (CDRSCs). It specifies whether they can be deactivated and, at the same time, the RDTE storage associated with the resource released.

If you specify DELETE without including a qualifier (YES or NO), the RDTE storage associated with the resource is released when the CDRSC is deactivated. This is the same result as if you specified DELETE=YES.

DELETE=YES: Specifies that the RDTE storage associated with the resource is released when the CDRSC is deactivated. If the CDRSC exists in ISTCDRDY, DELETE=YES is not necessary.
DELETE=NO: Specifies that the RDTE storage associated with the resource is not released when the CDRSC is deactivated.
If the CDRSC exists in ISTCDRDY, DELETE=NO is not applicable. If DELETE=NO is specified, it is ignored.

FINAL

Specifies whether the physical unit specified in the ID operand will be reactivated.

FINAL=YES

Specifies that there are no immediate plans to reactivate the physical unit. The actual effects of this operand are device-dependent, and could include such functions as automatic power-off. See the appropriate component's document for the specific effects of a DACTPU type hex 01 command on a particular device. For physical units in a local SNA or switched major node, FINAL is meaningful only if the physical unit is fully active before deactivation begins.

FINAL=YES is ignored for type 2.1 physical units if ACTPU is not sent.

If you enter FINAL=YES, you cannot enter TYPE=REACT.

The FINAL= YES operand can be issued for a DLUR CDRSC. See the description of TYPE=GIVEBACK for more information.

Note: VTAM will save an internal indicator that will prevent the DLUR from opening a CPSVMGR session with VTAM. Any attempt to establish a DLUS/DLUR CPSVRMGR session will be rejected with sense code 080A000D. The operator can enable the DLUR again by issuing a VARY ACT on the DLUR CDRSC.

FINAL=NO

Specifies that there are plans to reactivate the physical unit.

ID=name

Specifies the name of any active major or minor node that is to be deactivated. 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. (See the description of the ID operand on the VARY ACT command for an example of how you can specify a network-qualified application name.)

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

Attention: Deactivating ISTLSXCF removes all dynamic PUs and TRLEs and causes VTAM to leave the XCF group.If TCP/IP is using XCF connections, those connections are also terminated.

To deactivate 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

Note:

For a gateway NCP, resources in the nonnative network are not affected by the VARY INACT command.
The PUs and LUs within a model major node cannot be individually deactivated with the VARY INACT command. After either a dynamic switched major node or a dynamic switched PU has been deactivated, it cannot be reactivated without being redefined to VTAM. The major difference between dynamically defined devices and statically defined devices is that after a dynamically defined PU is deactivated, its elements will be deleted from VTAM.
For ID=pu_name, there is no relationship between the PU and the independent LU. Deactivation of the PU ends any LU-LU sessions that are using the connection. However, the actual independent LU resource remains active because it might be in session over another adjacent link station connection.
Network addresses for the boundary function CDRSC are reclaimed from the terminated sessions if appropriate (for example, if the cross-domain resource is a switched LU), but the RDTE remains intact.
For ID=rtp_pu_name, TYPE=FORCE is required. If you specify ID=rtp_pu_name and the RTP is a route setup RTP (the COS name is RSETUP in the DISPLAY RTPS display), VARY INACT fails as a result of an invalid node type. You cannot deactivate a route setup RTP PU using the VARY INACT command.
For ID=appl_name, TYPE=FORCE is required to override persistence and terminate the application and sessions.
For a model application program, the state of the model is changed from connectable (CONCT) to inactive (INACT). This means that it can no longer be used to build dynamic application programs. Active dynamic application programs built from the model are not affected by the deactivation of the model.
For any dynamic application program built from the model, when CLOSE macro processing for the dynamic application program is complete, the definition of the dynamic application program is deleted. The dynamic application program will no longer be known to VTAM and will not appear in the output of any DISPLAY commands.
For ID=ISTCDRDY, VTAM deletes all dynamically created CDRSC RDTEs and terminates their associated sessions. CP-CP and CPSVRMGR sessions involving this host are terminated if the partner's CDRSC RDTE was dynamically defined. To avoid losing the CP-CP and CPSVRMGR sessions, you can predefine a CDRSC for the partner LU. The name on the CDRSC statement or the LU statement should be the CPNAME of the session partner. Predefining the CDRSC is suggested only if you expect to deactivate ISTCDRDY while CP-CP sessions are active. (This should be rare.) See the z/OS Communications Server: SNA Resource Definition Reference for more information about defining cross-domain resources and independent LUs.
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.
Issuing a VARY INACT command to terminate the CP-CP session with an adjacent node might cause later session establishment requests to fail. To resolve the problem, reactivate the CP-CP session or else reactivate the link with CPCP=NO so that it will no longer be used in directed search routing.
For a dependent LU requester, VTAM deactivates the CDRSC node that represents the CPSVRMGR session between the DLUR and the DLUS. If a dependent LU requester is adjacent to a dependent LU server, the CDRSC also represents the CP-CP session. For a normal deactivation, all pending and queued sessions for supported PUs and LUs fail, but deactivation does not complete until all active LU-LU sessions are terminated. A forced deactivation ends all current sessions for LUs and PUs supported by this DLUR. For a TYPE=GIVEBACK deactivation, wildcard values can be used for dlur_name. See the z/OS Communications Server: SNA Network Implementation Guide for further information about the CPSVRMGR session.
For a PU supported by a DLUR, VTAM deactivates the PU. If there are no active or pending SSCP-PU sessions using the CPSVRMGR session, the CPSVRMGR session is deactivated.

IDTYPE

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

IDTYPE is required and has no default if the resource named on the ID operand is the host CDRM. IDTYPE is optional if the resource is an adjacent CP or an external CDRM; if both an adjacent CP and an external CDRM are found, the default is IDTYPE=SSCP. If you attempt to deactivate the host CP, the command will fail.

IDTYPE=CP: Deactivates the CP with the name specified on the ID operand.
IDTYPE=SSCP: Deactivates the SSCP with the name specified on the ID operand.
IDTYPE=XCFCP: Deactivates the dynamic XCF local SNA PU representing the connection to another VTAM, when the ID operand specifies the CP name of the other VTAM.

RMPO

Applies only to NCP major nodes. RMPO specifies whether the communication controller in which the NCP is running is to be powered off automatically at the completion of the deactivation.

RMPO can be done only by an implicitly activated link station.

RMPO=YES: Powers off the communication controller automatically. The communication controller must be link-attached, and must support the remote power-off facility for this operand to be effective. Use the same link for the RMPO operation as you used earlier to load and activate the remote NCP.
RMPO=NO: Does not power off the communication controller automatically.

SAVESESS

Applies to CDRM major and minor nodes. SAVESESS specifies that active LU-LU sessions set up using the SSCP-SSCP session, which is being terminated by the VARY INACT command, remain active. Queued or pending sessions using the specified CDRM are terminated.

After you deactivate a CDRM with SAVESESS, the active sessions that remain are no longer associated with the CDRM. Therefore, subsequent activations and deactivations of the CDRM have no effect on these sessions.

The SAVESESS operand is not required during normal deactivation, and if specified, does not change the normal deactivation.

SCOPE

Specifies the scope of the deactivation.

SCOPE applies only to model applications and model CDRSCs. For other resources, this operand is ignored.

SCOPE=ALL: Specifies that all of the clone applications or clone CDRSCs created using the specified model are deactivated.
Rule: This is not a wildcard command and is not governed by the VARYWLD start option.

TYPE

Specifies the type of deactivation (other than normal deactivation). Unless IMMED, UNCOND, FORCE, REACT, or GIVEBACK is specified, normal deactivation occurs. The TYPE operand is not valid for an ADJCP major node.

During normal deactivation, queued and pending sessions fail; the VARY INACT command is queued until all active sessions are terminated.

Note: During normal deactivation of an NCP, some active sessions might be disrupted. For more information about the effects of deactivating an NCP, see the z/OS Communications Server: SNA Network Implementation Guide.

TYPE=FORCE

Means that the specified resource and applicable subordinate resources are to undergo forced deactivation. This type of deactivation might be advisable for resources that do not respond to normal or immediate (I) deactivation requests, or that are preventing completion of a VTAM HALT command. A forced deactivation instructs VTAM to deactivate its internal representations of the applicable resources and to send appropriate deactivation requests to the resources or their superior nodes, without waiting for responses to these requests. Therefore, a forced deactivation of a resource could result in a mismatch between VTAM's record of the status of a resource and the actual status of the resource in the network.

If TYPE=FORCE, sessions involving the resources are disrupted, and VTAM might have to wait (depending on how a given application program is coded) for application programs being deactivated, or for application programs in session with resources being deactivated, to formally end their sessions (that is, issue CLSDST) before completing the deactivation. A forced deactivation might cause VTAM to enter the wait state. It could then be necessary to deactivate an associated resource in order to free the system.

Forced deactivation of a local device might result in a slight wait because VTAM might have I/O outstanding for the device. VTAM cannot complete deactivation until the outstanding I/O is completed.

Note:

Normally, all sessions involving a resource that undergoes forced deactivation terminate as a result of this command, but there are exceptions. For example, if there is no CDRM-CDRM session with the owning SSCP of the session partner, or if the CDRM of a session partner is unknown because of takeover, those sessions are not terminated.
Forced deactivation of an NCP link unconditionally takes down the link, regardless of the shared ownership of the link. However, any lines under the NCP that would remain active during an automatic network shutdown (ANS) remain active after a forced deactivation of an NCP link or link station.
V INACT FORCE deletes a dynamic CDRSC independent of the CDRSCTI start option. This will cause a buffer trace to be turned off.
For ID=rtp_pu_name, TYPE=FORCE is required. If ID=rtp_pu_name and the RTP is a route setup RTP (the COS name is RSETUP in the DISPLAY RTPS display), VARY INACT will fail because of invalid node type. A route setup RTP PU cannot be deactivated using VARY INACT.
For ID=appl_name, TYPE=FORCE is required to override persistence and terminate the application and sessions.

The TYPE=FORCE operand can be specified on a VARY INACT command entered while a normal or immediate deactivation or a VTAM HALT is in progress.

TYPE=GIVEBACK

Applies to SDLC switched and nonswitched links, leased lines, switched PUs that are supported by dependent LU requesters (DLURs) that allow ANS=CONTINUE, and CDRSCs that represent DLURs. (Token ring is considered to be a switched connection.) The specified resource and applicable subordinate resources are released from this SSCP. VTAM terminates queued and pending sessions before deactivating the resource. If the specified resource was defined with ANS=CONTINUE, active LU-LU sessions remain active.

If the link does not support giveback, VTAM waits for the session to terminate before giveback is completed.

Under certain conditions, sessions returned with giveback remain displayable in the SSCP that issued the giveback. Either of the following conditions produces such results:

If the session partner is in the domain of the SSCP owning the resource before giveback
If the session is cross-network and the old owner of the resource was a gateway SSCP and was in session with the gateway NCP

Note:

Issuing this command overrides any outstanding command for the node.
If you specify GIVEBACK on this command for a switched PU that is supported by a dependent LU requester that does not support ANS=CONTINUE, the value is automatically promoted to FORCE.
VARY INACT, TYPE=GIVEBACK will be allowed when issued against a CDRSC representing a DLUR. GIVEBACK on a CDRSC will be treated similar to a REACT on other node types. You will get the following results if you issue GIVEBACK on a CDRSC:
- If the CDRSC is not a DLUR, the command will be rejected.
- If the PU supports ANS=CONTINUE, subordinate PUs and LUs will be deactivated with the GIVEBACK variation.Existing LU-LU sessions will remain active.
- When the subordinate PUs have been deactivated the sessions supporting the DLUS-DLUR pipe will be broken.
- Sessions with the DLUR which are not CPSVRMGR sessions will be left active. Examples include CP-CP, SNASVCMG, or user sessions.
- When the command completes, the DLUR CDRSC will be in an ACTIVE state.
Preventing the DLUR from coming back to this DLUS:

In some cases, the DLUR may immediately try to reconnect to the DLUS which just performed the GIVEBACK. If this is not the required result the DLUS can prevent the DLUR from opening the pipe again. This is handled by way of an additional switch on the VARY INACT. If FINAL=YES is added to the command VTAM will save an internal indicator that will prevent the DLUR from opening a CPSVMGR session with VTAM. Any attempt to establish a DLUS/DLUR CPSVRMGR session will be rejected with sense code 080A000D. The operator can enable the DLUR again by issuing a VARY ACT for the DLUR CDRSC.

TYPE=IMMED or TYPE=UNCOND

Means that the specified resource and applicable subordinate resources are to be deactivated immediately.

If TYPE=IMMED or TYPE=UNCOND, sessions involving the affected resources are disrupted. However, before completing the deactivation, VTAM waits for application programs being deactivated, or for application programs in session with resources being deactivated, to formally end their sessions (that is, issue CLSDST).

A TYPE=IMMED or TYPE=UNCOND operand can be specified on a VARY INACT command entered while a normal deactivation is in progress.

Note:

TYPE=IMMED and TYPE=UNCOND have the same function. TYPE=UNCOND is consistent with the VARY TERM command.

TYPE=REACT

Means that the specified resource and applicable subordinate resources are to undergo deactivation and subsequent reactivation. This type of deactivation and reactivation might be advisable for resources that are not responding to VTAM commands, but that the operator wants to remain active. A forced reactivation instructs VTAM to deactivate its internal representations of the applicable resources and to send appropriate deactivation requests to the resources or their superior nodes, waiting for responses before beginning reactivation. If any of the resources still do not respond, a VARY INACT command with the TYPE=FORCE operand should be entered to force deactivation of those resources.

A device contained in a dynamic switched major node cannot be deactivated with TYPE=REACT. After such a PU is deactivated, it is no longer known to VTAM and cannot be reactivated with an operator command. Dynamic LUs under a dynamic PU can be deactivated and subsequently reactivated provided that their PU is not deactivated.

Note:

Normally, sessions involving a REACT deactivated resource terminate as a result of this command, but there are exceptions. For example, if there is no CDRM-CDRM session with the owning SSCP of the session partner, or if the CDRM of a session partner is unknown because of takeover, those sessions are not terminated. These sessions also do not respond to reactivation, and are not displayed as activated in response to this command.
If this command is issued for an NCP, the SSCP-PU session between VTAM and the NCP is disrupted. VTAM does not terminate any LU-LU sessions; they might or might not be disrupted, depending on what the NCP does for automatic network shutdown (ANS). LU-LU sessions involving type 2.1 PUs generally stay up.

A second VARY INACT command with TYPE=REACT issued before the first one has time to complete has the same effect as specifying the TYPE=FORCE option.

Any type of deactivation request (normal, immediate, or forced) can be entered while a forced reactivation is in progress if you want termination of the reactivation. As previously stated, forced deactivation might be the only effective deactivation method if a resource fails to respond to the forced reactivation.
If you specify REACT on this command for a dependent LU requester, the value is automatically promoted to FORCE.