A fix is available
APAR status
Closed as program error.
Error description
Various overlays can be seen after REORG LOGAPPLY of a RRF pageset, since only the first row was found to be in BRF format. The following abends were seen : DB1R,ABND=04E-00E20992,U=@SAT0019,M=N ,C=101.SMC -DSNSGBLK,M=DSNTFRCV,LOC=DSNSLD4 .DSNSVSVB+0EF8 DB4R,ABND=0C4-00000038,U=IOAPROD ,M=N ,C=101.DMC -DSNIISRT,M=DSNTFRCV,LOC=DSNXCEEI.DSNXCEET+027A DB4R,ABND=0C4 00000038 U=IOAPROD ,M=N ,C=101.RDS -SQL ,M=DSNTFRCV,LOC=DSNXGRDS.DSNXRFF +3544 Additional keywords: RC00E20992 ABENDS0C4 ABEND0C4 PIC38 DSNXRFF OFFSET3544 DSNXCEET OFFSET027A DB2OVRLAY/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 for z/OS v10 and v11 users running * * REORG utility with SHRLEVEL CHANGE. * **************************************************************** * PROBLEM DESCRIPTION: Table space is in RRF, during REORG * * SHRLEVEL CHANGE another UR inserted * * some data records, REORG applied all * * the inserts into the shadow database, * * but the first applied insert was * * converted from RRF to BRF during the * * log apply phase. When this incorrect * * record is accessed, it is processed * * as a RRF, the incorrect contents caused * * storage overlay problems such as: * * * * ABENDS0C4-38 in DSNXGRDS.DSNXRFF +3544 * **************************************************************** * RECOMMENDATION: * **************************************************************** At the beginning of REORG Log Apply phase, the insert code may not have initialized the record format indicator based on various conditions, so the indicator has the wrong information about the record format. Therefore, the record was inserted in the wrong format.
Problem conclusion
DB2 code is changed to initialize the record format indicator to ensure that the value is current for REORG log apply insert activities. Also added sanity check to ensure all REORG log apply inserts are using the correct record format before writing the record to the data page.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI72016
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-08
Closed date
2016-12-13
Last modified date
2018-03-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI43299 UI43300
Modules/Macros
DSNISGRT DSNISMRT DSNISRTI
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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:
14 March 2018