Defining a new CA AutoSys Workload Automation conversion project

This procedure describes how to define a new CA AutoSys Workload Automation (AutoSys) conversion project. You can analyze the complexity of the conversion project by viewing the assessment report.

Before you begin

Ensure the following:

• Create and export definitions files, as described in Setting up a CA Autosys Workload Automation project.

  This procedure describes how to extract CA AutoSys Workload Automation (AutoSys) data before starting a new conversion project. After extracting data, you can then define a new conversion project.

  For AutoSys recommended practices, see CA AutoSys recommended practices.

  To extract AutoSys data:

  1. Create the following definitions file by running the following commands:
     • .JIL jobs definitions: autorep –j ALL –q
     • .TZO time zones definitions: autotimezone –l
     • .CAL calendars definitions: autocal_asc –E autosys.STANDARD_CAL –s ALL
  2. Open the Conversion Tool and import the files, as described in Defining a new CA AutoSys Workload Automation conversion project.
• Create a new project, as described in Creating a new Conversion Tool project.

To define a new CA AutoSys conversion project:

1. From the CA AutoSys Workload Automation Load Data window, in the Import Scheduling Data area, complete the Import scheduling data parameters.

   The following table describes the Import scheduling data parameters when defining a new Autosys project.

   Parameter	Description
   Jobs definitions (JIL)	(Mandatory) Enables you to locate and select the job definitions file, .JIL by clicking on .
   Time zone definitions	Enables you to locate and select the time zones definitions file, .TZO by clicking on .
   Calendar definitions	Enables you to locate and select the standard calendar definitions file, .CAL by clicking on .
   Extended calendar definitions	Enables you to locate and select the extended calendar definitions file, .CAL by clicking on .

   NOTE: Only standard calendar conversion is supported by the Control-M Conversion Tool. Cyclic and extended calendars require manual definition in the Control-M environment. For more information, see Job scheduling in Using Control-M.

2. Click Import.

   The data is loaded into the Conversion Tool and in the Assessment Report window, a summary of the imported data appears. For more information, see Data evaluation.

3. Click Next.

   The Run Conversion window appears.

4. Select Run conversion or Load existing conversion results.

   For more information about running conversion, see Data conversion.

5. Click Next.

   The Conversion Settings window appears.

6. Continue converting project to Control-M by reviewing and changing any conversion settings, as described in Conversion settings.

   NOTE: In the Validation phase, you can compare your scheduler's forecast report to the Control-M forecast report created during validation. To create the report, use any of the report parameter files below.

   • To report from a specific date to infinity, use: job_depends -t -J ALL -F "mm/dd/yyyy".
   • To display all jobs scheduled to run between two dates, use: job_depends -t -J ALL -F mm/dd/yyyy hh:mm -T mm/dd/yyyy hh:mm. For example, job_depends -t -J ALL -F 01/03/2009 10:01 -T 02/15/2009 19:01.
   • To report for a specific date, use: job_depends -t -J ALL -F mm/dd/yyyy hh:mm -T mm/dd/yyyy hh:mm. For example, job_depends -t -J ALL -F 02/01/2009 00:01 -T 02/01/2009 23:59.

   For more information on validation, see Data validation.