The conversion process from a legacy product to Control-M is a complex one, and all aspects must
be addressed to reduce the risk involved. There are several steps in this process. 
1. Planning
2. Installation of the latest version of the conversion tool (including up-to-date maintenance/
   patches). 
	
After tailoring the conversion parameters, extracting the data from the legacy product, and 
running the tool, the following is produced: 
*  An XML file containing Job Schedule Definitions
*  An XML file containing Calendar definitions
*  A report containing informational and error messages indicating any manual adjustments which
   must be reviewed and applied if necessary. 

3. Import the XMLs into Control-M/EM, using the Planning GUI (for importing scheduling definitions)
   and utility defcal (for importing calendars).  Next use the Planning GUI and Find and Update 
   feature, to resolve all issues indicated in the reports.  Further details regarding these 
   activities can be found in the appropriate legacy Conversion guide (where relevant). 

Once all manual adjustments are completed, and spot checks have been made to verify that the 
Control-M job definitions are similar to the corresponding legacy product definitions 
including all ordering related issues like System Daily, User Daily and File triggers) the Forecast 
Verification phase can be started. 

In the Forecast Verification phase, several strategic dates (mid-week day, weekend day, start of 
the month, end of the month, start of quarter, end of quarter, holidays, etc.) should be selected 
and a legacy forecast report for each of those dates should be produced. 

The Conversion Verification tool gives the user the ability to compare these legacy forecast reports
to a Control-M forecast for each date selected. The tool produces a report for each date, which 
indicates which jobs are planned to be run by the legacy tool but are missing in Control-M, and 
which jobs are planned to be run by Control-M but are missing in the legacy report. For each job 
which appears in the report, the user should do the following: 

*  Review the Control-M job definition in EM
*  Compare the Control-M  job definition to the definition in the legacy tool 
*  Modify the job's scheduling criteria, so that the job will be scheduled correctly. 

After each set of changes, all the dates should be re-processed by the tool to validate the 
adjustments and as a regression test to verify that no harm was done to the other dates. 

4. Once everyone is satisfied with the forecast comparison report's content, the conversion process
   should proceed to the next step of parallel execution where the jobs are running in dummy mode (this
   is achieved by using Find and Update to flag all jobs as 'Run as Dummy). For this stage, the user 
   should produce a daily execution report from the legacy tool, and use the Conversion Verification tool
   to run a daily comparison with the execution report to verify that both schedulers run the same jobs. 
   Once all the report differences are reconciled or explained to the user's satisfaction, the Control-M 
   job can be moved to production. 

Running the Conversion Verification tool
----------------------------------------
The Control-M Conversion Verification tool can be run either via batch mode (mainly used for regression
tests) or by means of a Graphical User Interface (GUI). 

The GUI is invoked by running or double clicking on file verification.bat in the Verification Tool root 
directory. 

Once the GUI is displayed, the user must complete all the required fields, and click on the 'Run' button. 
The first three fields are the details of the Control-M/EM that is being used. In the next two fields, 
the user should select the legacy tool (Zeke, Zena, ESP, etc.) that is in use at the site, and the phase
- Forecast or Execution - that is currently under verification. (The Execution phase is when Control-M 
is running in parallel to the legacy tool with all jobs in dummy mode).

Based on the selection of the legacy tool and the verification phase, some other fields may appear on 
the screen (click on the associated help icon to display description of these fields).  

The final field on the screen is the target directory for the output report. 

Once all fields are properly filled in, i.e., no fields are marked as containing illegal values (red 
boundaries), the user has two options: 
*  The first option is to click the 'Run' button which executes the tool interactively. All run 
   messages are displayed in the Log area. Subsequently clicking the 'Open' button will display the 
   output report which is in Excel format. If Excel is not installed on the machine, the equivalent CSV 
   report is opened in a text editor. 
*  The second option is to copy the displayed command line using the 'Copy' button, and paste it into a
   .BAT file.  This option is useful for running regression tests when required. 

This process can be used for as many days as required, both in the Forecasting and Execution phase. 

Note: The above Excel file is created as a text XML file. Each time such a file is opened a confirmation 
pop-up is displayed. To eliminate this pop-up, the user can do one of the following: 

*  Run the supplied .reg file in: ThirdParty\do not ask before opening xml as xls.reg 
*  Manually add the following key in the Registry: 
 
        [HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Excel\Security] 

   with the value: 

        "ExtensionHardening"=dword:00000000 