Creating a Job
This procedure describes how to create a job inside a folder, SMART folder, or sub-folder in your Workspace.
Begin
-
From the center pane toolbar, click Add Job and from the drop-down list, drag and drop the job type
into a Workspace folder.
For job-specific information, see Job Types.
-
From the job definitions pane, click on one or more of the following tabs to define the job:
-
General: Defines job attributes, as described in Job General Attributes.
-
Scheduling: Defines job scheduling attributes, as described in Job Scheduling Attributes.
-
Prerequisites: Defines the prerequisites
required to run the job, as described in Prerequisites.
-
Actions: Defines the actions that Control-M performs after job execution, as described in Actions.
-
Job General AttributesLink copied to clipboard
The following table describes the General attributes for a job.
Attribute |
Description |
---|---|
Job Type |
Determines the job type that is selected from the Add Job drop-down list. |
Job Name |
Defines the job name. Rules:
|
Description |
Defines a description of the job using free text. Rules:
|
Run as Dummy |
Determines whether the job runs as a dummy job—not as a Dummy job (z/OS only) Determines whether the override path is set to Dummy, as described in z/OS Job. |
Server |
Defines the Control-M/Server or Control-M for z/OS name that processes the job. |
Host/Host Group |
Defines the 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. These jobs do not have to run at the same time. Rules:
|
Sub-application |
Defines a descriptive name for jobs that are more specifically related than in an Application. Rules:
|
Variables |
Determines variable types, names, and values, as described in Variables. Rules:
Control-M recognizes fields that you define with %% as variables |
Advanced |
|
Override Path |
Defines a temporarily-modified job script file without changing the original script file in the File Path or Member Library field and without changing when the folder is scheduled to run. Rules:
|
Pre-execution Command |
Defines a command that executes immediately before job execution. The return code is ignored.
|
Post-execution Command |
Defines a command that executes immediately after job execution. The return code is ignored.
|
Run Job on All Hosts in Group |
Determines whether Control-M runs the same job on all Agents in the host group—each 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 creates the job. Rules:
|
Type |
Determines where to save the folder documentation, as follows:
|
Doc Path |
Defines the directory where the folder documentation is saved. Valid Values:
|
Doc File |
Defines the filename of the saved folder documentation. Valid Values:
|
URL |
Defines the URL where the folder documentation is saved, in one of the following formats:
|
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, which ensures a resource allocation order. |