PK27611: NEW FUNCTION - DH320

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• New function - for DCR DH320.
  

Local fix

• For data sharing users running an application that reads
  the logs with the IFI facility (eg. Replication product),
  make sure that the PTF for PK81566 is applied before
  resetting the RBA to zero with a cold start.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of DB2.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Periodically issue a warning message    *
  *                      as DB2 approaches the end of the log    *
  *                      RBA range (x'FFFFFFFFFFFF').  Terminate *
  *                      DB2 if the current log RBA value        *
  *                      reaches within 4 Gb of the maximum RBA  *
  *                      value, and only allow DB2 restart in    *
  *                      "light" mode or ACCESS(MAINT) mode.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Provide warning messages as DB2 approaches the end of the
  log RBA range.  Allowing the log RBA value to reach the
  maximum RBA value of x'FFFFFFFFFFFF' will result in an
  extended and unplanned recovery outage.  The warning message
  will allow time to plan for quiescing DB2 and resetting the
  log RBA value.
  

Problem conclusion

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

• During DB2 restart and when DB2 switches active log data sets,
  DB2 will issue a new DSNJ032I warning message if the current
  log RBA value exceeds F80000000000.  At this point, users
  should begin the process of planning to quiesce this DB2 system
  and possibly resetting the log RBA.  The Print Log Map utility
  (DSNJU004) output can be used to calculate the average log RBA
  range used per day, which can be used to calculate the amount
  of time before DB2 reaches the end of the log RBA range
  (FFFFFFFFFFFF).
  
  DB2 will continue to run until the current log RBA value
  exceeds FFFF00000000.  At this point, there is only 4 Gb of
  log space available for DB2 to remain recoverable.  DB2 will
  issue the DSNJ032I message indicating the situation is now
  CRITICAL and will terminate with RC00D10251.  Any subsequent
  general access restart of DB2 will then be done in "light" mode,
  and DB2 will automatically shut down after restart has
  completed any incomplete units-of-recovery (URs).  DB2 can
  then be restarted in ACCESS(MAINT) mode to recover any
  In-Doubt URs, to -START any tablespaces in a restricted state
  (eg. LPL or GRECP), and to -TERM any in-progress utilities.
  
  The DB2 Message and Codes manual will be updated with the
  following message description:
  
  DSNJ032I csect-name alert-lvl - APPROACHING END OF THE LOG RBA
         RANGE OF FFFFFFFFFFFF.  CURRENT LOG RBA IS xxxxxxxxxxxx.
  
  Explanation: The current log RBA is approaching the end of the
  log RBA range.  xxxxxxxxxxxx is the current log RBA value.
  The current log RBA should not be allowed to advance to the
  maximum value of FFFFFFFFFFFF.  alert-lvl indicates one of the
  following:
  
  o WARNING  issued when the current log RBA reaches the
             F80000000000 value.  DB2 will continue processing.
  
  o CRITICAL issued after the log RBA value reaches FFFF00000000.
             If the message is issued during DB2 restart,
             processing will continue.  Otherwise, DB2 will
             terminate with reason code 00D10251.
  
  System Action: DB2 continues processing if the alert-lvl is
  WARNING or DB2 is restarting, otherwise DB2 terminates.  Any
  attempt to restart DB2 in general access mode following the
  CRITICAL termination will result in DB2 restarting in "light"
  mode, and DB2 will shut down after restart completes the
  recovery of the incomplete units-of-recovery.  DB2 can then
  be restarted in ACCESS(MAINT) mode to recover any In-Doubt URs,
  to -START any tablespaces in a restricted state (eg. LPL or
  GRECP), and to -TERM any in-progress utilities.
  
  Operator Response: Notify the System Programmer.
  
  System Programmer Response:  Contact IBM Support for assistance
  and current procedures on how to quiesce DB2 and reset the log
  RBA value.
  ==============================================================
  The procedure for quiescing the DB2 system and resetting the
  log RBA value will be documented at a future time.  Until
  then, users should contact IBM for assistance.  MSGDSNJ032I
  

APAR Information

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

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

  UK16512 UK16513

Modules/Macros

• DSNDLWTO DSNFJDIR DSNFJDTA DSNFMDIR DSNJT001
  DSNJW009 DSNJW307
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R710 PSY UK16512

     UP06/08/09 P F608

• R810 PSY UK16513

     UP06/08/09 P F608

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.