IBM Support

PK58555: RECOVERY DOES NOT USE THE ICR UNLESS RCVTIME IS EQUAL TO OR LATER THAN THE ICR STOPTIME.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using DRF to create ICR, copy ends with the copy registered to
    DBRC with a Runtime (timestamp of endtime from last SLDS used as
    input) and a Stoptime (the real time that IC took place). A
    later DRF recovery only used that ICR if RCVTIME is equal or
    later than the ICR Stoptime.  Stoptime of such ICR has no
    meaning for recovery, I would better expect DRF to use the
    Runtime.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS DRF version 3 Release 1 users        *
    *                 using the incremental image copy             *
    *                 OUTPUT(ICR) are affected.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: A DRF image copy created using the      *
    *                      OUTPUT(ICR) function while the database *
    *                      was in use could not be used later for  *
    *                      recovery because the stoptime of the IC *
    *                      was later than the RCVTIME for the      *
    *                      recovery.                               *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    DRF Version 3 Release 1 generates incremental image copies with
    the OUTPUT(ICR) function. If the database is in use when the IC
    is generated, it is recorded with DBRC as concurrent (CIC). The
    RUNTIME of the IC is the STOPTIME of the last SLDS used, and
    the STOPTIME is the current time that the OUTPUT(ICR) was run.
    .
    After the database was stopped, a timestamp recovery was
    attempted to a time after the runtime of the IC, but earlier
    than the STOPTIME. Because the STOPTIME was greater than the
    RCVTIME, DRF used an earlier IC, rejecting the latest IC.
    

Problem conclusion

  •  AIDS: RIDS/UTIL RIDS/DBS DBS/UTIL
      GEN:
    
    *** END IMS KEYWORDS ***
    DRF has changed to record the STOPTIME of a concurrent image
    copy created using the OUTPUT(ICR) function as one tenth of a
    second greater than the RUNTIME.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK58555

  • Reported component name

    IMS DB RECOVERY

  • Reported component ID

    5655I4400

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-12-20

  • Closed date

    2008-02-18

  • Last modified date

    2008-07-11

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

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

    UK33812

Modules/Macros

  •    FRXICTL0
    

Fix information

  • Fixed component name

    IMS DB RECOVERY

  • Fixed component ID

    5655I4400

Applicable component levels

  • R310 PSY UK33812

       UP08/02/20 P F802

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88Z","label":"IMS Database Recovery Facility"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210"}]

Document Information

Modified date:
09 November 2020