Note: Recovery Expert for z/OS supports the recovery of partitioned and non-partitioned table spaces, table space partitions, tables, and aggregate objects such as databases, storage groups, plans, packages, DB2 Grouper groups, and DB2 Automation Tool object profiles. It currently does not support indexes as objects of recovery in the Recovery Expert for z/OS GUI client. 2.3 Recovering objects to current The triggering event for recovering an object or set of objects to current is typically media failure, such as an input/output (I/O) error or volume failure. Typically, when a single object such as a table space is recovered to current, its dependent objects such as indexes or other table spaces in the same referential set are not recovered because they are considered to be unaffected by the error. Attention: Recovery Expert for z/OS assumes that all dependent objects such as other table spaces in the referential set, and all indexes a have to be recovered as well, and therefore generates appropriate control statements to do so. It also automatically generates CHECK DATA control statements for table spaces that are part of a referential set. If you think that this additional level of protection is not required in your organization, you can modify the generated recovery plans at your own risk. a. Indexes are rebuilt using the REBUILD INDEX statement. As far as possible, we have used a common timeline showing a sequence of events in all the scenarios. These events are not the most optimal of operations, and have been selected to demonstrate the recovery semantics of Recovery Expert for z/OS.