COPY IMAGECOPY syntax options

APPLICATION creatorName can be used to specify the object for COPY IMAGECOPY. When this type of object is specified with a creator name of SAPR3, all table spaces that have CREATOR=SAPR3 are copied. If INDEXES YES is specified, the indexes for the selected table spaces are also copied.

APPLICATION can be mixed with TABLESPACE and INDEXSPACE specifications within the same COPY IMAGECOPY command.

The ATLOGPOINT option provides BMC AMI Copy with a start RBA value of the image copy you want to duplicate. The LRSN of the copy must be registered in the SYSIBM.SYSCOPY table or BMCXCOPY. The default is the most recent primary image copy registered.

The ATRBA option provides BMC AMI Copy with the start RBA value of the image copy you want to duplicate. The RBA of the copy must be registered in the SYSIBM.SYSCOPY table or BMCXCOPY. The default is the most recent primary image copy registered.

The AUX option allows BMC AMI Copy to include auxiliary objects, history objects, and archive tables in the copy without having to explicitly specify these objects.

For a description of the AUX option and its parameters, see AUX.

The CHECKERROR integer option allows you to override the CHECKERR installation option that controls the severity of page checking errors. The value of integer is any integral number between 0 and 254 and is used by BMC AMI Copy as a condition code. A condition code of 4 or less allows execution to continue in the event of a page checking error; a code greater than 4 causes BMC AMI Copy to terminate at the point of the error.

The CHECKTSLEVEL option identifies any damaged pages found during the copy process and ensures that all target pages have correct internal formats and can be used for table space recovery. CHECKTSLEVEL allows you to select the level and frequency of checking for a target table space. Page checking in this way provides better use of computer resources because the integrity checks are performed when copies are made, instead of during a separate pass using a stand-alone utility. This option does not check data content. Refer to CHECKLVL=0 for information about performance considerations.

If a problem occurs, BMC AMI Copy issues a warning message (BMC474xx) specifying the nature of the problem and, if applicable, the page number. The job completes with a condition code based on CHECKERROR or, if CHECKERROR is not specified, based on CHECKERR. For more information about BMC474xx messages, see to BMC-Common-Db2-repository.

If you do not specify CHECKTSLEVEL, the level of checking performed by BMC AMI Copy is determined by the current value of the CHECKLVL installation option as follows:

• If CHECKLVL=0, the level of checking performed is the same as for CHECKTSLEVEL 0. CHECKLVL=0 is the installation option default.
• If CHECKLVL=1, the level of checking performed is the same as for CHECKTSLEVEL 1.
• If CHECKLVL=2, the level of checking performed is the same as for CHECKTSLEVEL 2.

The CLONE option indicates that COPY IMAGECOPY is to process only image copies that are for clone tables or indexes on clone tables.

The base table space and its clone can not be processed in the same BMC AMI Copy command.

The COMPRESS option allows you to override the COMPRESS installation option that tells BMC AMI Copy whether to compress disk image copies. This option provides synergy with the BMC PACLOG utility by using the BMC Extended Compression Architecture (XCA) technology. The compressed disk image copies can be used by the IBM Db2 RECOVER and DSN1COPY utilities and the BMC AMI Recover and UNLOAD PLUS utilities. This option can also be set with the OPTIONS command (see OPTIONS-command). Also, see  and SQUEEZE for further compression information.

To enable compression, the PACLOG load library must be in the BMC AMI Copy STEPLIB or JOBLIB. For more details, see the PACLOG for DB2 documentation.

If you do not specify COMPRESS in the COPY IMAGECOPY command, BMC AMI Copy uses the value of the COMPRESS installation option as the default.

Use the COPYDDN option to tell BMC AMI Copy what additional local site copies of the space or partition should be made and where the corresponding data set names can be found.

If you allocate the copy data sets in the JCL, COPYDDN specifies the JCL data set definition names (DDNames). If you dynamically allocate the copy data sets, COPYDDN specifies the appropriate output descriptor names. If you want, you can name both a DDName and an output descriptor in the same COPYDDN clause.

When you allocate copy data sets in the JCL, the COPYDDN option specifies the DDNames (DDName1, DDName2) to be used for making any required local site copies. Each DDName must be unique within the job step.

When you dynamically allocate the copy data sets, the COPYDDN option specifies the names of the output descriptors you want to use to provide the copy data sets. You can use the same output descriptor for both copies if you are not stacking copies to tape. When you stack both copies to tape, you must use a different output descriptor for each type of copy. (Refer to Stacking-copies-on-tape and Using-multitasking-with-tape-stacking-or-cabinet-copies for more information.)

