IBM Support

PH45342: DRF STARTS DATABASES AFTER INDEX REBUILD FAILS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When recovering with ADD IB and STACMD specified, DRF executes
    the START DB command even though the Index Builder has failed.
    This is because DRF does not check the status of the Index
    Builder execution before issuing the START DB command.
    .
    Additional keywords: Database Recovery Facility STACMD
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS Recovery Solution Pack for z/OS      *
    *                 Version 2 Release 1 ( FMID=HAHM210 )         *
    *                 IMS Database Recovery Facility users.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When recovering with ADD IB and STACMD  *
    *                      specified, DRF issues the START DB      *
    *                      command even though the IB has failed.  *
    *                      This is because DRF does not check the  *
    *                      status of the Index Builder execution   *
    *                      before issuing the START DB command.    *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    DRF does not verify whether the database has an index database
    after the database has been recovered by the Sort subordinate
    Address Space (SAS) region and before issuing START DB command.
    It also does not check the results of the index builder before
    issuing START DB command for the index databases recovered by
    the index builder.
    Therefore, when recovery is performed for a database with an
    index database by specifying ADD IB and STACMD, if the recovery
    of the primary database in the SAS region is successful, but
    the process of recovering the index database for that database
    by the index builder before fails, DRF will issue START DB
    commands for the primary and index databases, respectively.
    The truth is, the START DB command should not be issued for
    either database in such a case.
    

Problem conclusion

  • FRXVRCV0 has been modified as follows.
    1. Before issuing START DB command for a database recovered by
    the SAS region, DRF check whether ADD IB is specified, and if
    so, do not issue START DB command.
    2. DRF checks the results of IMS index builder or DFSPREC0
    execution before issuing START DB command to the index database
    recovered by IMS Index Builder or DFSPREC0, and if the
    RC is 4 or less, DRF issues START DB command to the primary
    database and the index database, if the value is 4 or higher,
    STACRT DB command is not issued to both the primary database
    and the index database.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH45342

  • Reported component name

    IMS RCVR SOLUTN

  • Reported component ID

    5655V8600

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-03-31

  • Closed date

    2022-04-19

  • Last modified date

    2022-05-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI80201

Modules/Macros

  • FRXVRCV0
    

Publications Referenced
SC27844102    

Fix information

  • Fixed component name

    IMS RCVR SOLUTN

  • Fixed component ID

    5655V8600

Applicable component levels

  • R210 PSY UI80201

       UP22/04/21 P F204

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"2.1.0"}]

Document Information

Modified date:
04 May 2022