Space announcement


This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.


Use the INDEPENDENT (or INDEP) OUTSPACE option to redirect the output of the recovery to a data set that is not used by Db2.

The syntax diagram for the INDEPENDENT OUTSPACE specification is in RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE syntax.


INDEP OUTSPACE recoveries do not require you to stop the spaces that are being recovered, and they do not interfere with production processing. INDEP OUTSPACE enables you to do the following things:

  • Test a recovery process without taking spaces offline

  • Migrate data to another Db2 system

  • Recover an image to another data set while allowing access to data that is experiencing intermittent errors

For Db2 objects that have multiple underlying VSAM data sets, the following rules apply:

  • If the object being recovered is specified by using DSNUM ALL (either explicitly or by default), the output of the recovery is redirected to multiple independent data sets.

  • If only a single data set or partition of an object is being recovered (by using DSNUM integer), the output of the recovery is redirected to a single independent data set.

You can specify the name of each independent data set or you can accept the BMC AMI Recover model as a default.


BMC AMI Recover requires consistent use of the INDEP OUTSPACE option across all commands; if you use INDEP OUTSPACE with one command, you must use it with all other commands that support it. If you use INDEP OUTSPACE but subsequently omit it from another command that supports it, BMC AMI Recover issues an error message.

You can preallocate the INDEP OUTSPACE data sets using the following guidelines:

  • For VCAT-defined spaces, ensure that the volumes or space allocated is large enough to hold the data set.

  • If the source space is defined using a STOGROUP, and if primary and secondary quantities are not defined for the source space, BMC AMI Recover uses a sliding-scale calculation for secondary extents, similar to the method Db2 uses.

For more information, see Primary space allocation and Secondary extents.

You can allow BMC AMI Recover to dynamically allocate the INDEP OUTSPACE data sets for STOGROUP-defined spaces. If the INDEP OUTSPACE data set does not exist, BMC AMI Recover uses the attributes of the source space to dynamically allocate the target INDEP OUTSPACE data set. If the INDEP OUTSPACE data set exists, BMC AMI Recover uses it as is (no DELETE or DEFINE executed).

BMC AMI Recover includes support for multi-data-set spaces. For example, BMC AMI Recover will dynamically allocate A002, A003, to A00n INDEP OUTSPACE data sets as needed.

To have BMC AMI Recover dynamically allocate the INDEP OUTSPACE data set on a specific volume or volumes, pass a volume list by using the STOGROUP...USEORDER specification in the OPTIONS statement (see STOGROUP specification description). BMC AMI Recover statements that use STOGROUP... USEORDER are shown in the following example:


The default model name is identical to the Db2 name of the object being recovered, but with BMCDBC substituted for DSNDBC in the CLUSTER portion of the VSAM data set:


The variables are defined as follows:

  • vcat is the ICF catalog name.

  • databaseName.objectName is the name of the database and object containing the data set being recovered.

  • p corresponds to the value that is used by Db2 for this node.

  • znnn is the data set number.

    z represents the letter A, B, C, D, or E. These letters correspond to the first digit--0, 1, 2, 3, or 4--of the partition number. nnn represents the rest of the partition number. znnn represents the partitions numbers as follows:

    • A001 through A999 for partitions 1 through 999

    • B000 through B999 for partitions 1000 through 1999

    • C000 through C999 for partitions 2000 through 2999

    • D000 through D999 for partitions 3000 through 3999

    • E000 through E096 for partitions 4000 through 4096

When you want to specify a name of your own choosing, use the MODEL option to specify the name of the CLUSTER portion of the VSAM data set that you want to use. The data set name that you specify may include any of the symbolic variables that are listed in the description of the MODEL keyword in the following section.

When you use INDEP OUTSPACE, you must specify it after the object specification, as shown in the syntax diagram in RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE syntax. Also, see Testing recovery with simulation and Examples of BMC AMI Recover jobs for information about applications of this feature.


The MODEL option specifies the non Db2 data set cluster name to which you want to redirect the output from the recovery of the specified object.

The data set name that you specify can optionally include the symbolic variables Using symbolic variables.


the INDEP INTABLESPACE option specifies that the indexes to be rebuilt are to be extracted from a data set other than the table space data set that is used by Db2.

When this option is specified on a RECOVER TABLESPACE command, it must follow the INDEP OUTSPACE syntax, and the independent intablespace data set name is automatically set to the INDEP OUTSPACE data set name.

Was this page helpful? Yes No Submitting... Thank you