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.

ACPGDG data sets

If you use dynamic allocation when making image copies, you can specify an optional data set, ACPGDG, to provide a GDG model that is applied if a GDG base does not exist.

This data set must contain the control cards to perform an IDCAMS DEFINE. The data set must also contain the symbolic variable, &BASE, that BMC AMI Copy replaces with the GDG base name needed. (For more information, see Using-symbolic-variables.) BMC AMI Copy will invoke IDCAMS and direct the output to SYSPRINT.

Example

This example defines a GDG base if one does not already exist and specifies keeping three generations of the data set, scratching (and uncataloging) any data sets beyond three.

DEFINE GDG (NAME(&BASE) LIMIT(3) SCR)

You can specify ACPGDGLP, ACPGDGLB, ACPGDGRP, and ACPGDGRB 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.

You may use ACPGDG data sets if you use the COPY, COPY IMAGECOPY, or TEMPLATE command to make copies. 

GUID-39295085-F4AA-40FE-BC68-2C663161DD18-low.png

Related topic

BMC-AMI-Copy-data-set-DD-statements



 

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