Using the Missed Object Policy in BRMS
When performing a backup with BRMS, there are times when objects or files are not saved. This page outlines how to use the Missed object policy to save objects that were locked during normal save procedures.
The Missed Object Policy
Beginning in V5R4M0, BRMS has the option to create a list of objects that were locked during normal save operations. In the control group attributes (and Backup Policy), there is a parameter called Missed object policy. The parameter has the following fields:Missed object policy . . . . . . . . . . *NONE Clear missed objects . . . . . . . . . *NO
This policy specifies the name of backup control group and lists that will be used to track missed objects during backup control group processing. If the backup control group or lists do not exist, these will be created using the same attributes as the current backup control group. When a user specifies a policy name, if the control group with that name does not exist, BRMS will create one with that name. An object list will also be created (WRKLBRM). The naming convention of the object list will be Zxxxxxxyyy (where xxxxxx is the job number of the save and yyy is a suffix). A list for each SAVLIB , SAVOBJ, or SAVCGHOBJ command BRMS build in the control group is created. Each of these lists will be added to the control group that is created.
Control Group Entries
Group . . . . . . . . . . : LOCKS Default activity . . . . : *BKUPCY Text . . . . . . . . . . : *NONE Auxiliary Weekly Retain Save SWA Backup List Storage Activity Object While MessageSeq Items Type Pool Device SMTWTFS Detail Active Queue 10 MISSED1 *SYSBAS *DFTACT *YES *NO 20 *EXIT *DFTACT 30 MISSED2 *SYSBAS *DFTACT *YES *NO
Control Group Attributes
IPL after backup . . . . . . . . . . . . *NO *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 . . . . . . . . . . *BKUPCY *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 . . . . . . . . *BKUPCY Name, *NONE, *BKUPCY Exit program library . . . . . . . . Name Exit program format . . . . . . . . . BKUI0100 Missed object policy . . . . . . . . . . MISSED Name, *NONE, *BKUPCY Clear missed objects . . . . . . . . . *YES *NO, *YES
Objects OBJECTA and OBJECTB were locked during the save.
Object Lists That Are Created
Use . . . . . . . . . : *BKU List name . . . . . . : Z515264001 Text . . . . . . . . : Entry created by BRM configuration Seq Library Object Type Member 10 MISSED1 OBJECTA *FILE *ALL Use . . . . . . . . . : *BKU List name . . . . . . : Z515264002 Text . . . . . . . . : Entry created by BRM configuration Seq Library Object Type Member 10 MISSED2 OBJECTB *FILE *ALL
New Missed Control Group
Group . . . . . . . . . . : MISSED Default activity . . . . : *BKUPCY Text . . . . . . . . . . : *NONE Auxiliary Weekly Retain Save SWA Backup List Storage Activity Object While Message Seq Items Type Pool Device SMTWTFS Detail Active Queue 20 Z515264001 *OBJ *SYSBAS FFFFFFF *YES *NO 30 Z515264002 *OBJ *SYSBAS FFFFFFF *YES *NO
It is important that this control group does not refer back to itself for the Missed Object Policy parameter. Specify *NONE or a different policy.
If the Missed Object Policy parameter is not updated on this control group and objects are missed again when this control is run, BRM4104 - Control group not found, will be logged.
Group . . . . . . . . . . . . . . . . : MISSED Type the information, and press the Enter key. 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 . . . . . . . . . . *BKUPCY *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 . . . . . . . . *BKUPCY Name, *NONE, *BKUPCY Exit program library . . . . . . . . Name Exit program format . . . . . . . . . BKUI0100 Missed object policy . . . . . . . . . . MISSED1 Name, *NONE, *BKUPCY Clear missed objects . . . . . . . . . *YES *NO, *YES
When control group MISSED is run and any of the objects in the object lists are locked, a new control group called MISSED1 and a new object list is created.
Additional Notes
Only available when using control groups. There is no option to do this if using the SAVLIBBRM or SAVOBJBRM commands.
The creation of these object lists and control group(s) does not mean that the objects are saved. The new control group should still be run when the object can be saved.
If Clear missed objects *NO is specified, the control group may fail with BRM9999 and BRM1820 . This is because a control group can only have 999 sequences. Users will need to manually manage the Missed Object Policy to ensure that there are never more than 999 entries by possibly deleting older sequences.
You must have object level detail specified with a *ERR, *YES, *OBJ, or *MBR for the control group entry in order for the missed object function to work.
Privacy Policy | Cookie Policy | Impressum
From time to time, this website may contain technical inaccuracies and we do not warrant the accuracy of any posted information.
Copyright © Fortra, LLC and its group of companies. All trademarks and registered trademarks are the property of their respective owners.