Using the default output descriptor


During BMC AMI Copy installation, installation options are installed that comprise the default output descriptor.

To dynamically allocate copy data sets in an BMC AMI Copy job, use the COPYDDN or RECOVERYDDN option in your COPY statement to name an output descriptor instead of naming a DD statement, as in the following example:


COPYDDN(DEFAULT,DEFAULT)

This example tells BMC AMI Copy to use the default output descriptor values to make the local site primary and backup copy data sets. The reserved word DEFAULT identifies that set of default output descriptor values. You cannot use DEFAULT for both COPYDDN and RECOVERYDDN when one is specified as stacked to tape and one is not.

You can mix dynamic and DD allocations, as in the following example:

RECOVERYDDN(DEFAULT,RBCOPY)

This example tells BMC AMI Copy to use the current default output descriptor values to make the remote site primary copy. It also specifies that the remote site backup copy requires a DD statement in the JCL named RBCOPY because (in this case) there is no output descriptor named RBCOPY but a DD statement for it exists in the JCL.

Warning

Important

BMC AMI Copy

 first checks to determine whether a specified name is a descriptor name; if it is not, 

BMC AMI Copy

 expects an appropriate DD statement in the JCL.

If you want to use different data set names than those in the current default output descriptor, you can use the COPYDSN, RECOVERYDSN, and DSNAME options to change them, as in the following example:

COPY TABLESPACE A.B ..... options
     COPYDDN(DEFAULT,DEFAULT)
     COPYDSN(NEWYEAR.LPCOPY,NEWYEAR.LBCOPY)
..... more options

This example tells BMC AMI Copy to use the current default output descriptor values. Then, the COPYDSN clause specifies new values for the local site primary and local site backup copy data sets.

Command-and-syntax-reference provides details about the COPYDSN, RECOVERYDSN, and DSNAME options available with the COPY and COPY IMAGECOPY commands. For more information, see Using-GDGs-and-symbolic-variables-in-data-set-names.

 

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

BMC AMI Copy for Db2 13.1