PM19497: APPLICATION GETS SQLCODE -904 RC00C90090 RESOURCE TYPE 00000801 IMMEDIATELY WHEN REQUESTING S-LOCK AND S-LOCK IS UNAVAILABLE

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Current locking protocol says that DB2 will return a SQLCODE904
  (-904) immediately, resource unavailable, showing a resource
  type of 801 (a PACKAGE) and RC00C90090 from DSNXEAAL when an
  ALTER TABLESPACE LOCKSIZE ROW or LOCKSIZE PAGE is issued.
  The problems with this are that the resource is incorrect, and
  there is not the typical wait/delay for an unavailable lock.
  DB2 code will be changed in this situation to return a
  SQLCODE911 (-911), allowing an internal retry for the lock,
  thus causing fewer application issues due to what should really
  not be a resource unavailable condition.
  -
  Additional symptoms:
    When users execute a package, they can receive:
  ABEND04E RC00C90101 DSNGEPLC ERQUAL5004 VRACE5004 5004
  Also, ABEND04E RC00E20005 DSNIDALC DSNSVBK +0994 +994 994
  When the rc00c90101 in dsngeplc occurred, GPR0 at time of abend
  showed rc00c90001. The directory and section records in SPT01
  were inconsistent with the directory in the EDM pool.
  The section was shorter than expected.
  
  This APAR also fixed accessing invalid package directory when
  the execution of the package and rebind or free the same package
  occurred simultaneously.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: DB2 users who simultaneously execute a       *
  *                 package and execute DDL against dependent    *
  *                 objects of that package.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: When users execute a package            *
  *                      with object dependencies, and issue     *
  *                      DDL on those dependent objects at the   *
  *                      same time, they can receive the         *
  *                      following message:                      *
  *                      SQLCODE=-904 RC00C90090                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When running a package with dependent objects and issuing DDL
  against those objects at the same time, DB2 can immediately
  return an SQLCODE -904 resource not available, indicating the
  package as the resource. The real issue is that an
  object was locked for updates. In this failing
  scenario, the typical wait/delay for an unavailable lock does
  not occur.
  

Problem conclusion

Temporary fix

Comments

• DB2 has been changed to wait for a time-out period
  which is controlled by ZPARM value SPRMTOUT,
  thus causing fewer application issues due to what should really
  not be a resource unavailable condition. Now, when trying to
  execute a package and DDL at the same time, if the needed locks
  can not be acquired within the time-out period, -911 is
  returned.
  

APAR Information

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

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

  UK63157 UK63158

Modules/Macros

• DSNGEFLC DSNXEAAL
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• R810 PSY UK63157

     UP10/12/30 P F012

• R910 PSY UK63158

     UP10/12/30 P F012

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.