Ensure the SETSYS CDSVERSIONBACKUP(BACKUPCOPIES(x)) command in the DFSMShsm ARCCMDxx PARMLIB member specifies a value that is equal to or greater than the owner- or installtion-specified critical value of backup copies. If the BACKUPCOPIES value is increased and the control data sets are backed up to DASD, ensure that each backup data set is pre-defined.

If the SETSYS CDSVERSIONBACKUP(BACKUPCOPIES(x)) command in the DFSMShsm ARCCMDxx PARMLIB member specifies a value equal to or greater than the critical value, issue a QUERY CDSVERSIONBACKUP command to DFSMShsm and determine the BACKUPCOPIES value reported in the ARC0376I message. If this value is not consistent with the value in the ARCCMDxx PARMLIB member, either the SETSYS CDSVERSIONBACKUP(BACKUPCOPIES(x)) command was issued dynamically to DFSMShsm or the ARCCMDxx PARMLIB member may have been modified since the last time DFSMShsm was initialized.

Modify the SETSYS CDSVERSIONBACKUP(BACKUPCOPIES(x)) command in the ARCCMDxx parmlib member and issue the command dynamically to DFSMShsm. Confirm the changes by issuing a QUERY CDSVERSIONBACKUP command to DFSMShsm and reviewing the BACKUPCOPIES value reported in the ARC0376I message. As noted, CDS backups to DASD require that all CDS backup data sets be pre-allocated. Data sets may need to be allocated if the BACKUPCOPIES value has been increased.

For more information about DFSMShsm control data set backup, see Defining the Backup Environment for Control Data Sets in DFSMShsm Data Sets of z/OS DFSMShsm Implementation and Customization Guide.

For more information about modifying check parameters, see IBM Health Checker for z/OS User's Guide.