How to handle when CA Datacom/DB 15.0 or 15.1 upgrade fails when UNIVERSAL Database or Area still exists?

Document ID : KB000016635
Last Modified Date : 21/02/2018
Show Technical Document Details
Introduction:

When the obsolete UNIVERSAL AREA and DATABASE still exist, the CA Datacom/DB Version 15.1 or 15.0 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 upgrade process:

Active Upgrade job BDACTDD2 or standard upgrade job BDUPG06 STEP6D.

 

Question:

How to handle when CA Datacom/DB 15.0 or 15.1 upgrade fails when UNIVERSAL Database or Area still exists?

Environment:
z/OS
Answer:

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. Refer to this knowledge document KB000040589 and run the same reports against this MUF to determine if UNIVERSAL entity as a FILE/RECORD pair is defined in to the DATA-DICT: 
KB000040589 "CA Datacom 14.0 upgrade job BDUPG07 STEP9E DDPFI30001 FILE NAME NOT CODED"
https://support.ca.com/us/knowledge-base-articles.TEC1111081.html 

Once UNIVERSAL FILE/RECORD pair exists, continue to delete the UNIVERSAL DATABASE and AREA.

Datacom/DB 15.0 upgrades require 15.0 PTF RO95060 and its SMP/e ++HOLD action.
Datacom/DB 15.1 upgrades require 15.1 PTFs RO95097 and RO98231 and its SMP/e ++HOLD action.

Note, as per the ++HOLD ACTION, after solution has been applied, run a DDUPDATE 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

Additional Information:

.

 

File Attachments:
TEC1146456.zip