Virtual image copies

The data set name is recorded in DBRC as an image copy of an index database, but an actual image copy data set does not exist.

Virtual image copies are useful in an environment where you plan to rebuild primary and secondary index databases rather than recovering them. In such an environment, you do not need to create a physical image copy data set for the index databases because they will not be used for recovery purposes.

The image copies defined to DBRC must be assigned the NOREUS parameter.

To allow DBRC to use appropriate purge times for change accumulation processing, BMC recommends that you perform a NOTIFY.IC function for the index databases. When you create a virtual image copy, the Image Copy function performs this notification automatically.

The Image Copy function supports creating an image copy of a shared secondary index data set if, on the IC control statement, you specify the first shared secondary index by using the DBD keyword. The Image Copy function does not support virtual image copies for shared secondary indexes.

To create a virtual image copy, perform the following tasks:

• Specify the VIC keyword in a valid control statement or options module.
• Specify the SIUDSN keyword in a valid control statement or options module.
• Use dynamic allocation members for the data set groups, or provide data set group DD statements.