I accidentally ran AXACTDD2 a second time and STEP2C got the following error:
*-----------------------------------------------------------------------------------*
* 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
The MUF log shows already shows 15.0 so can I ignore this RC=0008?
Release : 15.0
Component : CA CIS for VSE
This usually means that AXACTDD2 had already been submitted before. AXACTDD2 STEP2C tried to add a relationship between DATA-DICT tables DOCUMENT ( new in version 15.0) and the PROGRAM table. That relationship already exists 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:CA7TEST
DB00915I - CXX DBID 15 DDD-DATABASE DEFINITION VERSION 15.0 CHANGE LEVEL 0:CA7TEST
STEP2B might also receive a RC0004 error DDPNTF0003 not found.
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.