An IDMSDDDL step that updates APPLDICT with the DLODPROT member in CAGJSRC is failing with *+ E DC601997 CA-ENDEVOR/DB SPECIAL ERROR STATUS CODE 0897.
The DBNAME entry in the DBTABLE for APPLDICT is correct in that it includes the CCDB segment and is defined with INCLUDE SUBSCHEMA IDMSNWKA MAPS TO NDVRNWKA
CREATE
DBTABLE DBNAME1
INCLUDE SUBSCHEMA IDMSNWK? MAPS TO IDMSNWK? DBNAME APPLDICT
INCLUDE SUBSCHEMA IDMSCAT? MAPS TO IDMSCAT? DBNAME APPLDICT
INCLUDE SUBSCHEMA USVSUB0? MAPS TO USVSUB0? DBNAME DBX
INCLUDE SUBSCHEMA XDMSUB00 MAPS TO XDMSUB00 DBNAME DMA
INCLUDE SUBSCHEMA USDSUB00 MAPS TO USDSUB00 DBNAME DMLO
INCLUDE SUBSCHEMA ESXSUB00 MAPS TO ESXSUB00 DBNAME ENFORCER
INCLUDE SUBSCHEMA SSKSUB00 MAPS TO SSKSUB00 DBNAME MASTRKEY
INCLUDE SUBSCHEMA ESSSUB00 MAPS TO ESSSUB00 DBNAME SPG
;
CREATE
DBNAME DBNAME1.APPLDICT
MATCH ON SUBSCHEMA OPTIONAL
MIXED PAGE GROUP BINDS NOT ALLOWED
FOR GENERAL USE
INCLUDE SEGMENT APPLDICT
INCLUDE SEGMENT CCDB
INCLUDE SEGMENT SYSMSG
INCLUDE SEGMENT SYSSQL
INCLUDE SUBSCHEMA IDMSNWKA MAPS TO NDVRNWKA
;
I have modified this DBTABLE in various ways, trying to make it similar to that which all of our CVs use, but everything I’ve tried yields the same results.
The NDVRCNFG configuration table is also not being used.
Release : 19.0
Component : Endevor/DB for CA IDMS
Tried to recreate by hooking APPLDICT. Found DICTNAME= not necessary, being the default dictionary. And, batch will initialize a CCDB without a CV being brought up, even though the documentation says the online system should be used to seed the CCDB. All was working nicely.
Started walking code in NDVRSDBN. Turns out, there's an attempt to open a SYSIDMS DD. In this case, the customer is using a SYSIDMS load module. Created the load module, took SYSIDMS out of the JCL and got '*+ E DC601997 CA-ENDEVOR/DB SPECIAL ERROR STATUS CODE 0897'.
So, they should run the job with SYSIDMS DD in the JCL.
Please try coding SYSIDMS DD and the JCL.