A fix is available
APAR status
Closed as program error.
Error description
ABEND04E RC00C90101 AT DSNICMTC ERQUAL5004 without message in MSTR, dump analysis shows the abend is due to an old mass delete table lock remained in ALLOC duration. Trigger condition: The issue might occur when 1.)package break-in happens to 2.)an ISOLATION(UR) & 3.)bind RELEASE(DEALLOCATE) program against a 4.)multi-table tablespace ( classic segment tablespace defined with multi-tables inside)
Local fix
BYPASS/CIRCUMVENTION: Change either one of the conditions out of those four listed in trigger conditions will do.
Problem summary
**************************************************************** * USERS AFFECTED: * * All Db2 12 for z/OS users that run an * * application that is bound with ISOLATION UR * * and RELEASE(DEALLOCATE)option against a * * segmented tablespace that has multi-tables * * defined and package break-in happened. * **************************************************************** * PROBLEM DESCRIPTION: * * ABEND=04E-RC00C90101 in DSNICMTC * * with ERQUAL5004 during commit. * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** When Db2 users run an application that is bound with ISOLATION(UR) and RELEASE(DEALLOCATE)option against a segmented tablespace that has multi-tables defined and package break-in happened. During the commit process, the allocation duration mass delete lock will be downgraded to commit duration. However, Db2 code internal checking was affected by the other table in the same segmented table space and the downgrade process was incorrectly skipped, which caused the inconsistency between the Data Manager internal control block information and IRLM control information.The above inconsistency caused the ABEND=04E-RC00C90101 in DSNICMTC with ERQUAL5004.
Problem conclusion
Fixes made in Db2 to correctly handle the internal checking when downgrade mass delete lock during the commit process.
Temporary fix
Comments
APAR Information
APAR number
PH41335
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-10-15
Closed date
2021-12-04
Last modified date
2022-01-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
010PC2 UI78403
Modules/Macros
DSNICMT2
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI78403
UP21/12/11 P F112
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0"}]
Document Information
Modified date:
05 January 2022