In this example, KEY SYSCONSTRSRC is seen in the error message, but it may be a different KEY. The problem is caused by a broken RELATIONSHIP from either KEY to TABLE or TABLE to KEY.
How to address DDPUPN004 error running DDUPDATE -UPG KEY,ALL,ALL(version)?
Environment
z/OS
Resolution
To determine the cause, run the following DDUPDATE or DDUTILTY request for the version: -DEF PATH,P1 -DEF TRACE,KEY.TABLE,$INTERNAL -END -RPT START,KEY,ALL.ALL(version),P1 -RPT INDENT -END
The report may show one of two things….
1. If the TABLE to KEY relationship is missing but the KEY to TABLE relationship exists, the report will show TBL with “* * nnn” in the report.
For example:
KEY SYSTABAUTH.GRANTEE-KEY T T001 ATBK2 020
TBL SYSTABAUTH * *001 000 ENTITY MISSING
If no “* *nnn” in the DD report, the TABLE to KEY relationships do exist.
2. Then, if the relationship from the KEY to TABLE is missing, the report will show only the KEY occurrence and no TBL occurrence.