Control-M Conversion utilities

The types of Control-M Conversion are as follows:

CalendarsDuplicatesRemoval Utility

You might have a substantial number of Control-M Rule Based Calendars (RBCs) with identical data after converting your data to Control-M. The CalendarsDuplicatesRemoval utility removes all identical RBCs and updates Control-M data, which references these remaining RBCs.

After converting your data to Control-M, the Conversion Tool generates the following files:

  • Data XML

  • Calendar XML

The files are located in <conversion home>\workarea\datasources\<name of conversion project>\CONVERSIONS\<name of conversion project>. You can also access these files directly from the Load to Control-M window by clicking Open Conversion result.

Alternatively, if you have imported your data into Control-M, you can use the exportdeffolder and exportdefcal utilities to export the Data and Calendar XML.

The CalendarsDuplicatesRemoval utility reviews these files and generates the following files:

  • updateCalendars.xml: Contains the remaining unique RBCs.

  • updateCtmData.xml: Contains the updated Control-M data with new references to the remaining RBCs.

  • calDuplicatesRemovalReport.xlsx: Contains a list of the names of the remaining RBCs and the names of the RBCs that have been removed.

You can then import the updateCalendars.xml and updateCtmData.xml files into Control-M.

Running the CalendarsDuplicatesRemoval utility

The following procedure describes how to run the CalendarsDuplicatesRemoval utility.

Before you begin

Review the number of RBCs that have been created and whether they contain duplicate information.

Begin

  1. Extract the following files and move them to a temporary file:

    • Calendars.xml

    • draft.xml

  2. Open a command prompt and go to the <conversion home>\scripts\general\CalendarsDuplicatesRemoval directory.

  3. Type the following command:

    CalendarsDuplicatesRemoval.bat -calendarFile <calendar file path> –ctmData <Control-M data file path> -outputDirectory <output file path>

    CalendarsDuplicatesRemoval.bat -calendarFile c:\Temp\calendars.xml –ctmData c:\Temp\draft.xml -outputDirectory c:\NewCal\

CaldendarsDuplicatesRemoval parameters

The following table describes the CalendarsDuplicatesRemoval parameters:

Parameters

Description

CalendarFile

Defines the path to the Control-M calendar XML file.

ctmData

Defines the path to Control-M data that contains the input calendar file references

outputDirectory

(Optional) Defines the directory where the CalendarDuplicatesRemoval output is created.

Integrating between Broadcom ESP and Control-M with the Bridge Builder Tool

This procedure describes how to run the Bridge Builder Tool from the CLI.

This utility automates a Bridge creation between Broadcom ESP and Control-M, which reduces the manual work involved, when converting Broadcom ESP data to Control-M. The bridges between Broadcom ESP and Control-M are needed during the Conversion process when part of the flow is converted and running in Control-M and part is still running in Broadcom ESP.

The Bridge builder utility gets Broadcom ESP and Control-M bridges definitions information as input data and builds the following:

  • Control-O rules: Implements the Broadcom ESP to Control-M Bridges

  • Control-M MF Jobs: Implements the Control-M to Broadcom ESP bridges

Before you begin

Verify which bridges need to be created between Broadcom ESP and Control-M.

Begin

  1. Create a bridges definitions csv file that contains the following information:

    • Broadcom ESP APPL/Job name

    • CTM Job full path name (Folder/Job name)

    • Bridge Type, which supports the following options:

    • ESPDS_CTMDS (bridge from ESP DS to CTM DS)

    • ESPDS_CTMMF (bridge from ESP DS to CTM MF)

    • ESPMF_CTMDS (bridge from ESP MF to CTM DS)

    • ESPMF_CTMMF (bridge from ESP MF to CTM MF)

    • CTMDS_ESPMF (bridge from CTM DS to ESP MF)

    • CTMMF_ESPDS (bridge from CTM MF to ESP DS)

    • CTMDS_ESPDS (bridge from CTM DS to ESP DS)

    • CTMMF_ESPMF (bridge from CTM MF to ESP MF)

      For more information, see Bridges Information File Example.

  2. Set the bridges conditions prefixes you want to use per bridge type in the bridgeConditionsPrefixes.cfg file in home>\tools\CAESP\BridgeBuilder.

  3. Create the Control-O rule template that you want to use as input for the bridge builder by using the cto_rule_template file in the home>\tools\CAESP\BridgeBuilder\Examples folder.

  4. Create the Control-M MF SMART folder and job data that you want to use as input for the bridge builder, by using the ctm_mf_data_template file in the home>\tools\CAESP\BridgeBuilder\Examples folder.

    The templates contain place holders values (example: @MSG_ID@ ) that are being replaced by the bridge builder. They should be kept in the same format.

  5. Open a command prompt and go to the <conversion home>\tools\CAESP\BridgeBuilder directory.

  6. Type the following command:

    bridgebuilder.bat -bridgesData bridgesInfo.csv -ctmTemplate ctmTemplate.xml

    - ctoTemplate ctoTemplate.txt -outputDirectory c:\BridgeOutput\

Bridge Builder CLI Parameters

The following table describes the Bridge Builder parameters:

Parameters

Description

bridgesData

Defines the path to csv file with the required bridges information. For more information, see Bridges Information File Example.

ctmTemplate

(Optional) Defines the path to Control-M MF data template that will be used to create Control-M Mainframe Bridges Jobs.

ctoTemplate

(Optional) Defines the path to Control-O template that will be used to create Control-O Bridges rules.

outputDirectory

(Optional) Defines the path to the directory where BridgeBuilder outputs is created.

Bridges Information File Example

Broadcom ESP Job, CTM Job, Bridge Type

APPL1\JOB1,FOLDER1\JOB1,ESPDS_CTMDS

APPL2\JOB2,FOLDER2\JOB2,ESPMF_CTMMF

You must keep the headers (first line).

Bridge Builder Outputs

The Bridge Builder creates three outputs:

  • Bridge_Trigger_Jobs.xml: Holds the new MF folder that contains all the additional MF jobs that trigger ESP jobs.

    This file is created only if bridges that trigger Broadcom ESP jobs after Control-M jobs are needed.

  • CTORULS: A text file that holds all the Control-O Rules definitions created for triggering Control-M jobs after Broadcom ESP jobs ends.

  • AdjustCtmConditions.xlsx: An excel file that contains the names of all Control-M jobs that need to rename their existing In/Out Condition to fit the Bridges Builder outputs.

Implementing the Bridges

This procedure describes how to implement the bridge outputs created by the bridge builder.

Begin

  1. Copy CTORULS file to the MF Control-O Rules Library in text mode.

  2. Add Bridge_Trigger_Jobs.xml to the workspace that contains the Control-M converted data that need to trigger Broadcom ESP jobs and check it in.

  3. Review the AdjustCtmConditions.xlsx file and update the existing In/Out Conditions as required.