COPY object options

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.

BIGDDN provides an alternative DD or output descriptor name for COPYDDN (COPYDDN) or FULLDDN (FULLDDN) under the following conditions:

• Dynamic allocation is used
• Any FULL option is specified
• The threshold specified by the OUTSIZE option has been met or exceeded

OUTSIZE, described on OUTSIZE and OUTSIZE=0, specifies the threshold at which you want the output to go to an alternate DD, such as when you want large copies to go to tape rather than DASD, or to Instant Snapshots rather than standard copies. If the value of OUTSIZE is not met or exceeded, output goes to the DD specified by COPYDDN or FULLDDN, if they are specified.

BIGDSN provides an alternative data set name for COPYDSN (COPYDSN) or FULLDSN (FULLDSN) under the following conditions:

• Dynamic allocation is used
• Any FULL option is specified
• The threshold specified by the OUTSIZE option has been met or exceeded

OUTSIZE, described on OUTSIZE and OUTSIZE=0, specifies the threshold at which you want the output to go to an alternate data set, such as when you want large copies to go to tape rather than DASD. If the value of OUTSIZE is not met or exceeded, output goes to the data set specified by COPYDSN or FULLDSN, if they are specified.

For Instant Snapshot copies, BIGDSN is the VSAM cluster name. The data component is named by the hardware implementation. The maximum length of BIGDSN for Instant Snapshots is 39 characters.

BIGRECDDN provides an alternative DD or OUTPUT descriptor name for RECOVERYDDN (RECOVERYDDN) or FULLRECDDN (FULLRECDDN) under the following conditions:

• Dynamic allocation is used
• Any FULL option is specified

• The threshold specified by the OUTSIZE option has been met or exceeded

BIGRECDSN provides an alternative data set name for RECOVERYDSN (RECOVERYDSN) or FULLRECDSN (FULLDSN) under the following conditions:

• Dynamic allocation is used
• Any FULL option is specified
• The threshold specified by the OUTSIZE option has been met or exceeded

For Instant Snapshot copies, BIGRECDSN is the VSAM cluster name. The maximum length of BIGRECDSN for Instant Snapshots is 39 characters.

The CLONE option indicates that COPY is to copy only clone table or index data. If the COPY command is processing a table space and CLONE is specified, BMC AMI Copy will only process clone table data. If the COPY command is processing an index and CLONE is specified, BMC AMI Copy will only process clone table index data.

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

Use the COPYDDN option to tell BMC AMI Copy the names of the DD statements or the dynamic allocation output descriptors for the local site primary and backup copies of the table space or index space. 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 specify both a DDName and an output descriptor in the same COPYDDN clause. If you allocate the copy data set names in the JCL, you can list up to four copies with the COPYDDN option; however, if you allocate the copy data sets dynamically, you can allocate only two copies.

Allocating data sets in the JCL

In this case, the COPYDDN option specifies the DDNames to be used in the JCL for the local site copies. The following rules apply:

• Each DDName that you specify with COPYDDN must be unique within the job step. You can optionally enclose the list of DDNames in parentheses in the COPY statement and you must separate the DDNames by commas. Spaces between DDNames are optional.

• If you do not specify COPYDDN or RECOVERYDDN, BMC AMI Copy assumes that only one copy is required and uses SYSCOPY as the DDName if it exists in the JCL.

  If you specify RECOVERYDDN without specifying COPYDDN, BMC AMI Copy uses SYSCOPY as a local primary copy if a DD statement for it exists in the JCL. If no DD statement exists, BMC AMI Copy makes only recovery site copies.

• When you do not specify the RECOVERYDDN option, you can list up to four DDNames (DDName1 through DDName4) with the COPYDDN option (one DDName per copy). When you list only one DDName, the copy is registered as a local primary copy. If you list more than one DDName, the copies are registered according to the setting of the corresponding COPYDDN n installation option. For example, if COPYDDN2=RB, the copy specified by DDName2 (the second copy) is registered as the recovery backup copy.

• When you do specify the RECOVERYDDN option, you can list up to two DDNames ( DDName1 and DDName2) with the COPYDDN option thus allowing DDName3 and DDName4 to be specified with the RECOVERYDDN option. In this case, the copy specified by DDName1 (or by the default SYSCOPY) is registered as a local primary copy. When two copies are required, the copy specified by DDName2 is registered as a local backup copy.

  If RECOVERYDDN is specified, any third and fourth data sets specified by COPYDDN are invalid.

