A fix is available
APAR status
Closed as program error.
Error description
Running a CHECK DATA on a PBG tablespace using the EXCEPTIONS keyword, the tablespace is not left CHECK PENDING when the maximum number of exceptions is met and there is an index on the foreign keys of the child table.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users * * of CHECK DATA utility with EXCEPTIONS * * keyword * **************************************************************** * PROBLEM DESCRIPTION: CHECK DATA with EXCEPTIONS against a * * partitioned table space with an * * indexed foreign key and referential * * integrity (RI) violations reset * * check pending (CHKP) for the partition * * with violations when reaching the * * EXCEPTIONS limit. * **************************************************************** * RECOMMENDATION: Apply corrective PTF when available. * **************************************************************** User ran a CHECK DATA utility with EXCEPTIONS n against a partitioned table space in CHKP with an indexed foreign key. MSGDSNU733I was issued indicating a referential integrity violation was found and the utility ended with RC8 because the EXCEPTIONS limit was met. However, the table space was no longer in CHKP because the CHECK DATA utility erroneously reset the CHKP status for both the partition in which it hit the EXCEPTIONS limit and for the partitions which it had not yet finished processing. This problem does not exist if the EXCEPTIONS limit is not met. Additional Keywords: DSNU733I DSNU971I MSGDSNU971I DSNU973I MSGDSNU973I DSNU731I MSGDSNU731I
Problem conclusion
CHECK DATA EXCEPTIONS code has been modified to set and reset CHKP correctly.
Temporary fix
Comments
APAR Information
APAR number
PM73015
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-17
Closed date
2012-12-16
Last modified date
2013-02-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK90405 UK90406
Modules/Macros
DSNUKIFK DSNUKNFK
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:
13 February 2013