What's new in IMS Recovery Expert

This topic summarizes the technical changes for this edition.

New and changed information is denoted by carets (Symbol that indicates the start of new or changed content and Symbol that indicates the end of new or changed content) at the beginning and end of the new or changed information. Editorial changes that have no technical significance are not noted.

Revision markers follow these general conventions:

  • Only technical changes are marked; style and grammatical changes are not marked.
  • If part of an element, such as a paragraph, syntax diagram, list item, task step, or figure is changed, the entire element is marked with revision markers, even though only part of the element might have changed.
  • If a topic is changed by more than 50%, the entire topic is marked with revision markers (so it might seem to be a new topic, even though it is not).

Revision markers do not necessarily indicate all the changes made to the information because deleted text and graphics cannot be marked with revision markers.

Start of change

SC19-4368-15

Description Related APARs
This enhancement enables that Partner exit BSYPPUE0 to be used as IMS Refreshable exit. See Enabling IMS Recovery Expert in online and batch IMS environments for more information. PH64441
End of change

SC19-4368-14

Description Related APARs
This enhancement provides a new function to enable database recovery using User Image Copy. A new option is added to the Recovery Resources field on the Recovery Options panel. New and updated topics include: PH54197

SC19-4368-13

Description Related APARs
Documentation change on whether you need to restart the IMS control region after applying the PTF. See Making the IMS Recovery Expert load library available for more information. N/A

SC19-4368-12

Description Related APARs
Description of IMS user exits, BSYPPUE0 and BSYFLGX0, has been added. Updated topics include: N/A

SC19-4368-11

Description Related APARs
With a new parameter, FORCE_STARTDB, IMS Recovery Expert can issue the START DB command even if the DBR command was not issued at the beginning of the database recovery process. New and updated topics include: PH58283

SC19-4368-10

Description Related APARs
Usability improvement on the Parameters for IMS Subsystem ssid panel. New and updated topics include: PH48227

SC19-4368-09

Description Related APARs
Requirement to define resource definition data set when dynamic resource definition is enabled for the IMS online system has been added. New and updated topics include: PH43753

SC19-4368-08

Description Related APARs
This enhancement provides a new Recover IMS catalog first option that enables you to specify whether you want to recover IMS catalog database prior to other databases at the DR site. New and updated topics include: PH42119

SC19-4368-07

Description Related APARs
This enhancement provides a new Disable old backup in DR PDS option that enables you to specify whether you want to disable the previously built backup image of RECON and the IMS Recovery Expert repository in the DR PDS when the DR preparation job is executed. New and updated topics include: PH25092
This enhancement provides a new Key label replication option that enables you to specify whether you want the existing key label information to be set on the KEYLABEL parameter of the DEFINE CLUSTER command. New and updated topics include: PH31570
This enhancement provides a new Archive OLDS at DR site option that enables you to specify whether you want to execute OLDS archiving during the recovery process at the DR site. Also, using another new Delete all SUBSYS in RECON option, you can specify whether to delete all subsystem (SUBSYS) records in the DR RECON. New and updated topics include: PH38350

SC19-4368-06

Application operations redesign
To improve performance and usability, the Application Operations menu and functionality have been redesigned. Application profiles are now segmented into:
  • Object profiles
  • Utility profiles
  • Job profiles

Coordination application profile functionality has not be altered. Users may also now run on-demand operations to build the following jobs without needing a pre-defined profile to work from:

  • Recovery jobs
  • Create Recovery Point jobs
  • Quiet Time Analysis jobs
  • Health Check jobs
New options for controlling spawned job jobname and jobcard
Using the new Update Spawned Job Options option, you can now override the default methods for jobname and jobcard generation.
New recovery option for System Profile Recovery
Using the new recovery type option INITONLY, you can 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.

SC19-4368-05

