Skip to Content
Information
Limited support BMC 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

The GDG format that you use in data set name construction is the same format that you use in JCL when you use DD statements to allocate your copy data sets.

When dynamic allocation is used, BMC AMI Copy also provides the option of specifying an input data set, ACPGDG, to provide control cards to be used to define the GDG base if it does not already exist. This data set must contain the control cards to perform an IDCAMS DEFINE, as well as the symbolic variable, &BASE, which BMC AMI Copy replaces with the GDG base name.

ACPGDGLP, ACPGDGLB, ACPGDGRP, and ACPGDGRB can be specified for the GDG bases by copy type. These are DD statements like ACPGDG and are used for the same purpose.

BMC AMI Copy looks for the ACPGDG by copy type first and uses them if they exist. If ACPGDGLP, ACPGDGLB, ACPGDGRP, or ACPGDGRB does not exist, BMC AMI Copy looks for ACPGDG and uses it if it is specified.

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*

BMC AMI Copy for Db2 12.1