Create image copies

Use the following information to create image copies:

• • Build image copies before DROPs or REORGs
  • Select the utility to create the image copy
  • Create partition-level image copies

Build image copies before DROPs or REORGs

If you select Build an image copy before drops or reorgs, an image copy is created before tables are dropped.

Analysis inserts the PIC keyword into the ALUIN input stream.

Consider the following items when you choose to create a pre-drop or pre-reorg image copy:

• If either the NOCOPY or NOCOPYFORCE keywords are in the ALUIN input stream, the IBMCOPY or BMCCOPY keywords are ignored—except if the PIC keyword is also in the ALUIN stream or set in the installation options module.
• The IBM COPY utility is used if the PIC keyword and either the NOCOPY or NOCOPYFORCE keywords are specified in the ALUIN input stream, or if the PIC=Y and either the BMCCOPY=X or BMCCOPY=F keywords are specified in the installation options module.
• If you want to dynamically allocate the image copy data sets that are created before the tables are dropped and either the NOCOPY or NOCOPYFORCE keywords are the in ALUIN input stream, you must manually insert the DYNCOPY keyword into the ALUIN input stream.

Select the utility to create the image copy

You can select one of the following options to indicate which utility should be the default for building image copies:

• When you select Use Copy selection specified above to build image copies, separate copy commands generate all of the copies that are taken by the specific copy utility. The product inserts the NOUTILCOPY keyword into the ALUIN input stream.
• If you select Other utilities should build image copies when possible, image copies are created by utilities other than the copy utilities whenever possible. These other utilities include the LOAD, LOADPLUS, BMC AMI Recover, REORG, or REORG PLUS utilities. If the utilities cannot create a copy, a separate copy command is generated. The product inserts the UTILCOPY keyword into the ALUIN input stream.

Consider the following items when you specify the utility to create image copies:

• BMC AMI Reorg disregards the value of UTILCOPY and always creates a copy.
• If you select BMC LOADPLUS, the UTILCOPY keyword creates an image copy during the load. If it is a multi-table table space, the image copy is taken when the last table is loaded.
• If you select IBM LOAD, the UTILCOPY keyword creates an image copy if no other tables exist in the table space. If it is a multi-table table space, the copy utility takes the copies.

• If you select BMC REORG PLUS or IBM REORG, the UTILCOPY keyword creates an image copy if the entire table space is reorged and no tables are being loaded. If the table space is partitioned and REORG is being executed on a single partition, the image copies are deferred and are created later by the load or copy utilities.

  Warning

  Important

  If the reorg is a two-phase reorg (for example, REORG UNLOAD PAUSE / VALUE / REORG RESTART), the control cards to REORG must match exactly on each phase, including the COPYDDN and RECOVERYDDN cards.

• If the NOCOPY, NOCOPYFORCE, DYNCOPY, or PARALLEL keywords are in the ALUIN input stream, the UTILCOPY and NOUTILCOPY keywords are ignored—except if you have selected the BMC AMI Recover utility.

Create partition-level image copies

You can specify whether Analysis generates partition-level image copies for any partitioned table spaces or indexes.

If you select Make partition level copies using BMC utilities, the products use the BMC AMI Copy, LOADPLUS, BMC AMI Recover, BMC AMI Reorg, or REORG PLUS utility to make the copy. The products insert the PARTCOPY keyword into the ALUIN input stream. (The products insert the NOPARTCOPY keyword into the ALUIN input stream if you choose not to make a partition-level copy.)

For partitioned and nonpartitioned objects, the products use different ddnames for the following copies:

• Local primary copy
• Local backup copy
• Recovery primary copy
• Recovery backup copy

The following table lists the naming conventions for the primary and backup copies:

Type of copy	Nonpartitioned object DDName	Partitioned object DDName
Local primary	SYCLnnnn	Cxxxyyyy
Local backup	SYCRnnnn	Dxxxyyyy
Recovery primary	RECLnnnn	Exxxyyyy
Recovery backup	RECRnnnn	Fxxxyyyy

In the preceding table, nnnn represents a sequential number for the table space or index. The variable xxx represents a sequential number that pertains to the table space or index that is copied, and yyyy represents the partition number for copies made by BMC AMI Copy.

When you select Make partition level copies using BMC utilities, the products use the following ddnames:

• If the object is partitioned, the products use the partitioned object ddname.
• If the object is not partitioned, the products use the nonpartitioned object name.