Is Your SAVCHGOBJ Really Saving All Changed Objects?
What you may not know about SAVCHGOBJ or BRMS equivalent (Incremental Save), may be detrimental to your backup strategy.
By definition: The Save Changed Object (SAVCHGOBJ) command saves a copy of each changed object or group of objects located in the same library. When *ALL is specified for the Objects (OBJ) parameter, objects can be saved from all user libraries or from a list of libraries. When saving to a save file, only one library can be specified. For database files, only the changed members are saved.
By default, objects being journaled are not saved, which is what this iTech iTip covers.
If you are wondering why objects that have changed are not getting saved, are they being journaled?
For the SAVCHGOBJ command, the default value of the parameter for journaled objects is OBJJRN(*NO). This causes the objects that are journaled not to be saved.
So, how do you get Journaled Files/Objects saved during SAVCHGOBJ?
On the SAVCHGOBJ command, specify OBJJRN(*YES).
Change the command default value of the OBJJRN parameter to *YES for the SAVCHGOBJ command.
CHGCMDDFT CMD(SAVCHGOBJ) NEWDFT(‘OBJJRN(*YES)’)
The BRMS equivalent is incremental backups, which the default is not to save journaled objects. You can specify to save journaled objects during a BRMS incremental backup by:
Specifying *YES for the ‘Journaled Objects’ parameter on the Backup Control Group Attributes screen (WRKCTLGBRM option 8=’Change Attributes’ next to the control group to be changed).
If the control group attributes point to the backup policy, use command WRKPCYBRM *BKU to determine if journaled objects should be saved during an incremental backup. You can change the backup policy parameter ‘Save journaled objects when saving changed objects’ to *YES so that journaled objects are included in the incremental backups.