You can override the default data set names named in the descriptor by using the DSNAME option or the COPYDSN option. Refer to COPY IMAGECOPY syntax options#DSNAME dataSetName and COPYDSN .

Proceed as follows to specify either one or two copies using COPYDDN:

• Specify either COPYDDN(DDName1) or COPYDDN(outputDescriptor) to make a local site primary copy. This is valid only at a site where no local site primary copy is registered, except in the condition explained in the note below. Also, a remote primary copy must be registered already in SYSIBM.SYSCOPY or BMCXCOPY with the same RBA or LRSN values given with the ATRBA option or the ATLOGPOINT option, respectively.

  If neither a DDName nor an output descriptor is specified, no local primary copy is made. No default exists.

• Specify either COPYDDN(, DDName2) or COPYDDN(, outputDescriptor) to make a local site backup copy. A local site primary copy must be registered already in SYSIBM.SYSCOPY or BMCXCOPY with the same RBA or LRSN values given with the ATRBA option or the ATLOGPOINT option, respectively. Also, no local site backup copy must be registered already, except in the condition explained in the note below.
• Specify either COPYDDN(DDName1, DDName2) or COPYDDN(outputDescriptor, outputDescriptor) to make both local site primary and backup copies. Neither copy must be registered already in SYSIBM.SYSCOPY or BMCXCOPY, except in the condition explained in the note below. However, a remote site primary copy must be registered already with the same RBA or LRSN values given with the ATRBA option or the ATLOGPOINT option, respectively.

Use the COPYDSN option when you dynamically allocate the copy data sets and want to override the default copy data set names for the local site primary copy and/or the local site backup copy. COPYDSN is only valid after you have specified a copy data set output descriptor with COPYDDN.

Proceed as follows:

• To override only the local primary name, specify COPYDSN(dataSetName1).
• To override only the local backup name, specify COPYDSN(, dataSetName2).
• To override both, specify COPYDSN(dataSetName1, dataSetName2).

dataSetName1 and dataSetName2 are the new data set names. You can construct them using the symbolic variables described in Using-symbolic-variables.

For table space backup, the DSNUM option identifies either a single partition or data set in the table space named in the TABLESPACE option, or all of the partitions or data sets contained in that table space.

For index backup, BMC AMI Copy uses the value of DSNUM along with the setting of the IXDSNUM installation option to determine how index copies are handled. See IXDSNUM=ALL for details. You can override the IXDSNUM installation option at runtime by specifying IXDSNUM on the OPTIONS statement (see IXDSNUM).

For Instant Snapshot copies, see DSNUM-and-Instant-Snapshots.

For FlashCopies, see the information in DSNUM DATASET.

Use the EXCLUDE option after a wildcard space specification to exclude one or more spaces from copying that would otherwise be copied. You can use wildcards % and * or specific names to specify the exclusions.

The excluded spaces must be in the form of a list following the EXCLUDE keyword. Each item in the list must be in the form databaseName.s paceName and you must separate the individual items by commas. Optionally, you can enclose the list in parentheses. Excluding-specified-spaces-from-a-wildcard-specification provides more information.

The INDEXES option allows you to specify that you want BMC AMI Copy to make copies of the index copies associated with the table space copies given by the TABLESPACE option of the COPY IMAGECOPY command. The default is INDEXES NO indicating that no copies of the index copies are to be made.

Use the INDEX option to specify the indexes for which you want to make additional copies. The index specification is a list that can contain both explicit index names and wildcard patterns with the individual items in the list separated by commas. When you use a wildcard specification, you can also use the EXCLUDE option to specify any indexes you want to exclude from the copy. Also, when you use multiple index names in a single list, whether explicitly or by wildcard, you must use dynamic allocation.

Each explicit index in the list must be in the form creatorID.indexName where:

• creatorID is the 8-character creator of the index. If you do not provide a creator ID, BMC AMI Copy uses the default, DSNDB04.
• indexName is the 18-character name of the index to be copied.

You can enclose creatorID.indexName in double quotation marks or single quotation marks. This allows use of special characters, such as $, #, or /, in your object names.

When you use a wildcard pattern to specify multiple indexes, you can include the wildcard characters * (asterisk) and % (percent) to provide matching on one or more characters. Using-wildcard-characters-in-the-object-name-specification tells you how wildcards are used and how BMC AMI Copy orders the results of wildcard expansions.

