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