Chapter 7. Case studies 143
Enter command for VVDS fixer
Enter BCS record name to be deleted.
C type BCS record DELETED. Name=YCJRES1.CRPLUS.TESTE.E000024
T type BCS record DELETED. Name=YCJRES1.CRPLUS.TESTE.E000024.DATA
A BCS record can also be deleted with the Catalog RecoveryPlus ZAP BCS
DELETE command, by specifying the key of the record to be deleted (a cluster
sphere name), and the BCS name from which the record is to be deleted.
the record with that key is deleted.
Example 7-24 CR+ ZAP BCS DELETE to delete a BCS record
//YCJRES1Z JOB MSGCLASS=X,NOTIFY=&SYSUID,RESTART=*
//S1 EXEC PGM=CAT00010
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
ZAP BCS(UCAT.CRPLUS1) -
CAT01001I Catalog RecoveryPlus MAINSTAR SOFTWARE CORPORATION 02 OCT 2001 PAGE:1
CAT08213I RECORD DELETED
CAT08000I ZAP FUNCTION COMPLETE. RETURN CODE 0
CAT01009I Catalog RecoveryPlus EXECUTION COMPLETE. HIGHEST RETURN CODE WAS 0
7.9 Case study #9: Preventive maintenance
This case study demonstrates using the Catalog RecoveryPlus DIAGNOSE
command in a way that you can establish true ICF catalog preventive
maintenance. It uses two commands that can run on a regularly-scheduled
basis, with fixes automatically created for problems encountered.
The commands are DIAGNOSE BCS-VVDS and DIAGNOSE VVDS-BCS, both
specified with masking values for the BCSs and VVDSs and the ALLRELATED
keyword. These two features permit these commands to be run over and over
again, regardless of changes made to the ICF catalog and disk environment.
Example 7-25 illustrates a CR+ DIAGNOSE BCS-VVDS command. This
command compares all records in the selected BCSs, to determine if they each
have corresponding VVR/NVR records in the appropriate VVDS. In this case, the
COMPAREBCS mask selects all BCSs that match UCAT.CRPLUS*. The