A fix is available
APAR status
Closed as program error.
Error description
A REPORT RECOVERY utility on catalog tablespaces, including DSNDB01.SYSUTILX gets an abend0C4 in DSNUGSUU +0804 when the statement referencing DSNDB01.SYSUTILX is preceeding other utility statements that reference a list. i.e. this form will get the abend: LISTDEF LIST1 INCLUDE TABLESPACE DSNDB01.DBD01 LISTDEF LIST2 INCLUDE TABLESPACE DSNDB01.SCT02 REPORT RECOVERY TABLESPACE DSNDB01.SYSUTILX CURRENT REPORT RECOVERY TABLESPACE LIST LIST1 CURRENT REPORT RECOVERY TABLESPACE LIST LIST2 CURRENT . If moving the statement referencing SYSUTILX at the bottom the abend does not occur: LISTDEF LIST1 INCLUDE TABLESPACE DSNDB01.DBD01 LISTDEF LIST2 INCLUDE TABLESPACE DSNDB01.SCT02 REPORT RECOVERY TABLESPACE LIST LIST1 CURRENT REPORT RECOVERY TABLESPACE LIST LIST2 CURRENT REPORT RECOVERY TABLESPACE DSNDB01.SYSUTILX CURRENT
Local fix
Move the statement for DSNDB01.SYSUTILX at the bottom.
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS * * users of utilities. * **************************************************************** * PROBLEM DESCRIPTION: ABENDS0C4 RC38 DSNUGSUU OFFSET0802 * * during a REPORT RECOVERY on a list of * * objects. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** An ABEND0C4 RC38 at DSNUGSUU + '0802'x can occur when multiple REPORT RECOVERY statements are executed on the directory objects in the same job step as follows: LISTDEF LIST1 INCLUDE TABLESPACE DSNDB01.DBD01 LISTDEF LIST2 INCLUDE TABLESPACE DSNDB01.SCT02 REPORT RECOVERY TABLESPACE DSNDB01.SYSUTILX CURRENT REPORT RECOVERY TABLESPACE LIST LIST1 CURRENT REPORT RECOVERY TABLESPACE LIST LIST2 CURRENT The problem occurred on the last REPORT RECOVERY statement because the last REPORT RECOVERY was trying to access the SYSIBM.SYSUTILX but there was no record in this directory table for all the utilities in this job step. It is because the first REPORT RECOVERY was against the table space DSNDB01.SYSUTILX. The same problem can happen for other utilities executing in the same job step and some of them are running on the following directory objects: DSNDB01.DBD01 DSNDB01.SYSUTILX SYSIBM.DSNLUX01 SYSIBM.DSNLUX02
Problem conclusion
Utility code has been modified to correct the aforementioned problem.
Temporary fix
Comments
APAR Information
APAR number
PI77086
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-23
Closed date
2017-05-03
Last modified date
2017-06-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI77318 UI47131 UI47132
Modules/Macros
DSNUGSUU
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":"11.0","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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 June 2017