Defining a new IBM Tivoli Workload Scheduler conversion project

This topic describes how to define a new IBM Tivoli Workload Scheduler (TWS) conversion project. You can also analyze the complexity of the conversion project by viewing the assessment report.

For more information about creating a new conversion project, see Creating a new Conversion Tool project.

Before you begin

Ensure the following:

• Create and export Definition files in the Tivoli environment, as described in Extracting IBM Tivoli Workload Scheduler data.
• Define a new project, as described in Creating a new Conversion Tool project.

To define a new TWS conversion project:

1. From the IBM Tivoli Workload Scheduler - Load Data window, in the Import Scheduling Data area, click to locate and select the Import Scheduling Data parameters for TWS.

   The following table describes the TWS scheduling data parameters.

   Parameter	Description
   Job definitions	(Mandatory) Contains all the job attributes that relate to the job's functioning and/or how each job should be submitted. For example, which agent to submit the job to, which script to run, the owner of the job (the user who has the credentials for the job's functions), and the job description.
   CPU definitions	(Mandatory) Contains the physical host name for each logical CPU mentioned in schedule.txt, see below. The Control-M Conversion Tool uses this value for the Host ID field in the Control-M job definition.
   Parameter definitions	(Mandatory) Contains the actual value for each parameter mentioned in the jobs.txt file. The Control-M Conversion Tool defines each parameter mentioned in the jobs.txt file as a Variable expression.
   Schedule definitions	(Mandatory) Defines the main file to be imported, which includes the scheduling criteria of each job, and the dependencies between the jobs. Each job in the jobs.txt file can be scheduled more than once.
   Resource definitions file	Defines the resources which is required by tables and jobs and used by the Conversion Tool. TWS command: composer create <resource file> from RESOURCES.
   Calendar definitions file	Translates the information in this file from the Conversion Tool into Control-M calendars. TWS command: composer create <calendars file> from CALENDARS.
   Variable tables definitions file	Defines the variables which are used by the Conversion Tool. TWS command: composer create <variables file> from VARIABLES.
   Workstation parameters directory	Defines the workstation variables. The file names in this folder should be in the following format: <CPU_name>_parms.txt (for example: Workstation1_parms.txt). This should convert Workstation specific variables during the conversion. TWS format: <CPU_name>_parms.txt

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 conversion, see Data conversion.

5. Click Next.

   The Conversion Settings window appears.

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

   NOTE: (Optional) 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.

   • If you want a report for three months from specific workstations, use: rep11 -m mmyyyy mmyyyy mmyyyy -c workstation1 workstation2 workstation3. For example, rep11 -m 062004 072004 082004 -c workstation1 workstation2 workstation3.
   • If you want a report for three months of the current year from all workstations, which directly outputs to a file, use: rep11 -m mm mm mm -o output. For example, rep11 -m 06 07 08 -o output.
   • If you want a report for the current month for a specific workstation, use: rep11 -c workstation1.

   For more information, see Data validation.