ACB repository
The new ACB repository is a VSAM KSDS that contains ACBs as loaded and/or updated from the active ACB library (ACBLIB). Use of the ACB repository improves the performance of IMS Recovery Expert functions that access the ACB libraries of large systems.
New PARMLIB member to create unique default recovery options
Using the new member BSY#SSID, you can now create unique, default recovery options for each IMS subsystem or IMS group.
New parameter to control default recovery options
Using the new BSY#PARM parameter IMS_GENJCL_DFLT_MBR, you can control the default recovery options
New recovery options for System Recovery Profiles
New recovery options for System Recovery Profiles allow you to specify the type of recovery that can be performed at the disaster recovery site. The three types of recovery that can be performed are PITR, LASTPITCA, and LASTIC.
New parameters for recovery type options PITR, LASTPITCA, and LASTIC
New parameters for the recovery type options PITR, LASTPITCA, and LASTIC include DR_LASTPITCA_AGE, DR_LASTPITCA_RANGE, DR_LASTIC_AGE, and DR_LASTIC_RANGE.

SC19-4368-04

New parameter to control history information
The new BSY#PARM parameter DR_HISTORY_RETENTION controls the creation and retention of history information associated with each time the Disaster Recovery preparation job is executed.
New IDCAMS delete/define cards created upon job execution
The Disaster Recovery Profile now enables the DR preparation job to create new IDCAMS delete/define cards each time the job executes. The cards can be placed in members in the DR PDS, or a new PDS can be created each time.
New option to skip marking all DBDS as recovery needed
The Disaster Recovery Profile can now skip the process to mark all DBDS as recovery needed when the DR preparation job executes. This process might not be required for your DR environment, and skipping it reduces execution time for the DR preparation job.
New option to skip writing conditioned RECON to DR site
You can now skip writing the conditioned RECON data sets to the DR PDS when you have other methods of sending the conditioned RECON to the DR site.

SC19-4368-03

Run IBM IMS Database Recovery Facility/Extended Functions Health
You can now choose to run the Health Check feature from the following places:
  • Run HCHECK against an application profile.
  • Run HCHECK against a system level backup.
  • In the Disaster Recovery Profile, you can set HCHECK to be run against the conditioned RECON data sets when the disaster recovery preparation job runs.
Dynamic API enables IBM IMS Database Recovery Facility (DRF) and IBM IMS Database Recovery Facility/Extended Functions (DRF/XF) to use System Level Backups (SLBs)
A new dynamic API enables a DRF or DRF/XF job to be aware of any SLB that you have taken which contains data that meets your criteria better than data in the RECON data sets. For example, if you are recovering a database to the current time, and the image copy in the RECON is older than the last SLB, then the API will allow DRF to use the SLB as the image copy, thus reducing the number of logs needed to complete the recovery.
A new Recovery Sensor evaluates information in the RECON data sets to look for problems that can affect recovery
The Recovery Sensor is a batch job that can either be scheduled by the Autonomics Director, or in any job scheduler, and is control card driven. To look for potential problems related to recovery, the Recovery Sensor obtains information from the RECON data sets that matches the criteria you specify. This information is stored in the IMS Tools Knowledge Base (ITKB). You can then create recovery policies to evaluate this information and notify you when problems are detected.

SC19-4368-02

Checkpoint restart capability for local recovery
Checkpoint restart capability is now available when performing local recoveries. To enable this capability, you must:
  • Add the new RECOV_CHKPT_RESTART = YES parameter to your BSY#PARM parameter member
  • Tailor and execute the SBSYSAMP(BSYCHKPT) member to allocate the new checkpoint restart repository
  • Edit your BSYV220 invocation CLIST and:
    • add RBRCHKPT(dsn) on the PROC statement to specify the checkpoint data set
    • add “ISPEXEC VPUT (RBRCHKPT) ASIS” after the PROC statement

For more information, see Managing application recovery checkpoint restart.

Enhanced application recovery processing
Enhancements have been made in application recovery processing for both local and DR site application recovery, which allows more flexibility in defining and executing the utilities required to complete application recovery. With these changes, there are several areas which must be addressed in order to perform application recovery.
BSY#PARM member changes

