Skip to Content

Using GDGs and symbolic variables when multitasking

Related topic
Using GDGs and symbolic variables in data set names 

When the GDG base names do not contain adequate symbolic variables to make the GDG names unique, multitasking might cause cataloging difficulties. With BMC AMI Copy spaces might be copied concurrently in several task areas and the non-unique GDG name can cause this issue.

BMC AMI Copyhandles GDG name processing for the 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 issue might occur.

Information
Example

Example of a poorly constructed GDG name:

DSNAME INVENTRY.GDG(+1)
Information
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.

 

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

BMC AMI Copy for Db2 13.1