Converting AutoSys jobs to Control-M - recommended practice
This procedure describes the recommended practices for converting AutoSys jobs to Control-M.
To convert AutoSys jobs to Control-M:
Before converting jobs, it is recommended that you do the following:
A full scan of all scripts run by AutoSys, which enables you to look for occurrences of AutoSys command lines, executables and variables within the scripts.
Identify any external interfaces to, for example, monitoring and alerting tools, reporting tools, help desk incident management tools and CMDB’s.
A precursory scan of the JIL file. The conversion tool does not handle Job_terminator and box_terminator statements. Before commencing the conversion, you should scan the JIL extract file keywords. For more information, see CA AutoSys Keywords.
Create AutoSys virtual machines, which are equivalent to Control-M host groups. Obtain a list from AutoSys of all virtual machine names and the hosts that constitute the group, which can be obtained by running the following AutoSys command:
Create AutoSys variables. These are equivalent to Control-M variables and can be embedded in the job definition or script. Obtain a list of AutoSys variables and convert these manually to Control-M Variables for a one off installation. To obtain a list of AutoSys variables, run the following AutoSys command:
From the Conversion Settings window, in the General tab in the Job Type Conversion area, select Convert all jobs to Control-M command line jobs. For more information, see Setting General rules.
If you have Control-M for Advanced File Transfer, select AFT in the File Watcher Type otherwise use the Ctmfw utility which matches AutoSys. For more information, see Setting additional CA AutoSys Workload Automation rules.