IBM Support

PH55747: DRF JOB LOOPS WHEN RECOVERING KSDS WITH SMS-FORMAT IC

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DRF goes into a loop while recovering KSDS. This problem occurs
    when recovering a KSDS database using SMS-FORMAT IC, when there
    are Change Accumulation logs that is applied next to the IMS log
    where no IC record exists.
    

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: DRF goes into a loop while recovering   *
    *                      KSDS. This problem occurs when          *
    *                      recovering a KSDS database using        *
    *                      SMS-FORMAT IC, when there are Change    *
    *                      Accumulation logs that should be        *
    *                      applied next to the IMS log where no IC *
    *                      record exists.                          *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    When all of the following conditions are met, writing database
    records results in an endless loop:
    
    IMS Database Recovery Facility recovers a KSDS database
    Input image copy is an SMS image copy
    IMS logs and CA logs are used for recovery
    ADD IC, PC, or OUTPUT(BOTH) is not specified
    When IMS logs and CA records are sorted by keys, CA log records
    are placed after IMS log records where no IC record exists
    Also, this APAR corrects the following two problems:
    #1
    When all of the following conditions are met, IMS Database
    Recovery Facility does not recover database records correctly.
     (Changes in CA in #4 below are not applied to the record.)
    - IMS Database Recovery Facility recovers a KSDS database
    - Input image copy is an SMS image copy
    - ADD IC, PC, or OUTPUT(BOTH) is not specified
    - When IMS logs and CA records are sorted by keys, database
      records are placed in the following sequence:
      1. Image Copy + No CA
      2. No Image Copy + CA
      3. No Image Copy + No CA
      4. Image Copy + CA
    
    #2
    When all of the following conditions are met, IMS Database
    Recovery Facility does not recover database records correctly:
    - IMS Database Recovery Facility recovers a KSDS database
    - Input image copy is an SMS image copy
    - ADD IC, PC, or OUTPUT(BOTH) is specified
    - When IMS logs and CA records are sorted by keys, multiple
      IMS and CA logs for database records without image copy record
      exist between image copy keys
          Or
      When IMS logs and CA records are sorted by keys, IMS and CA
      logs for database records without image copy record exist
      between image copy key and contain delete log records.
    

Problem conclusion

  • This APAR corrects the problem as follows:
    
    Before this APAR, when ADD IC, PC, or OUTPUT(BOTH) was not
    specified, IMS Database Recovery Facility put only the database
    records with CA log or IMS log after restoring image copy to the
    database to be recovered. After the PTF for this APAR is
    applied, IMS Database Recovery Facility puts all of the database
     records.
    When image copy record does not exist between image copy records
    but multiple records with CA logs or IMS logs exist, IMS
    Database Recovery Facility has been corrected so that it does
    not read the next image copy while processing a database record
     without image copy records.
    
    Also, when image copy record does not exist but a CA log or IMS
    log with delete log exists, IMS Database Facility has been
    corrected so that it does not delete the next record.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH55747

  • Reported component name

    IMS RCVR SOLUTN

  • Reported component ID

    5655V8600

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-07-13

  • Closed date

    2023-08-04

  • Last modified date

    2023-09-01

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

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

    UI93051

Modules/Macros

  • FRXBDMG0 FRXIVSM0
    

Fix information

  • Fixed component name

    IMS RCVR SOLUTN

  • Fixed component ID

    5655V8600

Applicable component levels

  • R210 PSY UI93051

       UP23/08/08 P F308 ¢

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":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"2.1.0"}]

Document Information

Modified date:
01 September 2023