Changing XSUSPEND TIMEOUT intervals

The following scenario shows how to change a previously specified timeout interval. It may be that the planned outage is taking longer than you thought it would, or that it is causing unanticipated production impact. You have decided to suspend the XRC sessions.

Suspend the session named TUCSON. The planned outage is expected to be completed within 12 hours.
```
XSUSPEND TUCSON TIMEOUT(12.00.00)
```
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.

(Normal data processing continues.) However, after about ten hours you realize that the timeout interval is not long enough.
Restart the session named TUCSON, causing the SDM to start recording changes to volumes in the session.
```
XSTART TUCSON SESSIONTYPE(XRC) ERRORLEVEL(VOLUME)
```
Issue the following command to start a new timeout period of five hours:
```
XSUSPEND TUCSON TIMEOUT(05.00.00)
```
The XRC session remains suspended for up to five hours, which is plenty of time to complete the planned work.

Note: 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.