The following BSY#PARM parameters are obsolete and must be removed from your BSY#PARM member:

  • GENJCL_DRF_RECOV_MEM
  • GENJCL_IMS_RECOV_MEM
  • GENJCL_HPCA_CA_MEM
  • GENJCL_IMS_CA_MEM
  • GENJCL_HPIC_PR_MEM
  • GENJCL_IMS_PR_MEM
  • GENJCL_IMS_FPSI_MEM
  • GENJCL_IMS_HALDB_MEM
  • GENJCL_IMS_IX_MEM
  • IMS_HALDB_UTIL
  • IMS_POINTER_CHECK
  • IMS_STANDARD_UTILITIES
  • IMS_USE_FOR_ILDS_RBLD
  • IMS_USE_FOR_PI_RBLD
  • IMS_VERIFY
  • IMS_VERIFY_LEVEL
  • DR_VERIFY
  • DR_VERIFY_LEVEL
The following BSY#PARM parameters have been renamed and must be changed in your BSY#PARM member:
Old name New name
GENJCL_USER_FPSI_MEM GENJCL_USER_FPIX_MEM
GENJCL_USER_HALDB_MEM GENJCL_USER_HBIX_MEM
GENJCL_USER_IX_MEM GENJCL_USER_FFIX_MEM
GENJCL_USER_PR_MEM GENJCL_USER_IC_MEM
IMS_POST_RECOV_UTIL IMS_IC_UTIL
The following new parameters have been added to BSY#PARM and must be specified:
USE_FFIX_FOR_HALDB_RBLD        N -\* Specify "Y" to use the    *\   
                                 -\* FFIX GENJCL member for    *\   
                                 -\* processing HALDB PINDEX/  *\   
                                 -\* IDLS rebuild or "N" if    *\   
                                 -\* that is not desired       *\   
INDEX_RBLD_WHEN_RECOV          Y -\* Specify "Y" to have any   *\   
                                 -\* index needing recovery to *\   
                                 -\* be rebuilt instead of     *\   
                                 -\* recovered or "N" if this  *\   
                                 -\* is not desired.           *\   
HALDB_RBLD_ON_RECOV_TO_CURRENT Y -\* Specify "Y" to have any   *\   
                                 -\* HALDB ILDS/PINDEX rebuilt *\   
                                 -\* when the HALDB is         *\   
                                 -\* recovered to current or   *\   
                                 -\* "N" if this is not        *\   
                                 -\* desired.                  *\
ACTION_ON_WARNING              C -\* Specify the action to be  *\ 
                                 -\* taken if warnings occur   *\ 
                                 -\* during recovery, "W" to   *\ 
                                 -\* issue a WTOR to pause     *\ 
                                 -\* processing, "C" to        *\ 
                                 -\* continue, or "A" to       *\ 
                                 -\* abort.                    *\    

For more information on the BSY#PARM changes, see (Optional) Configuring the PARMLIB member.

GENJCL member changes
To provide more capability and flexibility for generating the jobs required to perform recovery, index rebuild, change accumulation, and image copy, the structure of the GENJCL members has changed. New members that support the IMS base utilities, IBM IMS Tools utilities, and user utilities have been supplied using the new format. You must modify your existing GENJCL skeletons that are used for application recovery when driven by IMS Recovery Expert. For more information, see Creating GENJCL skeletal members.
Recovery options changes
To provide more flexible processing options when performing the functions associated with application recovery under IMS Recovery Expert, the recovery options have been modified in the following places:
  • System Recovery Profile recovery options
  • Application Profile recovery options
  • System Level Backup restore recovery options

Before you can perform any application recovery processing, you must edit and upgrade the recovery options for any of these areas you currently have set up. If you do not, then when you try to perform application recovery, you will receive an error that the recovery options need to be upgraded and jobs will not process until that is done.

SC19-4368-01

Combined SLB
You can now create a combined SLB for IMS and Db2. For more information, see Performing a Combined System Level Backup.

SC19-4368-00

Storage group discovery
When creating a backup profile and specifying the Source/Target Mapping, you can now specify a new option for SMS storage group discovery for source volumes. With this option, you specify the SMS storage group names which contain the IMS source volumes and all of the volumes in that storage group will be included in the backup. For more information, see Creating System Level Backup profiles for Combined SLB groups.
Redesigned ISPF interface
The ISPF interface has been redesigned for this version of the product.