Example: suspending and resynchronizing a session

The following scenario describes XRC commands that are used for suspending and resynchronizing the XRC session to allow you to change to another virtual server or processor.

Start a session named TUCSON for disaster recovery, using the following command:
```
XSTART TUCSON SESSIONTYPE(XRC) ERRORLEVEL(SESSION)
```
Note: An error on any volume will cause the XRC session and all volumes in the session to be suspended. All volumes must be resynchronized. The state, control, and journal data sets are under a high-level qualifier of SYS1.
Add the volume pair to the XRC session.
```
XADDPAIR TUCSON VOLUME(PRIM01,SECO01)
```
The volume inherits session-level recovery from the XSTART command. (Normal data processing continues.)
Suspend the XRC session, and make the planned system changes.
```
XSUSPEND TUCSON TIMEOUT(03.30.00)
```
The timeout duration of three hours and 30 minutes means that you plan to restart this session by an XSTART command before this timeout duration has passed.

During the suspension, storage controls that support hardware bitmapping record application updates in their hardware bitmaps. Storage controls that do not support hardware bitmapping do not record application updates. Instead, updates accumulate in cache until the XSTART command function is complete.
Restart the XRC session on the new system.
```
XSTART TUCSON SESSIONTYPE(XRC) ERRORLEVEL(SESSION)
```
The state, control, and journal data sets are under a high-level qualifier of SYS1.
Add back to the session all pairs that are in suspended state at the time that you initially issued the XADDPAIR command. Issue the following command:
```
XADDPAIR TUCSON SUSPENDED
```
XRC starts volume synchronization processing, subject to the SYNCH and SCSYNCH values.