The following scenario uses XRC commands to suspend an XRC session
in preparation for applying maintenance to the SDM system.
- Start a session named TUCSON for disaster recovery with the state,
control, and journal data sets under a high-level qualifier of NEW.
Use the command:
XSTART TUCSON SESSIONTYPE(XRC) ERRORLEVEL(VOLUME) HLQ(NEW)
Note: An error on any volume suspends the volume; other volumes
continue to be copied.
- Allocate 70 MB of fixed real storage to the system data mover.
- Add a volume pair to XRC session TUCSON.
XADDPAIR TUCSON VOLUME(PRIM01,SECO01) SCSESSION(AB)
- Add another volume pair to the XRC session, specifying the error
response level as SESSION. The volume is assigned to the default storage
control session "--".
XADDPAIR TUCSON VOLUME(PRIM02,SECO02) ERRORLEVEL(SESSION)
Normal data processing continues.
- Suspend the XRC session (XSUSPEND) and apply maintenance to the
system. In time, maintenance needs to be applied to the SDM system.
The maintenance, which may include IPLing the SDM system or refreshing
SYS1.LINKLIB, is expected to take a maximum of six hours. If the maintenance
is to be applied to the SDM modules in SYS1.LINKLIB, you must cancel
the ANTAS000 address space after the refresh of SYS1.LINKLIB to have
the maintenance take effect.
XSUSPEND TUCSON TIMEOUT(06.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.
- Restart the TUCSON session for disaster recovery.
XSTART TUCSON SESSIONTYPE(XRC) ERRORLEVEL(VOLUME) HLQ(NEW)
- Allocate 70 MB of fixed real storage to the system data mover.
- Add all suspended volume pairs back to the XRC session.
XADDPAIR TUCSON SUSPENDED
All ERRORLEVEL and SCSESSION values default to what they
were prior to the suspension. XRC resynchronizes all volume pairs.