Managing change accumulation groups

You can use the

R+/CHANGE ACCUM

online interface to manage change accumulation group definitions and output file sets.

The interface allows you to create and modify change accumulation groups and view the repository information created by change accumulation executions. You can also use the interface to customize some of the online interface options.

Updates to change accumulation groups do not take effect until you exit the definition or template panel by pressing the END key. After you have made a modification, the status field of the panel contains one of the following strings:

ADD PENDING
UPDATE PENDING
DELETE PENDING

You can cancel a requested modification by typing the CANCEL command on the command line of the panel.

Creating change accumulation groups

To create a change accumulation group, you must name the Db2 spaces contained within the group. Also, you must define the templates that you want to use to create the output change accumulation files. You can provide a description to help identify the contents of the group.

When you add Db2 spaces to a change accumulation group, the interface prompts you to supply a database name, table space name, and range of DSNUM values. You can add this definition directly to the change accumulation group, or you can query the Db2 catalog through the online interface to determine whether the space exists. Doing so is helpful when you use wildcards for the object name. The wildcarded name displays all existing table spaces that fit the wildcard definition. You can choose to add the wildcard definition to the change accumulation group, or you can add the individual spaces that have been resolved by the wildcard.

Note

A table space does not have to exist before adding it to a group.

To complete the group, you must define the file templates. The file template describes the physical characteristics of the change accumulation file. The following file templates are available:

LOCAL PRIMARY
LOCAL BACKUP
REMOTE PRIMARY
REMOTE BACKUP

You can define up to four templates for the group.

If the file created by the template is a GDG, you must specify the model data set control block (DSCB) and the number of generations. You should specify the model DSCB unless your installation does not require a model DSCB to allocate a generation data set. If the file is to reside on DASD, you must provide space allocations. Optionally, you can use Storage Management Subsystem (SMS) to manage the file.

You can use the online interface to create a new group using the definitions of an existing group. Then you can use the online interface to make modifications to customize the new group.

Modifying an existing change accumulation group

After you use R+/CHANGE ACCUM to create a change accumulation group, you can modify the space and file template definitions at any time.

These modifications do not alter existing change accumulation file sets, nor do they affect the current state of recovery.

Deleting change accumulation groups and files

When you delete a change accumulation group, R+/CHANGE ACCUM deletes the object and file template definitions.

With the deletion of a change accumulation group or file template, you have the option to delete the file sets and repository log ranges associated with this group or file. If you elect to do so, recoverability of the objects within this group may be affected.

Viewing change accumulation files

You can use the online interface to view repository information created from previous change accumulation executions. The interface displays all of the groups in which a given table space resides. It also displays all of the change accumulation log ranges recorded for the table space. You can narrow this information by specifying a DSNUM value.

For more information, refer to Analyzing-R-CHANGE-ACCUM-data-by-target-space.

Modifying online interface options

You can modify some of the online interface options.

Refer to Setting-and-modifying-options for more information.