During the conversion from FDS to FDB it can happen that the conversion completes successfully but the DBREVERS gets the below error message:
ADSHR001 4541 CA HEALTH CHECKER INITIALIZATION FAILED, RC=00000008 RSN=00000008
ADSDM175 4538 INITIALIZATION OF HEALTH CHECKS FAILED: MODULE ADSHR001 FAILED WITH RC= 4 RS= 8
ADSDC010 4302 FILES DATA SET SYSXXX.CA.DISK.TEST.FILES IS ASSIGNED TO CA-DATACOM DBID 651
ADSDC010 4302 FILES DATA SET SYSXXX.CA.DISK.TEST.FILES IS ASSIGNED TO CA-DATACOM DBID 651
ADSDC010 4302 FILES DATA SET SYSXXX.CA.DISK.TEST.FILES IS ASSIGNED TO CA-DATACOM DBID 651
ADSDC696 4424 UNABLE TO ESTABLISH DATABASE IDENTITY
Checking the expansion of the procedures included in the DBREVERS job, in the distributed members DMSSTPLB and DMSFILES there are 3 possible choices as reported below :
//* --- INCLUDE GROUP DMSSTPLB ---
//* TAILOR THIS SAMPLE MEMBER TO MEET YOUR REQUIREMENTS, AND THEN
//* COPY THE FINAL VERSION TO MEMBER NAME "DMSSTPLB" IN THE
//* PROCLIB YOU WILL USE FOR CA DISK.
//*
//* IN ORDER TO SUPPORT DMSAR AND OTHER STARTED TASKS, YOU WILL NEED
//* TO CREATE DMSFILES IN A SYSTEM PROCLIB. YOU CAN CREATE ALTERNATE
//* COPIES IN ADDITIONAL PROCLIBS AND REFERENCE THEM USING THE
//* JCLLIB STATEMENT.
//*
//* CHOOSE ONE OF THE FOLLOWING ALTERNATIVES
//*
//* 1. SYMBOLICS "Q" AND "DCAI" FOR INSTALLED ELEMENTS,
//* "C" AND "DCUS" FOR CUSTOMIZED MEMBERS
//*STEPLIB DD DISP=SHR,DSN=&C..T1.CCUWLOAD.DATACOM
//* DD DISP=SHR,DSN=&Q..LOADLIB
//* DD DISP=SHR,DSN=&DCUS..CUSLIB
//* DD DISP=SHR,DSN=&DCAI..CAAXLOAD
//*
//* 2. EXISTING SYMBOLICS "Q", "DCUS", "DCAI", FOR ALL LIBRARIES
//*STEPLIB DD DISP=SHR,DSN=&Q..LOADLIB
//* DD DISP=SHR,DSN=&Q..CUSLOAD
//* DD DISP=SHR,DSN=&DCUS..CUSLIB
//* DD DISP=SHR,DSN=&DCAI..CAAXLOAD
//*
//* 3. FIXED DATA SET NAMES
//*STEPLIB DD DISP=SHR,DSN=&Q..LOADLIB
//* DD DISP=SHR,DSN=CAI.DISK.CUSLOAD
//* DD DISP=SHR,DSN=CAI.ADRR.CUSLIB
//* DD DISP=SHR,DSN=CAI.ADRR.CAAXLOAD
//* -------- END DMSSTPLB --------
//* --- INCLUDE GROUP DMSFILES ---
//*---------------------------------------------------------------
//* NON VENGONO PASSATI I FILES DA QUESTA PROCEDURA MA VENGONO
//* RICHIAMATI DIRETTAMENTE DAI JCL
//*---------------------------------------------------------------
//* TAILOR THIS SAMPLE MEMBER TO MEET YOUR REQUIREMENTS.
//* COPY THE FINAL VERSION TO MEMBER NAME "DMSFILES" IN THE
//* PROCLIB YOU WILL USE FOR CA DISK.
//*
//* IN ORDER TO SUPPORT DMSAR AND OTHER STARTED TASKS, YOU WILL NEED
//* TO CREATE DMSFILES IN A SYSTEM PROCLIB. YOU CAN CREATE ALTERNATE
//* COPIES IN ADDITIONAL PROCLIBS AND REFERENCE THEM USING THE
//* JCLLIB STATEMENT.
//*
//* CHOOSE ONE OF THE FOLLOWING ALTERNATIVES:
//*
//* 1. EXISTING SYMBOLIC "Q"
//*FILES DD DISP=SHR,DSN=&FILES
//*
//*
//* 2. SEPARATE SYMBOLIC "F"
//*FILES DD DISP=SHR,DSN=&FILES
//*
//*
//* 3. FIXED DATA SET NAME
//*FILES DD DISP=SHR,DSN=&FILES
//*
//* -------- END DMSFILES --------
If all the 3 options are commented in and used at the same time, they cause redundant allocations :
ADSHR001 4541 CA HEALTH CHECKER INITIALIZATION FAILED, RC=00000008 RSN=00000008
ADSDM175 4538 INITIALIZATION OF HEALTH CHECKS FAILED: MODULE ADSHR001 FAILED WITH RC= 4 RS= 8
ADSDC010 4302 FILES DATA SET SYSXXX.CA.DISK.TEST.FILES IS ASSIGNED TO CA-DATACOM DBID 651
ADSDC010 4302 FILES DATA SET SYSXXX.CA.DISK.TEST.FILES IS ASSIGNED TO CA-DATACOM DBID 651
ADSDC010 4302 FILES DATA SET SYSXXX.CA.DISK.TEST.FILES IS ASSIGNED TO CA-DATACOM DBID 651
ADSDC696 4424 UNABLE TO ESTABLISH DATABASE IDENTITY
So only one choice should be commented in and used, according to the explanation provided.