Setting system recovery options
You can set system recovery options in each system recovery profile. You can also update system recovery options when you build the recovery job.
Procedure
-
On the Update System Recovery Profile panel, specify
Y in the Update Recovery Options field and press
Enter.
Figure 1. System Recovery Options panel (BSY$SRP2) BSY$RECR V2R2 -------- System Recovery Options --------- 2021/08/27 13:35:3 Option ===> ----------------------------------------------------------------- Creator: CSMESHA Name: IBA2 DBHDO00 SSID: IBA2 Share Option: U (Upd,View,No) Description: IBA2 DBHDO00 ------------------------------------------------------------------------------- Enter the Recovery options to associate with this profile: More: + Execute Recovery ==> Y (Yes) Edit Options N (Yes/No) Execute Index Rebuild ==> Y (Yes/No/Rcvutil) Edit Options N (Yes/No) Create Post Recovery IC ==> Y (Yes/No/Rcvutil) Edit Options N (Yes/No) Recovery Type ==> 2 (1=PITR/2=LASTPITCA/3=LASTIC) Action on Warnings ==> C Continue/Wtor/Abort) GENJCL Defaults Member ==> Datasets for GENJCL ==> SIR.IBA2.NEW.JCLPDS ==> ==> ==> ==>
-
From the System Recovery Options panel, specify information in one or more
of the following fields:
- Execute Recovery
- The only valid value in this field is Y. You must specify a type of recovery utility for
recovery.
- Edit Options
- To update the Execute Recovery parameters, specify Y in this field to access the Recovery Utility Parameter Update panel. Specify N if you do not want to update these parameters.
- Execute Index Rebuild
- Specify Y (Yes) or N (No) to indicate whether you
want to perform index rebuild.
You may also specify R (Rcvutil) to perform index rebuild as an integrated utility. This allows the restart code to process correctly if some related indexes were not rebuilt.
To edit the options for driving Full Function, Fast Path, and HALDB indexes and ILDS, open the Index Rebuild Utility Parameter Update panel.
- Edit Options
- If you want to update the Execute Index Rebuild parameters, specify Y in this field to access the Index Rebuild Utility Parameter Update panel. Specify N if you do not want to update these parameters.
- Create Post Recovery IC
- Specify Y (Yes) or N (No) to indicate whether you
want to create image copies for recovered databases.
You may also specify R (Rcvutil) to create image copies for recovered databases as an integrated utility. This allows the restart code to process correctly if an image copy does not exist after recovery.
- Edit Options
- If you want to update the Create Post Recovery IC utility parameters, specify Y in this field to access the Post Recovery IC Utility Parameter Update panel. Specify N if you do not want to update these parameters.
- Recovery Type
- Specify the type of recovery to perform at the disaster recovery site when the recovery job is
executed. There are three possible types of recoveries that can be performed at the disaster
recovery site:
- PITR
- This is the default recovery method performed at the disaster recovery site when recovering application objects. If using the IMS Database Recovery Facility (DRF) for recovery, the DRF command RCVTIME(timestamp,PITR) is generated and used to recover all objects in this profile. The timestamp specified is determined by the disaster recovery preparation job by inspecting the available archive logs and determining the most current timestamp that can be used for recovery.
- LASTPICA
- This option requires the use of DRF. The command RCVTYPE(LASTPITCA) is
generated to recover all objects in the profile using the last point in time changed accumulation
(PITCA) recovery point and the image copy prior to this PITCA. When this method is selected, all the
objects included in the System Recovery Profile are change accumulation groups. If anything other
than change accumulation groups are specified, an error message is issued and the Recovery Type is
set to 1 for PITR. When the disaster recovery preparation job executes, it performs additional
validation to ensure objects with LASTPITCA are recoverable. The following verification is done:
- Verify that only change accumulation groups are included in the profile. If not, then an error message is issued and processing terminates.
- Verify that for each change accumulation group in the profile, a PITCA exists. If not, then an error message is issued and processing terminates.
- Find the last PITCA for each change accumulation group in the profile and ensure that the time between the oldest and newest is within the range of hours specified in the BSY#PARM parameter DR_LASTPITCA_RANGE. If not, a warning message is issued but processing continues.
- Find the newest PITCA for all of the change accumulation groups and ensure that it is not older than the hours specified in the BSY#PARM parameter DR_LASTPITCA_AGE. If it is, a warning message is issued but processing continues.
- Once all verification is completed, the stop time of the last (that is, newest PITCA) across all of the groups is saved and used as the coordinated recovery time.
If the DR profile indicates an external Db2® subsystem, then this coordinated recovery time is used to provide a Db2 RBA and LRSN that can be used to recover the associated Db2 objects.
For each System Recovery Profile that specifies LASTPITCA as the recovery type, a new member in the DR PDS is created with the name pattern of ssidTnnn where ssid is the SSID of the IMS system being processed and nnn is a number from 000-998 matching the ssid#nnn member in the DR PDS created to perform application recovery for the profile. This member contains detailed information for LASTPITCA processing as well as the coordinated recovery time and Db2 RBA/LRSN.
- LASTIC
- This option requires the use of DRF. The command RCVTYPE(LASTIC) is generated
to recover all objects in the profile using the last batch image copy. No forward log processing is
performed. When the disaster recovery preparation job executes, additional validation is performed
to ensure objects with LASTIC are recoverable. The following verification is done:
- Verify that every object to be recovered has a batch image copy. If not, an error message is issued and the job terminates.
- Find the last batch IC for each object in the profile and ensure that the time between the oldest and newest is within the range of hours specified in the BSY#PARM parameter DR_LASTIC_RANGE. If not, a warning message is issued but processing continues.
- Find the last batch IC and ensure that it is not older than the hours specified in the BSY#PARM parameter DR_LASTIC_AGE. If it is, a warning message is issued but processing continues.
- INITONLY
- This option allows the user to set the System Recovery Profile so that the objects in the
profile are initialized instead of recovered. This option is only valid for a DR System Recovery
Profile. It is not valid for local recovery. Specifying INITONLY in the Recovery
Type field will change certain labels in the Recovery Utility
Options panel. Specifying INITONLY will also require the INIT GENJCL member
name to be specified. If left unspecified, Recovery Type will
reset to PITR and the message BSY956E will be issued. For more information, see Setting recovery utility options.
When INITONLY is specified, the following processes are available for recovery:
- IDCAMS delete / define
- Index Rebuild
- Post Recovery Image Copy
- Update Spawned Job Options
- Specify Y (Yes) to specify Spawned Job Options, or N (No) to use the default method for generating the jobcard and/or jobname. For more information, see Setting spawned job options.
- Action on Warnings
- Specify how you want to process warnings that are issued during recovery. Specify A to abort, C to continue, or W to issue a WTOR.
- GENJCL Defaults Member
- Specify a member to be used as the GENJCL defaults when GENJCL is executed. If specified, this member will be included in the DEFAULTS() keyword.
- Datasets for GENJCL
- Specify up to 5 data sets for GENJCL skeletons. The data sets are concatenated in this order. These data sets are used by the recovery utility to restore an image copy, apply logs, or both; the index rebuild utility; the change accumulation utility; or a post-recovery image copy and pointer checker utility.