Quiescing VTAM communication
When you quiesce communication, all VTAM communication stops between a local and remote CAS after processing all pending requests for information. For example, suppose your local CAS is SYSA. You open a window, access MainView for z/OS on SYSB, and enter the WFLOW command. If communication between SYSA and SYSB is quiesced, the VTAM communication link does not end until WFLOW is displayed.
After VTAM communication quiesces, you cannot access the remote CAS until you restart communication again with the STart command; see Starting VTAM communication for more information.
Before using the QUIEsce command, you should display the DIAGSESS view to see a list of the active product and user sessions communicating with the local CAS. Based on the information shown in DIAGSESS, you can determine the potential impact of quiescing CAS communication.
After you enter the QUIEsce command, the following conditions exist:
All pending requests for information are processed.
Windows opened to the remote CAS are terminated for terminal sessions logged on through the local CAS.
Windows opened to the local CAS are terminated for terminal sessions logged on through the remote CAS.
VTAM links between the two CASs become inactive.
Windows eventually become empty and a T appears in the window status field on the window information line.
You cannot use the QUIEsce command against the local CAS, which is identified by a Yes in the Cur Sys field of the CASACT view.
The following forms of the QUIEsce command are available:
The primary command is entered on the COMMAND line as follows:
where system is the name of a remote CAS listed in the System field.
The QUI line command is entered in the line command field ( CMD) at the left of the CASACT view. VTAM communication is quiesced for the remote CAS where the command is entered.