Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Recover for Db2 13.1.

OUTCOPY specification for IMPORT


This topic contains option descriptions for the OUTCOPYDDN and RECOVERYDDN specifications which are included in the OUTCOPY specification.

The syntax diagram for the OUTCOPY specification is in IMPORT syntax.

Option

Description

OUTCOPY

You can specify OUTCOPY to make copies of the object or object data set being imported. For each object or data set that you process, you can request up to four image copies. The default is no copies. If you are migrating to the real Db2 data sets and you request image copies, you can choose which copies, if any, to register in the SYSIBM.SYSCOPY table. However, if you are using the INDEPENDENT OUTSPACE option to import to non Db2 data sets and you request image copies, you cannot register those copies.

Output copies are produced in the SYSTEMPAGES YES format when possible.

If the output copies that you want to make are allocated in the JCL, the OUTCOPYDDN and RECOVERYDDN options specify the DD names for those data sets. If the output copies are dynamically allocated, the OUTCOPYDDN and RECOVERYDDN options refer to the appropriate OUTPUT descriptor names. For more information, see OUTCOPYDDN-specification and RECOVERYDDN-specification. The copies that you want to register are specified by the REGISTER option (OUTCOPY-specification).

When you create an OUTCOPY and want to force the copy to the cylinder-managed space of an extended address volume (EAV), specify the SPACE keyword (OUTCOPY-specification).

Important

You can use BMC AMI Recover to automatically size the OUTCOPY files generated by BMC AMI Recover. For more information, see Automatic-sizing-of-output-copies-dynamically-allocated-on-DASD.

How the copies are made depends on whether the object is partitioned or nonpartitioned.

  • If the object is partitioned, and OUTCOPY BYPART is specified or a specific DSNUM is coded in the object specification, a separate output copy is made for each partition. If you specified OUTCOPY ASCODED and DSNUM ALL with the RECOVER command, a single output copy is made for the object as a whole.

    For more information about using OPTIONS OUTCOPY BYPART, see OUTCOPY.

  • If the object is nonpartitioned and you are importing multiple data sets by specifying DSNUM ALL, each output copy is for all of the data sets. If you are importing multiple data sets by specifying each one individually with DSNUM integer, a separate output copy is made for each data set.

OUTCOPY NO

OUTCOPY NO is the default and specifies that no output copies are required.

OUTCOPY YES

OUTCOPY YES specifies that you want image copies or DSN1COPY-type copies of the table space being imported. You can make up to four image copies or up to four DSN1COPY-type copies. A DD statement or an OUTPUT command statement must exist for each copy. The ddnames for the copy DD statements are specified by the OUTCOPYDDN and RECOVERYDDN options.

Important

You cannot use the OUTCOPY YES option to produce Instant Snapshot copies.

OUTCOPYDDN specification

The syntax diagram for the OUTCOPYDDN specification is in RECOVER-TABLESPACE-RECOVER-INDEX-and-RECOVER-INDEXSPACE-syntax.

RECOVERYDDN specification

The syntax diagram for the RECOVERYDDN specification is in RECOVER-TABLESPACE-RECOVER-INDEX-and-RECOVER-INDEXSPACE-syntax.


Related topic


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*