IBM Support

PK82637: GET MESSAGE FRD4216W LEAP SECONDS APPLIED 000, DIFFER FROM LOG 034, DRF RECOVERY ENDED WITH RC=4 09/04/28 PTF PECHANGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Get message FRD4216W LEAP SECONDS APPLIED 000, DIFFER FROM LOG
    034, DRF recovery ended with RC=4
    We do not need to adjust timestamp with leapseconds because we
    only perform FULL database recovery. We do not use PITR nor TSR.
    Therefore RC=4 and FRD4216W are inappropriate in our environment
    .
    Also, message description in Users Guide for FRD4216W is not
    adequate. By following the directions provided recovery will
    result in incorrect output.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users that has PK63938 installed         *
    ****************************************************************
    * PROBLEM DESCRIPTION: PK63938 for Leapsecond adhustment in    *
    *                      DRF does not calculate the correct      *
    *                      value from the IMS logs. This is due to *
    *                      the timestamps on certain log records   *
    *                      not containing expected values. A       *
    *                      warning message is issued when the log  *
    *                      leapseconds and the CVTLSO value does   *
    *                      not match. The incorrect value can also *
    *                      lead to records being dropped from a    *
    *                      DRF recovery. This APAR removes         *
    *                      Leapsecond procesing                    *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    Disable functionality introduced by PK63938 (Leapseconds) due to
    values calculated from logs for leap seconds being misleading.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    Users that has PK63938 installed should install this APAR to
    disable Leapsecond processing.
    

Temporary fix

  • *********
    * HIPER *
    *********
     IN CASES WHERE DATA LOSS IS SUSPECTED, ADD CONTROL CARD
     LEAPSECS(000), IGNORE THE LEAPSECS WARNING AND RC=4.
    

Comments

APAR Information

  • APAR number

    PK82637

  • Reported component name

    IMS DB RECOVERY

  • Reported component ID

    5655I4400

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-03-16

  • Closed date

    2009-04-21

  • Last modified date

    2009-10-01

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

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

    UK45913

Modules/Macros

  • FRXRBUF0
    

Fix information

  • Fixed component name

    IMS DB RECOVERY

  • Fixed component ID

    5655I4400

Applicable component levels

  • R310 PSN UK45913

       UP09/04/23 P F904 «

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88Z","label":"IMS Database Recovery Facility"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 October 2009