Prior to running the monitoring program, we need to create a database for the monitoring data.
COBOL Migration Manager relies on a dataset to generate reports. It is a listing of COBOL programs (PROGI). We will identify the COBOL programs in Step 3 when we populate the PROGI dataset. Prior to populating the PROGI dataset, we need to initialize it by running job CMMDEFIN in the SAMPLIB data set to create the program inventory database required for COBOL Migration Manager.
//JOBNAME JOB ... (RC=0 EXPECTED)
//*
//* THIS JOB CREATES THE CMM INVENTORY DATA SETS. THE FOLLOWING JCL
//* REQUIRES SEVERAL MODIFICATIONS BEFORE THE JOB CAN BE SUBMITTED.
//*
//* 1) JOBCARD - USE A VALID JOBCARD FOR YOUR ENVIRONMENT
//* 2) VOLUME - SELECT A VOLUME(######) FOR THE VSAM DATA SETS
//*
//*
//* OPTIONAL CHANGES
//* A) STORCLAS - FOR SMS-MANAGED VSAM DATA SETS, REPLACE THE
//* VOLUMES(######) STATEMENT WITH A VALID STORCLAS
//* AS STORAGECLASS(%%%%%%%%)
//*
//STEP01 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DELETE DTS.R72.PROGI CLUSTER
SET MAXCC=0
//*
//STEP02 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER( +
NAME(DTS.R72.PROGI) +
VOLUMES(######) +
SHAREOPTION(2) KEYS(214 3) +
CYLINDERS(10 10) INDEXED +
RECORDSIZE(1000 1000) +
)
/*
//*
//* INITIALIZE PROGRAM INVENTORY DATA SET
//*
//STEP03 EXEC PGM=CMMINPRI
//STEPLIB DD DISP=SHR,DSN=DTS.R72.LOADLIB
//PROGI DD DISP=SHR,DSN=DTS.R72.PROGI
//SYSPRINT DD SYSOUT=*
//*
//