Use INDEX OBJECTSET to specify the indexes that are included in a BMC AMI Recovery Manager object set for which you want to make additional copies. The BMC AMI Recovery Manager object set is identified by objectSetName. BMC AMI Copy expands the indexes for the objectSetName  into the appropriate index names and copies them.

objectSetName can have zero to any number of dot (.) separators.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager object sets, see the BMC AMI Recovery Manager for Db2 documentation .

Use INDEXSPACE OBJECTSET objectSetName to specify the index spaces that are included in a BMC AMI Recovery Manager object set for which you want to make additional copies. The BMC AMI Recovery Manager object set is identified by objectSetName. Each original must be an existing registered local site primary copy or a registered recovery site primary copy. If the allocation of the primary copy fails, BMC AMI Copy will attempt to use the backup copy as input if it exists.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager object sets, see the BMC AMI Recovery Manager for Db2 documentation .

Use OBJECTSET objectSetName to specify the table spaces and index spaces that are included in a BMC AMI Recovery Manager object set for which you want to make additional copies. The BMC AMI Recovery Manager object set identified by objectSetName.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager object sets, see the BMC AMI Recovery Manager for Db2 documentation.

The ON ERROR ICEXISTS option allows you to specify what action BMC AMI Copy is to take for COPY IMAGECOPY when the image copy to be created already exists or a valid source copy does not exist.

The ON ERROR NOTSUPPORTED option allows you to specify what action BMC AMI Copy is to take if a space or partition is an unsupported type in BMC AMI Copy. The following table lists the types not supported by BMC AMI Copy and the error messages that BMC AMI Copy issues:

Use the RECOVERYDDN option to tell BMC AMI Copy what additional recovery site copies of the space or partition should be made and where the corresponding data set names can be found.

If you allocate the copy data sets in the JCL, RECOVERYDDN specifies the JCL data set definition names (DDNames). If you dynamically allocate the copy data sets, RECOVERYDDN specifies the appropriate output descriptor names. If you want, you can name both a DDName and an output descriptor in the same RECOVERYDDN clause.

When you allocate copy data sets in the JCL, the RECOVERYDDN option specifies the DDNames (DDName3, DDName4) to be used for making recovery site copies. Each DDName must be unique within the job step.

When you dynamically allocate the copy data sets, the RECOVERYDDN option specifies the names of the output descriptors that you want to use to provide the copy data sets. You can use the same output descriptor for both copies if you are not stacking copies to tape. When you stack both copies to tape you must use a different output descriptor for each type of copy. (Refer to Stacking-copies-on-tape and Using-multitasking-with-tape-stacking-or-cabinet-copies for more information.)

You can override the default data set names named in the descriptor by using the DSNAME option or the RECOVERYDSN option. You can override other descriptor default parameters by using an OUTPUT statement. Refer to DSNAME dataSetName and RECOVERYDSN.

Proceed as follows to specify either one or two copies using RECOVERYDDN:

• Specify either RECOVERYDDN(DDName3) or RECOVERYDDN(outputDescriptor) to make a recovery site primary copy. This is valid only at a site where no recovery site primary copy is already registered, except in the condition explained in the note below. There must be a local primary copy already registered in SYSIBM.SYSCOPY or BMCXCOPY with the same RBA or LRSN values given with the ATRBA option or the ATLOGPOINT option, respectively.

  If you specify neither a DDName nor an output descriptor, no recovery site primary copy is made.

• Specify either RECOVERYDDN(, DDname4) or RECOVERYDDN(, outputDescriptor) to make a recovery site backup copy. This is valid only when a recovery site primary copy is already registered in SYSIBM.SYSCOPY or BMCXCOPY with the same RBA or LRSN values given with the ATRBA option or the ATLOGPOINT option, respectively. Also, no recovery site backup copy should be already registered, except in the condition explained in the note below.
• Specify either RECOVERYDDN(DDName3, DDName4) or RECOVERYDDN(outputDescriptor, outputDescriptor) to make both recovery site primary and backup copies. Neither copy can be registered already in SYSIBM.SYSCOPY or BMCXCOPY, except in the condition explained in the note below. However, a local site primary copy must be registered already with the same RBA or LRSN values given with the ATRBA option or the ATLOGPOINT option, respectively.

Copies you make using COPY IMAGECOPY are automatically registered in SYSIBM.SYSCOPY or BMCXCOPY.

Use the RECOVERYDSN option when you dynamically allocate the copy data sets and want to override the default copy data set names for the recovery site primary copy and/or the recovery site backup copy. RECOVERYDSN is valid only after you have specified a copy data set output descriptor with RECOVERYDDN.

