A fix is available
APAR status
Closed as program error.
Error description
REORG ABEND04E 00C200B8 with DSNDB01 in UT status. DSNT501I -**** DSNIDBET RESOURCE UNAVAILABLE CORRELATION-ID=021.OPNLGR00 CONNECTION-ID=DB3S LUW-ID=*** REASON 00C90086 TYPE 00000100 NAME DSNDB01 DSNT500I -**** DSNUAHR2 RESOURCE UNAVAILABLE REASON 00C90086 TYPE 00000100 NAME DSNDB01 DSNT500I DSNUGBAC - RESOURCE UNAVAILABLE REASON 00C200B8 TYPE 00000300 NAME DSNDB06 .SYSRTSTS.X'00000023'
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: ALL DB2 9 FOR z/OS AND DB2 10 FOR z/OS * * USERS WHO START THE DB2 DIRECTORY * * DATABASE IN UT MODE * **************************************************************** * PROBLEM DESCRIPTION: ABEND04E RC00E400E1 RC00E200B8 ON * * REORG OF DSNDB06.SYSCOPY WHEN DB2 * * DIRECTORY DATABASE IS STARTED FOR * * UT ACCESS * **************************************************************** * RECOMMENDATION: * **************************************************************** User started the DB2 directory database for UT (utility) access only: -START DB(DSNDB01) ACCESS(UT) A REORG utility on DSNDB06.SYSCOPY was submitted. The job abended with MSGDSNT500I - REASON 00C200B8 TYPE 00000300 NAME DSNDB06 .SYSRTSTS.X'00000023' MSGDSNU017I - UTILITY DATA BASE SERVICE MEMORY EXECUTION ABENDED, REASON=X'00E400E1' CAUSE=X'00C200B8' because REORG directed a real time statistics (RTS) update to DSNDB06.SYSRTSTS, and when DB2 tried to log this update (which requires writing to DSNDB01.SYSLGRNX), it failed due to the UT status of the DB2 directory. The problem was this RTS update was not recognized as a utility-driven update, even though it was, and this caused the update to fail if the UT status on the directory was held at the database level.
Problem conclusion
Code was added to utility SYSLGRNX services to ensure that code which properly identifies utility-driven updates was extended to cases where the entire directory database is started for UT access.
Temporary fix
Comments
APAR Information
APAR number
PM74674
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-09
Closed date
2012-12-20
Last modified date
2013-02-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK90550 UK90551
Modules/Macros
DSNUAHR2
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":"9.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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 February 2013