APAR status
Closed as program error.
Error description
After DSNI014I message, there were mismatches in DSNI005I message: TYPE did not match OBJECT TYPE and NAME did not match OBJECT NAME. EXAMPLE: DSNI014I -xxxx DSNIBHRE DATA IN USE DURING ABEND REASON 00C90101 ERQUAL 5007 TYPE 00000302 NAME DBxxxxxx.SPxxxxxx.X'02C00143' CONNECTION-ID=xxxx CORRELATION-ID=014.IFTSKS33 LUW-ID=DAPG.DAP2LU.E21D6E3802FF=0 DSNI005I -xxxx DSNILOGA LPL OR GRECP RECOVERY CANNOT 421 BE DONE FOR AUTOMATIC GRECP RECOVERY-ID = 1 OBJECT TYPE 00000210 OBJECT NAME DBxxxxxx.SPxxxxxx.00000045 REASON 00C90101 TYPE 00000300 NAME DBxxxxx.SPxxxxxx.X'8520'.X'02C0014
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Db2 V13 for z/OS users processing * * LPL or GRECP recovery * **************************************************************** * PROBLEM DESCRIPTION: During the Db2 log-apply process for * * LPL or GRECP recovery, a DSNI005I * * message issued after DSNI014I can * * contain incorrect object information. * * In this scenario, the TYPE does not * * match the OBJECT TYPE, the NAME does * * not match the OBJECT NAME, and the * * partition value reported in DSNI005I * * is invalid. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available * **************************************************************** This error can occur during LPL or GRECP recovery log-apply processing when an abend in modules DSNIBHRE or DSNIBHUN triggers DSNI014I and then DSNI005I. In this failure path, DSNI005I is issued with incomplete or corrupted context, causing it to format and print object and partition information from invalid or uninitialized data, leading to mismatched TYPE/NAME fields and an incorrect partition value. Error example: DSNI014I -xxxx DSNIBHRE DATA IN USE DURING ABEND REASON 00C90101 ERQUAL 5007 TYPE 00000302 NAME DB01.SP01.X'02C00143' CONNECTION-ID=xxxx CORRELATION-ID=014.IFTSKS33 LUW-ID=DAPG.DAP2LU.E21D6E3802FF=0 DSNI005I -xxxx DSNILOGA LPL OR GRECP RECOVERY CANNOT 421 BE DONE FOR AUTOMATIC GRECP RECOVERY-ID = 1 OBJECT TYPE 00000210 OBJECT NAME DB01.SP01.00000045 REASON 00C90101 TYPE 00000300 NAME DB01.SP01.X'8520'.X'02C0014
Problem conclusion
Db2 was modified to ensure DSNI005I is issued with a valid object context after DSNI014I, eliminating mismatched TYPE/NAME fields and incorrect partition values so that diagnostic messages now report accurate and reliable information. Fixed example: DSNI014I -xxxx DSNIBHRE DATA IN USE DURING ABEND REASON 00C90101 ERQUAL 5007 TYPE 00000302 NAME DB01.SP01.X'02C00143' CONNECTION-ID=xxxx CORRELATION-ID=014.IFTSKS33 LUW-ID=DAPG.DAP2LU.E21D6E3802FF=0 DSNI005I -xxxx DSNILOGA LPL OR GRECP RECOVERY CANNOT 421 BE DONE FOR AUTOMATIC GRECP RECOVERY-ID = 1 OBJECT TYPE 00000210 OBJECT NAME DB01.SP01.00000045 REASON 00C90101 TYPE 00000210 NAME DB01.SP01.00000045
Temporary fix
Comments
APAR Information
APAR number
PH70056
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
D10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2026-02-10
Closed date
2026-04-03
Last modified date
2026-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO07402
Modules/Macros
DSNIFLRD DSNILOGA DSNIREDO
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"D10","Line of Business":{"code":"LOB70","label":"Z TPS"}}]
Document Information
Modified date:
03 April 2026