PH52111: OBJECTS COULD BE LEFT IN PSEUDO OPEN FOR A LONG TIME IF WRITE CLAIM IS NEVER MADE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If an object is only updated under a drain like COPY utility,
  the object would be pseudo opened without a write claim.  If
  write claim is never made afterwards, sporadic read claims would
  advance one internal timestamp and keep delaying the pseudo
  close.
  

Local fix

• BYPASS/CIRCUMVENTION:
  n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 12 for z/OS and Db2 13 for z/OS                      *
  * users of data sharing.                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * After a COPY utility completed,                              *
  * the page set P-lock was held as SIX                          *
  * for a long time, keeping the object                          *
  * GBP dependent in read-write mode.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  When there is no write activity on an object for PCLOSET
  minutes, the object is converted to read-only.  This
  conversion process downgrades the page set P-lock to
  a read-only state.  If the page set P-lock was held
  as SIX, castouts are done, the object is converted to
  non-GBP-dependent and the page set P-lock is downgraded
  to the read-only S state.
  Write activity is usually determined by write claims, but
  agents such as the COPY utility can update a page without
  a write claim. Special tracking is done for these
  updates that are done without a write claim, but the
  timestamp used to determine when the last update completed
  was not correct.  This caused the page set P-lock to be held
  as SIX even though there was no write activity.
  

Problem conclusion

• Db2 was fixed to correctly track the write activity for
  updates that are done by the COPY utility.
  

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:

  UI92173 UI92174

Modules/Macros

• DSNB1CPS DSNB1PCP DSNB1DCM DSNB1DDN
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI92173

     UP23/06/22 P F306

• RD10 PSY UI92174

     UP23/06/22 P F306

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.