Utility and Maintenance Functions › Backing Up the SCDS

Backing Up the SCDS

Because the SCDS file contains the index to the SMF data in your history files, you should back it up often -- preferably once a day. This way, if a problem should arise in this file, you are able to restore the SCDS with a minimal loss of information.

The provided sample JCL member CASFBKUP is illustrated below:

//CASFBKUP JOB (ACCTINFO),PGMR,CLASS=A,MSGCLASS=A
//*
//*THIS SAMPLE JCL PERFORMS A BACKUP OF CA SMF Director
//*CONTROL DATA SET (SCDS).
//*
//*NOTE: EDIT AS PER INSTALLATION STANDARDS
//*
//STEP1    EXEC PGM=SMFD,REGION=2M,PARM=BACKUP
//STEPLIB  DD DISP=SHR,DSN=CASFLOAD
//SYSPRINT DD SYSOUT=*
//SYSXDIAG DD SYSOUT=*
//SCDS     DD DISP=SHR,DSN=CAI.SMFDIR.SCDS
//SCDSBACK DD DSN=CAI.SMFDIR,SCDSBKUP(+1),UNIT=CART,
//            DISP=(NEW,CATLG,DELETE)
/*
//

Note that the new SCDS backup data set is sequential and can reside on tape or disk. However, it must be backed up by the SMFD program rather than by other file copy utilities.

The following is an example of the audit trail report produced by executing the CASFBKUP sample JCL:

CA                            AUDIT TRAIL REPORT          SMFD  PAGE   1
CA SMF Director r12 SPn                       SYSA  22 DEC yyyy 17:52:19

CAF53I SCDS BACKUP COMPLETE, 24 BLOCKS COPIED:
CAF54I 3 CNFC RECORDS
CAF54I 1 CNFA BLOCK
CAF54I 1 CNFN BLOCK
CAF54I 1 CTLR BLOCK
CAF54I 123 DPIX RECORDS
CAF54I 1734 DSIR BLOCKS
CAF54I 536 FREE BLOCKS
CAF54I 1 FSPR RECORD
CAF54I 24 TOTAL BACKUP FILE RECORDS

CAF29I RUN COMPLETE

Important! CASFBKUP abends may not be recognized because normal abend notification may not be given. Unless job output is examined, problems would not be apparent. To resolve this problem, change the EXEC PARM in CASFBKUP to PARM='NOSTAE,BACKUP'.