Creating a Job
This procedure describes how to create a job in a folder or sub-folder in your WorkspaceA working area in the Planning domain where you define and edit new jobs and SMART folders..
Begin
-
From the Center Pane Toolbar, click Add Job and from the drop-down list, drag and drop the job type
The type of the job, such as an OS Job that executes at the operating system level or integrations that run on third-party applications, such as AWS, Azure, and Control-M for Databases. into a folder or sub-folder within the Workspace.
For a list of all available job types, see Job Types.
-
From the Edit tab, define one or more of the following:
-
General: Defines information about the job, as described in Job General Attributes.
-
Scheduling: Defines scheduling attributes for the job, as described in Job Scheduling Attributes.
-
Prerequisites: Defines the prerequisites
The part of the job definition that controls the flow of your jobs, such as an event that controls flow sequence or a resource that controls load balancing. required for the job to run, as described in Prerequisites.
-
Actions: Defines the actions that Control-M performs after the job has executed, as described in Actions.
-
Job General Attributes
The following table describes the General attributes for a job:
Attribute |
Description |
---|---|
Job Type |
Determines the job type selected from the |
Job Name |
Defines the name of the job. Rules:
|
Description |
Defines a description of the job using free text. Rules:
|
Run as Dummy |
Runs as a dummy job, and not as a Dummy job type. A job that is set to Run as Dummy is not submitted by Control-M/Server and only performs post processing actions.
|
Server |
Indicates the name of the Server that processes the job. |
Host /Host Group |
Defines the name of an Agent Rules:
|
Parent Folder |
Defines the name of the parent folder or parent folder and sub-folder. |
Application |
Defines a descriptive name for related job groups. Jobs do not have to run at the same time. Rules:
|
Sub-application |
Defines a logical name for the Sub-application. Rules:
Application = Finance, and Sub-application = Payroll. |
Variables |
Determines variable types, names, and values, as described in Variables. Rules:
If you include %% in the value for a job definition attribute, Control-M treats this as a variable |
Advanced |
|
Override Path |
Defines a temporarily-modified job script file without changing the original script file in the File Path and without changing the run schedule of a folder. Rules:
|
Pre-execution Command |
Defines a command that runs immediately before running the job. The return code is ignored.
|
Post-execution Command |
Defines a command that runs immediately after running the job. The return code is ignored.
|
Run Job on All Hosts in Group |
Determines whether Control-M runs the job on all Agents within the Host Group. All available Agents in the Host Group run an identical job, and each such job has a unique run ID
|
End Folder on Job Completion |
Determines whether Control-M stops executing jobs and sub-folders in the folder. To enable this option, you must have full User Views set in User and Role Authorizations. |
Created By |
Defines the Control‑M user who created the job. Rules:
|
Documentation |
Defines the location of the documentation of the folder. |
Type |
Determines whether the documentation for the job is in a file or URL, as follows:
Doc Path Rules:
Doc File Rules:
|
Priority |
Determines the order that Control-M processes jobs. A higher priority forces Control-M to reserve resources from the Resource Pool |
Critical |
Determines whether the job is a critical-path job in Control-M. This ensures a resource allocation order. |