Working with multi-data-set, nonpartitioned table spaces

However, additional restrictions apply:

• A recovery or a change accumulation for a table space that is defined with DSNUM ALL will not use as input any change accumulation file that is defined with DSNUM n.

• If you run BMC AMI Recover and specify DSNUM ALL, you cannot (in the same run) specify ACCUM GROUP for a group in which a specific data set (DSNUM n) of the same table space is defined. You cannot run BMC AMI Recover for DSNUM n with change accumulation for DSNUM ALL.

• When you are processing nonpartitioned multi-data-set table spaces, you cannot perform a DSNUM ALL recover and an ACCUM DSNUM n on the same table space in the same step, or vice versa. Also, you cannot perform an ACCUM where you specified a nonpartitioned multi-data-set table space as DSNUM ALL and DSNUM n.

• The INDEXES YES option is not available when R+/CHANGE ACCUM processes a group that includes a DSNUM n specification.

The following example statements are invalid. (Not all invalid combinations are shown.) In these examples, GRP1 includes table space A.B DSNUM ALL, and GRP2 includes table space A.B DSNUM 1 and 2.

RECOVER TABLESPACE A.B DSNUM ALL 
ACCUM GROUP GRP2 

RECOVER TABLESPACE A.B DSNUM 1 
ACCUM GROUP GRP1 

ACCUM GROUP GRP1 
ACCUM GROUP GRP2 

ACCUM TABLESPACE A.B DSNUM ALL 
ACCUM TABLESPACE A.B DSNUM 1 

RECOVER TABLESPACE A.B DSNUM 1
ACCUM TABLESPACE A.B DSNUM ALL

ACCUM TABLESPACE A.B DSNUM 1 INDEXES YES

When R+/CHANGE ACCUM encounters these invalid statements, you receive message BMC40185 or BMC40545, and the job step ends with reason code 8.