Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
![]() Manual recovery z/OS DFSMSrmm Implementation and Customization Guide SC23-6874-00 |
|
When manual recovery is required, each subsystem request that results in I/O to the control data set fails. For requests that can be retried, DFSMSrmm issues WTOR EDG4001D or EDG8008D. When you perform manual recovery because the control data set is no longer valid, restore the control data set using the most recent backup copy of the control data set. Forward recover the control data set to the point of failure by using the latest control data set backup and the applicable journal backups that are concatenated with the active journal. See Restoring the control data set with forward recovery for information. If manual recovery is required because the control data set is full or for some other reason where the control data set information is valid except for the most recent failed record updates, use the current control data set for recovery rather than a backup copy. When you use the current control data set for recovery, you do not need to perform forward recovery because DFSMSrmm restart performs automatic forward recovery. Also do not run the EDGUTIL utility against the control data set before you resume DFSMSrmm operation. Use one of these methods to perform manual recovery by using the
current control data set.
Manual recovery requires operator intervention. See z/OS DFSMSrmm Managing and Using Removable Media
for operator procedures for information about stopping, quiescing,
and restarting the DFSMSrmm subsystem. After manual recovery completes,
the operator can reply 'RETRY' or 'CANCEL' to the EDG4001D and EDG8008D
WTORs. These requests fail and must be rerun or reissued after manual
recovery:
![]() ![]() ![]() |
![]() |