Job definition

A job definition contains job processing information, which defines what, where, and how a job runs. For example, the job might run a script on a particular computer. The following procedures describe some of the procedures that are used in the process:

Procedures

Description

Creating a job

Enables you to define a job that includes the following types of parameters:

  • Job types: Enables you to set parameters that define what, how, and where the specific jobs type runs.
  • Job scheduling: Enables you to set options that define when the job and folder runs, including creating or using a Folder Rule-based Calendar or selecting from a Control-M Rule-based Calendar, which you define in the Calendar Manager, but select as part of the scheduling. You can also define when not to run a jobs, by adding the Rule-based Calendar to an Excluded Rule-based Calendar list.
  • Job prerequisites: Enables you to set parameters that define job submission criteria that must be met for a job to run.
  • Job actions: Enables you to set parameters that define actions for Control-M to perform based on various job run events, such as specific output patterns and the job completion status.

Creating a regular folder

Enables you to define containers of one or more jobs, which enables you to organize your jobs according to schedules or resources. You can define as many folders as you need, and assign each folder to a specific Control-M/Server. For more information on the types of folders, see Folder parameters.

Creating a SMART Folder

Enables you to define containers of one or more jobs and Sub Folders, which enables you to organize your jobs according to schedules or resources. The jobs and Sub Folders in a SMART Folder (for non-z/OS jobs) can inherit definitions from parent SMART Folder.

Creating a Sub Folder

Enables you to define containers of one or more jobs and Sub Folders (for non-z/OS jobs), which enables you to organize your jobs according to schedules or resources. The Sub Folder can inherit definitions from the parent SMART folder.

Example: Creating a Control-M Rule-based calendar

Enables you to create a calendar that you can apply to all jobs in your Control-M/Server.

Example: Defining a cyclic job

Enables you to define a job that is defined to rerun.

To test your design, you can temporarily identify the job processing definitions as type “Dummy,” which executes the batch flow without actually running the jobs. For more information on Dummy jobs, see OS Dummy job parameters.

Parent Topic

Planning