Refer to Installation-options for more information about the COPYDDNn installation option. Also, see RECOVERYDDN.

Allocating data sets dynamically

When you dynamically allocate the copy data sets, use COPYDDN to specify the names of the output descriptors to be used to provide the local site copy data sets. The following rules apply:

• Specify DEFAULT to use the default installation options or specify an appropriate descriptor name to refer back to an OUTPUT statement. (Refer to COPY-IMAGECOPY-command for more information.)
• 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 sets named in the descriptor by using the COPYDSN option. You can optionally enclose the output descriptor list in parentheses in the COPY statement. The descriptor names in the list must be separated by commas. Spaces between names are optional. (Refer to COPYDSN for more information.)
• You can list up to two output descriptor names with COPYDDN to make two copies. When you list only one output descriptor name, the copy is registered as a local primary copy. If you list more than one output descriptor name, the copies are registered according to the setting of the corresponding COPYDDNn installation option. For example, if COPYDDN2=RB, the copy specified by the second descriptor name is registered as the recovery backup copy.

• When you specify both COPYDDN and RECOVERYDDN, you can list up to two output descriptor names with COPYDDN so allowing two more to be specified with RECOVERYDDN. In this case, the copy specified by the first output descriptor is registered as a local primary copy. When two copies are required, the copy specified by the second descriptor name is registered as a local backup copy.

  If RECOVERYDDN is specified, any third and fourth data sets specified by COPYDDN are not valid.

Refer to Installation-options for more information about the COPYDDN n installation option. Also see RECOVERYDDN.

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

• 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).

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

If you prefer, you can use the DSNAME option instead of using COPYDSN to set the values of both of the new data set names. (Refer to DSNAME.)

Use the DSNAME option when you dynamically allocate the copy data sets and want to override the default names for both the local site and recovery site copy data sets. The value for dataSetName becomes the new default data set name for all output copies. When you use DSNAME, you do not need to specify COPYDSN or RECOVERYDSN.

You can construct dataSetName using any of the symbolic variables listed under COPYDSN on COPYDSN. It is suggested that if you create more than one site type copy, you use the variable &TYPE to uniquely identify the data set name.

Typically, you use this option with wildcard specification of data sets.

Refer to COPY-IMAGECOPY-command, Using-symbolic-variables, and Stacking-copies-on-tape.

For table spaces, 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. The default is all of the partitions or data sets (DSNUM ALL).

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

Use the EXCLUDE option after a wildcard space specification to exclude one or more spaces from copying that would otherwise be copied. Thus, EXCLUDE applies only to objects specified in the COPY statement. You can use the 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 formdatabaseName.spaceName 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.

FULLDDN and FULLRECDDN provide an alternative DD or OUTPUT descriptor name for COPYDDN and RECOVERYDDN when FULL AUTO or CHANGELIMIT is used. If a full copy is selected, the FULLDDN and FULLRECDDN options are used to control the output.

FULLDDN corresponds to COPYDDN; however, FULLDDN is used only for full copies. (See the COPYDDN description on COPYDDN.)

If the copy is a full copy and FULLDDN is specified, FULLDSN is used. If FULLDDN is not specified, COPYDDN is used for the full copy.

You can use FULLDSN and FULLRECDSN without FULLDDN and FULLRECDDN. They are used to name the corresponding full copies.

FULLDSN corresponds to COPYDSN; however, FULLDSN is used only for full copies. (See the COPYDSN description on COPYDSN.)

If the copy is a full copy and FULLDSN is specified, FULLDSN is used. If FULLDSN is not specified, COPYDSN is used for the full copy.

FULLDDN and FULLRECDDN provide an alternative DD or OUTPUT descriptor name for COPYDDN and RECOVERYDDN when FULL AUTO or CHANGELIMIT is used. If a full copy is selected, the FULLDDN and FULLRECDDN options are used to control the output.

FULLRECDDN corresponds to RECOVERYDDN; however, FULLRECDDN is used only for full copies. (See RECOVERYDDN.)

