Note: Except for channel-attached SNA devices, if this command is issued to a resource with outstanding I/O, the command will not complete and VTAM must be recycled.

1. Channel-attached physical unit or logical unit, SNA, or non-SNA:
   1. Display the resource status. If it is PHLIN, PHLAC, PDLUC, or PSUB1, the channel is hung or a required interrupt is missing.
   2. If the status is PNFYx, go to step 11.
2. Link-attached SNA logical unit, switched logical unit:
   1. Display the resource status. If it is PNFYx, go to step 11.
   2. If it is anything else, there is a VTAM problem.
3. Link-attached BSC 3270 logical unit:
   1. Display the resource status. You should see PDACL or PFDLU.
   2. Issue VARY INACT,FORCE for the NCP or CA major node that defines the device.
   3. Message IST105I indicates whether the deactivation succeeded and all lower-level nodes are inactive.
   4. If the deactivation failed, display the status of all the resources in the NCP or CA major node.
   5. If the status is PNFYx, go to step 11.
   6. If it is anything else, there could be a VTAM or NCP problem. Go to Reporting the problem to IBM.
4. Link-attached SNA physical unit, switched physical unit:
   1. Display the resource status. You should see PDISC or PFDSC.
   2. Issue VARY INACT,FORCE for either the physical unit to which the device is attached, or for the NCP or CA major node that defines the device.
   3. Message IST105I indicates whether the deactivation succeeded and all lower-level nodes are inactive.
   4. If the deactivation failed, display the status of all the resources attached to the NCP.
   5. If the status is PSUBx, go to step 10.
   6. If the status is PNFYx, go to step 11.
   7. If it is anything else, there is a VTAM problem.
5. Link-attached BSC 3270 physical unit:
   1. Display the resource status. You should see PDACP or PFDCP.
   2. Issue VARY INACT,FORCE for the NCP.
   3. Message IST105I indicates if the deactivation succeeded and all lower-level nodes are inactive.
   4. If deactivation failed, display the status of all the resources in the NCP or CA major node.
   5. If the status is PSUBx, go to step 10.
   6. If the status is PNFYx, go to step 11.
   7. If it is anything else, there is a VTAM problem.
6. Local SNA or non-SNA major node, switched major node:
   1. Display the resource status. You should see PSUBx.
   2. Issue VARY INACT,FORCE for any minor nodes that are not inactive. This should allow deactivation to be completed.
7. Link:
   1. Display the resource status. You should see PDLNK.
   2. Issue VARY INACT,FORCE for the NCP to which the link is attached. This should allow deactivation to be completed.
8. Channel-attached NCP:
   1. Display the resource status. You should see PDISC.
   2. Press the RESET LOAD button on the communication controller. This should allow deactivation to be completed.
9. Link-attached NCP:
   1. Display the resource status. You should see PSUBx.
   2. Display the status of the lower-level nodes.
   3. If the status is PNFYx, go to step 11.
   4. If the status is anything else, there is a VTAM problem.
10. PSUBx status:
    1. Display the status of the lower-level nodes to find any pending states.
    2. Deactivate any active or pending nodes. This should allow deactivation to be completed.
11. PNFYx status:
    1. For application programs with an NSEXIT exit routine:

       If the VARY INACT,FORCE command is unable to complete, there is a VTAM problem. Otherwise, deactivation should complete.

    2. For application programs with only a LOSTERM exit routine:
       1. If the application program has issued a CLSDST macroinstruction, deactivation should complete.
       2. If the application program has not issued a CLSDST macroinstruction for the logical unit, issue a second VARY INACT,FORCE for the logical unit in question. If that does not correct the problem, you might need to cancel the application program to allow the deactivation to complete. (Canceling the application program terminates all of the LU-LU sessions with the application program.)

          Coding the LOSTERM parameter on the APPL definition statement allows you to recover this type of hung resource without having to cancel the application.

    3. For application programs with neither exit:

       Deactivation does not complete until the application program issues CLSDST, the application program closes its ACB, or the operator cancels the application program.

Return to step 2 on page Wait.