Proceed as follows:

• Specify RECOVERYDSN(dataSetName3) to override only the recovery primary name.
• Specify RECOVERYDSN(, dataSetName4) to override only the recovery backup name.
• Specify RECOVERYDSN(dataSetName3, dataSetName4) to override both.

dataSetName3 and dataSetName4 are the new data set names. You can construct them using any of the symbolic variables listed under COPYDSN .

RMGROUP can be used in place of TABLESPACE in any COPY IMAGECOPY command. Use RMGROUP to specify the table spaces that are included in a BMC AMI Recovery Manager object set for which you want to make additional copies.

RMGROUP is followed by the two-part BMC AMI Recovery Manager creator.objectSetName. A maximum of 8 characters can be used for creator, while objectSetName can be a maximum of 18 characters. creator follows the rules for short SQL identifiers. objectSetName follows the rules for long SQL identifiers. Each part, creator and objectSetName, can be delimited by double or single quotation marks. The symbols $, #, and @ are valid and can be used as the first character for creator.

BMC AMI Copy does not allow wildcards to be specified with RMGROUP and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager object sets, see the BMC AMI Recovery Manager for Db2 documentation .

Use RMGROUPIX to specify the index spaces that are included in a BMC AMI Recovery Manager object set for which you want additional copies. BMC AMI Copy expands the indexes for the creator.groupName into the appropriate index space names and makes the copy.

RMGROUPIX is followed by the two-part BMC AMI Recovery Manager creator.objectSetName. A maximum of 8 characters can be used for creator, while objectSetName can be a maximum of 18 characters. creator follows the rules for short SQL identifiers. objectSetName follows the rules for long SQL identifiers. Each part, creator and objectSetName, can be delimited by double or single quotation marks. The symbols $, #, and @ are valid and can be used as the first character for creator.

BMC AMI Copy does not allow wildcards to be specified with RMGROUPIX and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager object sets, see the BMC AMI Recovery Manager for Db2 documentation.

The SQUEEZE option specifies to BMC AMI Copy whether to consolidate the rows on a table space page so that all of the free space on the page is contiguous. This consolidation enables more effective data compression (whether accomplished by software or by hardware) by decreasing the media space required for copy data sets. Row-consolidation-SQUEEZE provides more information about media space savings; also, see COMPRESS for other information about compressing copy data sets.

If you do not specify SQUEEZE, BMC AMI Copy uses the value of the SQUEEZE installation option as the default.

Use the TABLESPACE or INDEXSPACE option to specify the spaces for which you want to make additional copies. Each original must be an existing registered local site primary copy or a registered recovery site primary copy. If the allocation of the primary copy fails, BMC AMI Copy will attempt to use the backup copy as input if it exists.

The space specification is a list that can contain both explicit space names and wildcard patterns with the individual items in the list separated by commas. When you use a wildcard specification, you can also use the EXCLUDE option to specify any spaces you want to exclude from the copy.

When you use multiple space names in a single list, whether explicitly or by wildcard, you must use dynamic allocation.

Each explicit space name in the space list must be in the form databaseName.spaceName where:

• databaseName is the name of the database containing the space. If you do not provide a database name, BMC AMI Copy uses the default DSNDB04.
• spaceName is the name of the space containing the partitions or data sets for which the additional copies will be made.

You can enclosedatabaseName.spaceName in double quotation marks or single quotation marks. This allows use of special characters, such as $, #, or /, in your object names.

When you use a wildcard pattern to specify multiple spaces, you can include the wildcard characters * (asterisk) and % (percent) to provide matching on one or more characters. Using-wildcard-characters-in-the-object-name-specification tells you how wildcards are used and how BMC AMI Copy orders the results of wildcard expansions.

You can also use the DB2CATALOG wildcard to specify the copying of image copies of Db2 catalog and directory spaces.

Use TABLESPACE OBJECTSET objectSetName to specify the table spaces that are included in a BMC AMI Recovery Manager object set for which you want to make additional copies. The BMC AMI Recovery Manager object set is identified by objectSetName. Each original must be an existing registered local site primary copy or a registered recovery site primary copy. If the allocation of the primary copy fails, BMC AMI Copy will attempt to use the backup copy as input if it exists. objectSetName identifies the BMC AMI Recovery Manager object set that contains the table spaces.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager object sets, see the BMC AMI Recovery Manager for Db2 documentation .