PK63938: DB UPDATES NOT BEING APPLIED DUE TO THE LEAP SECONDS ISSUE

APAR status

• Closed as program error.

Error description

• DB updates not being applied due to the leap seconds issue
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the DRF product are affected.   *
  *                 Problem have been identified by QA and no    *
  *                 users have yet reported the problem.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: DRF does not account for Leap seconds   *
  *                      when selecting log records. During IMS  *
  *                      log processing the Leapsecond defined   *
  *                      to MVS (CVTLSO), value is added to the  *
  *                      STCK value and this presents a problem  *
  *                      when jobs reqiuring specific time       *
  *                      precision are run. Changes have been    *
  *                      made to 1) Calculate the Leapseconds    *
  *                      from log records, 2) Issue a warning    *
  *                      when Leapseconds calculated do not      *
  *                      match Lea¬seconds in log an 3). Allow   *
  *                      for a new control statement to specify  *
  *                      Leapseconds in the case where the       *
  *                      default (CVTLSO) has to be overwritten. *
  *                      Control statement syntax:LEAPSECS(nnn | *
  *                      MVS | NO )where: nnn = user specified   *
  *                      number of Leapseconds to be applied.    *
  *                      MVS = Value found in CVTLSO             *
  *                      (Default) , Value should be 23 in 2008. *
  *                      NO  = No Leapseconds will be            *
  *                      applied. Same as LEAPSECS(000).         *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  DRF has been changed to allow for the automatic checking of the
  Leap second values aplied to the IMS STCK value. A new keyword
  LEAPSECS(nnn | MVS | NO) has been added to allow the users to
  specify / override the default value for Leapseconds. The Leap
  second value will be subtracted from the STCK value prior to
  checking the value within DRF.
  

Problem conclusion

• AIDS: RIDS/UTIL RIDS/DBS DBS/UTIL
   GEN:
  KEYWORDS:
  
  *** END IMS KEYWORDS ***
  Code changes has been made to allow for the adjustement of the
  Leapsecond value by DRF prior to record selection. In the IMS
  log records the STCK value has the Leapseconds storeed in CVTLSO
  included and this leads to incorrect record selection when a
  PITR recovery is performed. In most cases this does not present
  a problem since the RCVTIME specified is greater than 23 seconds
  from actual time. In cases where specific time stamps are
  required, the leapsecond value can affect record selection.
  

Temporary fix

Comments

• ×**** PE09/04/28 PTF IN ERROR. SEE APAR PK82637  FOR DESCRIPTION
  

APAR Information

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

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

  UK44187

Modules/Macros

• FRXBDMG0 FRXEDRF  FRXEDRF0 FRXEPSS0 FRXEWSP
  FRXRBUF0 FRXRVGB  FRXRWSP  FRXVWSP
  

Fix information

• Fixed component name

  IMS DB RECOVERY

• Fixed component ID

  5655I4400

Applicable component levels

• R310 PSY UK44187

     UP09/02/21 P F902