A fix is available
APAR status
Closed as program error.
Error description
DSMD ABND 04E 00C90101 U=RSVUSR M=N C=101.LOCN LOC=DSNIDM DSNIRNXT 53A2 RC00C90101 DSNIRNXT ERQUAL53A2 on a workfile. The ABEND happened because a segment in SESSION.SYSINDEXES had some SESSION.SYSCOLUMNS rows. Additional symptoms: 00C90101 DSNITNPG ERQUAL5097 5097 00C90216 DSNIRNXT ERQUAL5008 5008
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 10 (NFM) for z/OS users of DGTT - * * declared global temporary tables (both * * regular external ones and the internal * * ones built for static scrollable cursor or * * INSTEAD OF trigger usage) and partition-by- * * growth table spaces defined in Workfile * * database * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIRNXT ERQUAL53A2 * * during DGTT application when DB2 stores * * DGTT in partition-by-growth table space * * in Workfile database (new ability in * * DB2 10 NFM) * * * * ABEND04E RC00C90216 DSNIRNXT ERQUAL5008 * * is also possible, as well as storage * * overlay due to fetching rows with * * incorrect format * **************************************************************** * RECOMMENDATION: * **************************************************************** When concurrent DGTT applications were running on a partition- by-growth table space in Workfile database, the aforementioned abend occurred due to a conflicting space usage between these applications. Specifically, the first (offending) application mistakenly inserted a DGTT row into a segment that belonged to the second (victim) application's DGTT. When the victim application read this foreign row, it abended due to the inability to interpret it. The root cause of this problem is an incorrect search for free space during insert of the offending application, when such free space was created earlier during singleton delete by the same offending application. During the insert, this application mistakenly interpreted an internal segment cursor field with disregard to the partition it represented and so as a result, the offending application inserted into segment X in partition 1 (belonging to the victim application), when it should have inserted into segment X in a different partition.
Problem conclusion
Code has been changed to properly interpret the internal segment cursor field during space search for insert into DGTT in a partition-by-growth table space in Workfile database. Additional keywords: SQLDGTT SQLPBG SMCOVERLAY DB2OVRLAY/K
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PM84542
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2013-03-11
Closed date
2013-06-17
Last modified date
2013-08-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK95212
Modules/Macros
DSNISGSC
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK95212
UP13/07/03 P F307
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 August 2013