Using Missed Object Policies

You can have BRMS record library objects and members or directories and files that could not be saved when running backup control groups. BRMS records the unsaved objects in a missed object policy which is nothing more than another backup control group containing one or more backup object lists or backup link lists containing these missed objects. You can then use the missed object policy to review which objects did not get saved, or to run the missed object policy in an attempt to re-save the missed objects.

Note:
Missed object policies do not support folder and documents or spooled files.

To have BRMS record unsaved objects for all backup control groups, you can specify a missed object policy name on the Missed object policy prompt of the Backup policy. To have BRMS record unsaved objects for individual backup control groups, you can specify a missed object policy name on the Missed object policy prompt on specific backup control groups.

                        Change Backup Control Group Attributes

Group  . . . . . . . . . . . . . . . . : *BKUGRP

Type information, press Enter.

IPL after backup . . . . . . . . . . . . *BKUPCY     *YES, *NO, *BKUPCY
How to end  . . . . . . . . . . . . . *BKUPCY     *CNTRLD, *IMMED, *BKUPCY
Delay time, if *CNTRLD  . . . . . . . *BKUPCY     Seconds, *NOLIMIT
Restart after power down  . . . . . . *BKUPCY     *YES, *NO, *BKUPCY
IPL source  . . . . . . . . . . . . . *BKUPCY     *PANEL, A, B, *BKUPCY
IPL restart type  . . . . . . . . . . *IPLA       *FULL, *IPLA, *SYS ...
Save active wait time:
Object locks  . . . . . . . . . . . . 120         0-99999, *NOMAX
Pending record changes  . . . . . . . 120         0-99999, *NOCMTBDY, *NOMAX
Other pending changes . . . . . . . . 120         0-99999, *NOMAX
Backup item exit program . . . . . . . . *NONE       Name, *NONE, *BKUPCY
Exit program library  . . . . . . . .             Name
Exit program format . . . . . . . . .             BKUI0100
Missed object policy . . . . . . . . . . NOTSAVED    Name, *NONE, *BKUPCY
Clear missed objects . . . . . . . . . *YES        *NO, *YES                 

If the missed object policy does not exist when the backup control group runs, it will be created using the same attributes as the current backup control group. If the missed policy exists, you can also specify whether it is cleared of any existing missed objects using the Clear missed objects prompt.

Missed objects are recorded in backup object lists and/or backup link lists, and these lists are added to the missed object policy as backup items. The format of the backup lists name is Znnnnnnaaa where nnnnnn is the current job number and aaa is unique sequence identifer. These backup lists are created as needed depending on the auxiliary storage pool, object detail, and save-while-active attributes of the current backup items. These lists are deleted when a missed object policy is cleared. If you do not clear a missed object policy and use it for a subsequent backup, new lists are created and added as backup items to the missed object policy.



[ Top of Page | Previous Page | Next Page | Contents | Index ]