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 Copy for Db2 13.1.

Using GDGs and symbolic variables when multitasking

When the GDG base names do not contain adequate symbolic variables to make the GDG names unique, multitasking may cause cataloging difficulties. With 

BMC AMI Copy

 version 9.1.00 and later, spaces may be copied concurrently in several task areas and the non-unique GDG name can cause this problem.

BMC AMI Copy handles GDG name processing for disk. However, controlling tape GDG name assignment is more difficult because tapes are not assigned at allocation time. For tapes, when BMC AMI Copy encounters a poorly constructed GDG name, an informational message is issued that indicates a problem may occur.

Example

Example of a poorly constructed GDG name:

DSNAME INVENTRY.GDG(+1)
Example

Example of a well-constructed GDG name:

DSNAME INVENTRY.&DB.&TS.&TYPE&PART.GDG(+1)

You need the &TYPE variable only when you designate more than one output type (LP, LB, RP, or RB) for the COPYDDN and RECOVERYDDN options.

Related topic

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*