Producing image copies
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*
For efficiency, BMC AMI Reorg might initiate an extra copy server. This server job functions solely to produce image copies from objects that have been already reorganized and completed.
In addition to the syntax options described in REORG-TABLESPACE-syntax-diagrams, you can use the following controls.
Important
BMC AMI Reorg supports only dynamic allocation of copy data sets. If you specify copy DD statements in your JCL, BMC AMI Reorg ignores them.
Global parameters | The following global parameters enable you to control copy processing:
|
---|---|
NGTTAPE command | The NGTTAPE-command passes tape unit allocation data to BMC AMI Reorg. |
OUTPUT command | The BMC-AMI-Reorg-OUTPUT-command passes allocation information to BMC AMI Reorg. |
Automation control points | The following automation control points enable you to control copy processing:
|
In the following example, only a Local Primary (LP) copy is requested. Since this is the default copy destination the Reorg statement does not have to specify it. The DDNCOUNT keyword mounts two tape drives for the LP copy to write copies in parallel.
In this example:
a Remote Primary (RP) copy is requested so a RECOVERYDDN keyword is added to the Reorg statement. A COPYDDN keyword was still not required because the LP copy is required and will be produced. Having the NGTTAPE LP statement directs it to tape rather than the default of DASD
NGTTAPE is used for all Db2 copy destinations. The REORG statement requests the copy destinations and the NGTTAPE statement specifies its destination which defaults to DASD if not specified