Introduction to Control-M Conversion

Control-M Conversion enables you to convert your workflows from your current scheduler or application to Control-M.

Converting Workflows to Control-M

This procedure describes how to convert your workflows to Control-M.

Begin

  1. From your current scheduler or application, extract the data as described in Source Data Extraction.

    If you can not find your scheduler in Source Data Extraction, use Control-M Self Conversion to convert your data.

  2. Convert the extracted data to Control-M data and load it into the Control-M environment, as described in Converting to Control-M.

  3. Resolve conversion issues inside the Control-M environment, as described in Post-Processing.

Setting Up the Conversion Tool

This procedure describes how to setup the Conversion Tool.

Begin

  1. Download the Conversion Tool from the following link:

    Conversion Tool Download

  2. Unzip the file.

  3. Open Conversion.bat

     

Verification Tool

Control-M Conversion includes a Verification Tool, which enables you to compare scheduler forecasts and execution history reports with Control-M forecast and execution reports. The report helps you to verify that the definitions in Control-M are functionally equivalent to those in the legacy tool.

To access the Verification Tool, from the click the drop-down list, select Verification Tool.

The Verification Tool is relevant for the following schedulers:

  • ASG-Zeke

  • ASG-Zena

  • Broadcom Dollar Universe

  • Broadcom-AutoSys

  • Broadcom-ESP

  • Broadcom Unicenter WLM (TNG)

  • Broadcom-7

  • IBM TWS (DS & MF)

The Verification Tool produces a report for each date, which indicates the following:

  • Jobs that have run or are planned to run by the scheduler but are missing from Control-M.

  • Jobs that have run or are planned to run by Control-M but are missing from the scheduler.