Registering copies
How BMC AMI Copy registers copies when you use the COPY command or COPY IMAGECOPY command depends on which version of Db2 is installed.
You can register up to four copies for use during recovery. Each copy is registered with the same RBA or LRSN and is additionally registered as either the primary or backup copy, depending on whether it is specified first or second in the COPYDDN or RECOVERYDDN options. Copies specified in the COPYDDN option are registered as local copies; those specified in the RECOVERYDDN option are registered as recovery site copies.
If you specify FULLDDN or FULLRECDDN with FULL NO, FULL AUTO, or CHANGELIMIT and full copies are made, FULLDDN and FULLRECDDN are used in the same manner as COPYDDN and RECOVERYDDN.
If you specify BIGDDN or BIGRECDDN with any FULL option when dynamic allocation is used and you have also specified a value other than the default for the OUTSIZE installation option (OUTSIZE=0) and that value is met or exceeded, BIGDDN and BIGRECDDN are used in the same manner as COPYDDN and RECOVERYDDN.
However, if multiple values of COPYDDN are specified and RECOVERYDDN is not specified, the types of copy are determined by the COPYDDN n installation options (0). COPYDDN1 specifies the type for the first data set indicated with COPYDDN; COPYDDN2 specifies the type for the second data set indicated, and so on. For more information, see COPY-object-options and Installation-options.
You can register a copy as primary or backup. However, you cannot register a copy as a backup unless you also register a primary copy for the same site type (local or recovery).
When more than one copy is registered, BMC AMI Copy registers them in the order that the data sets are indicated in the COPYDDN and RECOVERYDDN options.