If the copy is a full copy and FULLRECDDN is specified, FULLRECDSN is used. If FULLRECDDN is not specified, RECOVERYDDN is used for the full copy.

You can use FULLDSN and FULLRECDSN without FULLDDN and FULLRECDDN. They are used to name the corresponding full copies.

FULLRECDSN corresponds to RECOVERYDSN; however, FULLRECDSN is used only for full copies. (See FULLRECDSN.)

If the copy is a full copy and FULLRECDSN is specified, FULLRECDSN is used. If FULLRECDSN is not specified, RECOVERYDSN is used for the full copy.

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

Use the RECOVERYDDN option to tell BMC AMI Copy the names of the DD statements or the dynamic allocation output descriptors for the recovery site primary and backup copies of the table space or the index space. If you allocate the copy data sets in the JCL, RECOVERYDDN specifies the JCL DDNames. If you dynamically allocate the copy data sets, RECOVERYDDN specifies the appropriate output descriptor names. If you want, you can specify both a DDName and an output descriptor in a single RECOVERYDDN clause.

Refer to Allocating-output-copy-data-sets-dynamically and COPY-IMAGECOPY-command for more information about output descriptors.

Allocating data sets in the JCL

When you allocate copy data sets in the JCL, the RECOVERYDDN option specifies the DDNames to be used for making any required recovery site copies. The following rules apply:

• Each DDName you use with RECOVERYDDN must be unique within the job step. You can optionally enclose the DDName list in parentheses in the COPY statement. You must separate the DDNames in the list by commas. Spaces between DDNames are optional.
• The copy specified by DDName3 is registered as a recovery site primary copy. When two copies are required, the copy specified by DDName4 is registered as a recovery site backup copy.

Allocating data sets dynamically

When you dynamically allocate the copy data sets, use RECOVERYDDN to specify the names of the output descriptors to be used to provide the remote site copy data sets. The following rules apply:

• Specify DEFAULT to use the default installation options, or specify an appropriate descriptor name to refer back to an OUTPUT statement. (Refer to COPY-IMAGECOPY-command for more information.)
• 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 RECOVERYDSN option. You can optionally enclose the output descriptor list in parentheses in the COPY statement. You must separate the descriptor names in the list by commas. Spaces between names are optional. (Refer to RECOVERYDSN for more information.)
• The copy specified by outputDescriptor3 is registered as a recovery site primary copy. When two copies are required, the copy specified by outputDescriptor4 is registered as a recovery site backup copy.

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

• 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.

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

Refer to COPY-IMAGECOPY-command for more information.

If you prefer, you can use the DSNAME option instead of using RECOVERYDSN to set the values of both of the new data set names. (Refer to COPYDSN.)

Use the SCOPE option to reduce the object list to only those table spaces and index spaces that meet the specified criteria.

SCOPE STATUS (status1,statuss2,...)

BMC AMI Copy bypasses spaces that are not in at least one of the specified statuses.

SCOPE PENDING

SCOPE PENDING achieves the same result as using SCOPE STATUS(COPY,ICOPY). BMC AMI Copy bypasses spaces that are not in COPY or ICOPY status.

To process spaces with other statuses, use SCOPE STATUS(...).

SCOPE ALL

SCOPE ALL is the default. If you specify SCOPE ALL, BMC AMI Copy copies all specified spaces.

The TASK option allows you to specify a task number that is associated with a space controlling how the work is divided. If TASK is not specified for a space or space list, BMC AMI Copy starts the copy for a space in the next available task.

Spaces within a task are ordered:

• By appearance in the space list in the COPY command
• In alphanumeric order within wildcard expansions.

Select the value of integer based on this ordering.

Parsing and some initialization and termination functions are performed by the main task. Each subtask may perform other initialization and termination functions. The subtask also performs the actual copy of the space. Each subtask creates a thread to Db2. If one task ends abnormally (abends) or ends with a return code greater than 4, no new tasks will be started. BMC AMI Copy will then terminate as soon as any other outstanding subtasks complete. If the main task encounters an error condition, BMC AMI Copy immediately terminates, thus terminating all subtasks.

If MAXTASKS is greater than 1, and TASK is not specified, spaces will be copied by the first available subtask.

For more information about the interaction between TASK and MAXTASKS, see Using-Multitasking.