Running Datacom/AD 15.1 active upgrade job AXACTDD2, DDUPDAT2 step gets RC 8 due to the following errors:
*-----------------------------------------------------------------------------------* * CODE ENTITY-TYPE,OCCURRENCE(VERS,PSWD,OVRD),STATUS,LOCK * * -ADD RELATIONSHIP,PROGRAM.DOCUMENT(,**,****),PGM-DOC-PRODUCE ; PROC * *-----------------------------------------------------------------------------------* *-----------------------------------------------------------------------------------* * * * CODE MP R A O C M * * 2000 MM N Y N S N * *-----------------------------------------------------------------------------------* **** ERROR **** RETURN CODE = DDPOAE0001 OCCURRENCE ALREADY EXISTS ERRORS DETECTED, NO MAINTENANCE APPLIED
*-----------------------------------------------------------------------------------* * CODE ENTITY-TYPE,OCCURRENCE(VERS,PSWD,OVRD),STATUS,LOCK * * -ADD RELATIONSHIP,PROGRAM.DOCUMENT(,**,****),PGM-DOC-READ ; PROC * *-----------------------------------------------------------------------------------* *-----------------------------------------------------------------------------------* * * * CODE MP R A O C M * * 2000 MM N Y N S N * *-----------------------------------------------------------------------------------* **** ERROR **** RETURN CODE = DDPOAE0001 OCCURRENCE ALREADY EXISTS ERRORS DETECTED, NO MAINTENANCE APPLIED
The MUF log already shows DataDictionary 15.0 so can this RC=0008 be ignored?
Release : 15.1
Component : DATACOM/AD
AXACTDD2 already executed.
This usually means that AXACTDD2 had already been submitted before. AXACTDD2 DDUPDAT2 tried to add two relationships between DATA-DICT DOCUMENT (new in DataDictionary version 15.0) table and the PROGRAM one. Those relationships already exist and is fine. As long as the MUF startup now shows version 15.0 for DD and DDD-DATABASE in messages DB00915I as expected, then yes you can ignore the RC=0008
DB00915I - CXX DBID 2 DATA-DICT DEFINITION VERSION 15.0 CHANGE LEVEL 0:cxxname
DB00915I - CXX DBID 15 DDD-DATABASE DEFINITION VERSION 15.0 CHANGE LEVEL 0:cxxname
DDUPDATE step might also receive a "DDPNTF0003 NOT FOUND" error.
This is also okay since the first time AXACTDD2 was submitted, it performed a delete on a particular area (FIL01) that Datacom/AD clients do not need. So when submitting this job again, it can not find the area it has already deleted.