Deleting impact analysis data

You can delete impact analysis data for source files no longer used.

Before you begin

These instructions assume you have already generated impact analysis data as described in Gathering initial impact analysis data.

About this task

You can delete entries associated with specified source files from the impact analysis data by executing the BCCIADEL program. The files for which associated dependency entries are to be deleted are specified in a file with the SYSIN DD name. The file names are specified as dataset name(member name) as shown in the following sample JCL. In this sample, RCC.IA.TSCLOAD is the z/OS® Extensions load library and ADMIN.VSAM1.CCZVSAM.COPY.NUPATH1 and ADMIN.VSAM1.CCZVSAM.CALL.NUPATH1 are the data sets containing the impact analysis data.

//ADMIN JOB ,
// MSGCLASS=H,MSGLEVEL=(1,1),TIME=(,4),REGION=70M
//GO    EXEC   PGM=BCCIADEL
//STEPLIB  DD DSN=RCC.IA.TSCLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=* 
//SYSTERM  DD SYSOUT=* 
//SYSOUT   DD SYSOUT=* 
//PLIDUMP  DD SYSOUT=* 
//SYSABEND DD SYSOUT=* 
//SYSUDUMP DD SYSOUT=* 
//COPYAIX1 DD DSN=ADMIN.VSAM1 .CCZVSAM.COPY.NUPATH1,DISP=SHR 
//CALLAIX1 DD DSN=ADMIN.VSAM1 .CCZVSAM.CALL.NUPATH1,DISP=SHR  
//SYSIN    DD * 
ADMIN.PROJ2.COBOL.SRC(PGMA) 
ADMIN.ALLPROJ.PLI.SRC(PGM7) 
/*