INDEPENDENT OUTSPACE

Use the INDEPENDENT (or INDEP) OUTSPACE option to redirect the output of a RECOVER BUILDINDEX run to data sets other than those that are used by Db2.

Important

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 A00 n 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).

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

The default name is identical to the Db2 name of the index space to which the indexes are normally directed but with BMCDBC substituted for DSNDBC:

vcat.BMCDBC.databaseName.indexSpaceName.p0001.znnn

The variables are defined as follows:

  • vcat is the ICF catalog name.

  • databaseName.indexSpaceName is the name of the database and index space containing the data set being rebuilt.

  • 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

Any data set name that you specify must be preceded by the MODEL keyword.

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 prior to the TABLESPACE specification in the RECOVER BUILDINDEX command statement, as shown in RECOVER BUILDINDEX syntax.

For information about using redirection with multiple BMC AMI Recover commands, see Recovering to a non-DB2 data set. For information about some applications of this feature, see Testing recovery with simulation.

MODEL

The MODEL option precedes the non Db2 data set cluster name to which you want to redirect the output from the rebuilding of the specified index. The data set name that you specify may optionally include any of the symbolic variables in Stacking copies on tape.



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

Comments