PK60569: NO NEED TO WRITE DBET DIAGNOSTIC NOTIFY LOG RECORDS DURING DB2 SHUTDOWN. ALSO, DB COMMANDS/DBET SERVICEABILITY ENHANCEMENTS.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• During DB2 shutdown in data sharing, the DB2 that is getting
  shut down need not write DBET diagnostic notify exit log
  records. This will speed up the shutdown.
  Additionally, this APAR introduces DBET-related internal
  serviceability enhancements in the areas of dump formatting
  and control block storage tracking.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 for z/OS data sharing users who      *
  *                 issue -STOP DB2.                             *
  *                                                              *
  *                 Also, all DB2 for z/OS users of -START       *
  *                 DATABASE, -STOP DATABASE and -DISPLAY        *
  *                 DATABASE commands.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION: DBET diagnostic notify exit log records *
  *                      (written only in data sharing) need not *
  *                      be written by DB2 member that is in the *
  *                      process of getting shut down.           *
  *                                                              *
  *                      Also, provide internal serviceability   *
  *                      in the areas of -START DATABASE, -STOP  *
  *                      DATABASE, -DISPLAY DATABASE commands.   *
  *                                                              *
  *                      Also, provide internal serviceability   *
  *                      in the area of dump formatting for      *
  *                      DBET.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In data sharing, DB2 writes DBET-related diagnostic log records
  that help serviceability-wise in ensuring that DBET exception
  states are correctly processed on each active data sharing
  member. However, if a member is in the process of being shut
  down, there is no compelling reason to write these kinds of log
  records on that member, considering that the member is about to
  be down anyway.
  
  Also, unrelated to the above, provide serviceability enhancement
  for REPT internal control block storage tracking, benefiting
  problem diagnosis mostly in the areas of -START DATABASE, -STOP
  DATABASE and -DISPLAY DATABASE commands.
  
  Also, unrelated to any of the above, provide serviceability
  enhancements in the area of dump formatting for DBET-related
  issues.
  

Problem conclusion

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:

  UK39706 UK39707

Modules/Macros

• DSNDREPT DSNGDVUT DSNIDBLG DSNIDBMP DSNIDBRP
  DSNIDRCT DSNIIF   DSNILSTS DSNIRTSX DSNISREC DSNTDINQ DSNTDMST
  DSNTDMUL DSNUDISD DSNUGSRX DSNUGTE0 DSNUKRDY DSNWDFDM
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R810 PSY UK39706

     UP08/09/26 P F809

• R910 PSY UK39707

     UP08/09/25 P F809

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.