Datacom/DB 15.1 upgrade fails when UNIVERSAL Database or Area still exists

Products

• Datacom
• Datacom/DB

Issue/Introduction

When the obsolete UNIVERSAL AREA and DATABASE still exist, the Datacom/DB Version 15.1 upgrade from version 14.0 will fail when running CABDSAMP(AD15TRN) DDUPDATE transactions:

-UPG AREA,ALL.ALL(TEST)
1500 URI-REUSE,&
-END

*** ERROR **** RETURN CODE = DDPAR10001 DATACOM-NAME MISSING OR INVALID

This error will occur for either Active Upgrade job BDACTDD2 or standard upgrade job BDUPG06 STEP6D.

Resolution

If UNIVERSAL exists, it must exist as a FILE/RECORD pair. 

Since the situation may have been overlooked during the upgrade to Datacom/DB 14.0, this needs to be addressed first.

Run the following DDUTILTY report to find out if that UNIVERSAL entity exists as a FILE/RECORD pair in DATA-DICT and not as a TABLE entity:

-USR DATACOM-INSTALL,NEWUSER

-DEF PATH,P1

-DEF TRACE,FILE.RECORD,$INTERNAL

-END

-RPT START,FILE,UNIVERSAL(ALL),P1

-RPT INDENT

-END

 

If "NOT FOUND" condition occurs or if a user table with entity-name UNIVERSAL exists, open a ticket so support can provide a program called DDUNILM that will transform this Table into a FILE/RECORD pair. DDUNILM is the "UNIVERSAL" table clean up program.

 

Once UNIVERSAL FILE/RECORD pair exists, continue to delete the UNIVERSAL DATABASE and AREA. Datacom/DB 15.1 upgrades require 15.1 PTFs RO95097 and RO98231 and its SMP/e ++HOLD action. As per the ++HOLD ACTION, that is also attached to this article as a downloadable file, run a DDUPDATE after the solution has been applied with the following to delete the UNIVERSAL database and area. Note that no version should be specified: 

 

-USR DATACOM-INSTALL,NEWUSER
-DEL AREA,UNIVERSAL
-END
-DEL DATABASE,UNIVERSAL
-END