Step 2 - Define reporting database - syncsort_cobol_migration_manager - syncsort_clone_center - syncsort_space_recovery_system - syncsort_scc_monitor - syncsort_simulate_2000 - syncsort_allocation_control_center - Latest

Syncsort™ Storage Management COBOL Migration Manager Getting Started Guide

Product type
Software
Portfolio
Integrate
Product family
Syncsort™ software
Product
Syncsort™ Storage Management > Syncsort™ Cobol Migration Manager
Version
Latest
ft:locale
en-US
Product name
Syncsort Storage Management
ft:title
Syncsort™ Storage Management COBOL Migration Manager Getting Started Guide
Copyright
2025
First publish date
1991
ft:lastEdition
2025-12-05
ft:lastPublication
2025-12-05T05:06:06.635000

Prior to running the monitoring program, we need to create a database for the monitoring data.

COBOL Migration Manager relies on two datasets to generate reports. The first is a listing of COBOL programs (PROGI). We will identify the COBOL programs in Step 3 when we populate the PROGI dataset.

The second is a repository for jobs that have executed the COBOL programs that we are monitoring (PROGL).

Prior to populating the PROGI dataset, we need to initialize both the PROGI and PROGL datasets by running job CMMDEFIN in the SAMPLIB data set to create the program inventory database required for COBOL Migration Manager.