Use the XSUSPEND TSO command to either suspend an XRC session or to suspend one or more volume pairs from the XRC session. In a coupled environment, you may either suspend all XRC sessions coupled to the master session or suspend all volume pairs from sessions that are coupled to the master session.
When an XRC session is suspended, the system data mover is no longer active and the volume pairs are in suspended state. Session suspension should occur as part of a planned outage when you stop applications or intend the outage to be brief. Suspending an XRC session cancels all pending volume commands; you must reissue pending commands when you restart the session.
The system data mover remains active when a volume pair is in suspended state. If a storage control supports a hardware bitmap, the SDM does not read record updates from it. If a storage control does not support a hardware bitmap, the SDM continues to read record updates from the primary storage control that owns the suspended volume. A volume-level suspension does not affect application activity.
After you issue the XSUSPEND command, XRC prompts you (unless you have specified NOVERIFY) to confirm the request to suspend the session or set of specified volumes. If the XSUSPEND command is invoked through a CLIST written in REXX, you should either specify NOVERIFY or place your response to the prompt in the data stack prior to issuing the command. In a batch environment, you can stack the response.
For additional information about suspending coupled sessions, refer to XSUSPEND in a coupled environment.