PI24194: DB2 RESTART DOES NOT IMMEDIATELY TERMINATE FOLLOWING CONDITIONAL RESTART LOG READ ERROR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When an incorrect RBA or LRSN value is specified on a
  conditional restart, the following error messages may be issued:
  MSGDSNJ153E DSNJR006 CRITICAL LOG READ ERROR
  MSGDSNJ113E DSNJR003 RBA '00006F509000' NOT IN ANY
  ACTIVE OR ARCHIVE LOG DATA SET. CONNECTION-ID=VA1A,
  CORRELATION-ID=004.JW006 00, MEMBER-ID=0
  MSGDSNJ098E DSNJW306 CRCR ENDLRSN OF 00006F509000 IS
  HIGHER THAN ANY KNOWN RBA, NO TRUNCATION WILL OCCUR.
  If running in single logging mode, and there are COPY2 active
  logs in the BSDS, DB2 restart may not terminate following
  these error messages.  DB2 restart may eventually fail, or
  restart could complete without doing any log truncation.  DB2
  restart should fail immediately with
  DSNJ232I OUTPUT DATA SET CONTROL INITIALIZATION PROCESSING
  FAILED and
  DSNV086E DB2 ABNORMAL TERMINATION REASON=00E80084
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of DB2 for zOS.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: DB2 does not terminate immediately      *
  *                      when a log read error is received       *
  *                      due to an incorrect RBA or LRSN         *
  *                      specified on a conditional restart      *
  *                      of DB2.  DB2 restart may eventually     *
  *                      abend, or could complete restart        *
  *                      without truncating the logs.  This can  *
  *                      happen during a conditional restart in  *
  *                      single logging mode, when there are     *
  *                      COPY2 active log data sets registered   *
  *                      in the BSDS.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A non-zero return code could be lost in DSNJW306 when a log
  read error is received during a conditional restart of DB2
  in single logging mode, and when there are still COPY2 active
  log data sets in the BSDS.  DB2 should terminate immediately
  with:
  DSNJ232I OUTPUT DATA SET CONTROL INITIALIZATION PROCESSING
  FAILED and
  DSNV086E DB2 ABNORMAL TERMINATION REASON=00E80084
  

Problem conclusion

• Return code checking has been corrected in DSNJW306.
  

Temporary fix

Comments

APAR Information

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

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

  UI21280 UI21281

Modules/Macros

•    DSNJW306
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI21280

     UP14/09/26 P F409

• RB10 PSY UI21281

     UP14/09/26 P F409

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.