Creating a Job

This procedure describes how to create a job inside a folder, SMART folder, or sub-folder in your Workspace A 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 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 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 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 Attributes

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: Characters: 1–64 Case Sensitive: Yes Invalid Characters: ', $, /, , and ?. Variable Name: %%JOBNAME The job name must be unique in each folder, and it cannot share the same name with a parent folder or sub-folder. To write a ) or ( (parenthesis), precede it with a / (forward slash), as follows: /( or /) IBM i (AS/400) Only* Name the job according to IBM i (AS/400) conventions and verify that it matches the actual job name used by IBM i (AS/400). The Job Name value is considered part of the job submission command.
Description	Defines a description of the job using free text. Rules: Characters: 1–4,000 Case Sensitive: Yes
Run as Dummy	Determines whether the job runs as a dummy job—not as a Dummy job A job type that enables you to perform job actions, but not execute anything on the Agent. type. This job is not submitted by the Control-M/Server and only performs post-processing actions. (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 A Control-M component installed on a host (computer) that runs and monitors the jobs on the host. hostname, Agentless Host name, empty host name, or host group where the job executes. Rules: Characters: 1–85 Valid Characters: A–Z, a–z, 0–9, -, ., _, and :. Invalid Characters: Latin-1 special characters.
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: Case Sensitive: Yes Invalid Characters: Blank spaces and '. Variable Name: %%APPLIC For more information, see Application and Sub-application Variables.
Sub-application	Defines a descriptive name for jobs that are more specifically related than in an Application. Rules: Characters: 1–64 Case Sensitive: Yes Invalid Characters: Blank spaces and '. Variable Name: %%APPLGROUP For more information, see Application and Sub-application Variables. Application: Finance Sub-application: Payroll
Variables	Determines variable types, names, and values, as described in Variables. Rules: Characters: 1–40; z/OS: 1–66 Value: 1–4,000; z/OS: 1–66 Invalid Characters: Latin-1 special characters. Control-M recognizes fields that you define with %% as variables A memory location with a name and value that you can reference in your job processing definitions, which Control-M resolves for the current job execution..
Advanced
Override Path	Defines a temporarily-modified job script file without changing the original script file in the File Pathor Member Library field and without changing when the folder is scheduled to run. Rules: Characters: 1–255 iSeries (AS/400): 1–10 Case Sensitive: Yes Invalid Characters: Blank spaces. All Versions of Microsoft Windows 2000: \, /, , ?, <, >, and \|. Variable Name*: %%OVERLIB
Pre-execution Command	Defines a command that executes immediately before job execution. The return code is ignored. Characters: 1–4,000 Variable Name: %%PRECMD
Post-execution Command	Defines a command that executes immediately after job execution. The return code is ignored. Characters: 1–4,000 Variable Name: %%POSTCMD
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 The identification code for a SMART folder, sub-folder, or job execution.. On: The job runs on all Agents within the Host Group. Off: The job runs only on the current Agent.
Run as Detached	Determines whether the job is run as a background process. The results of the job (the output) are analyzed by the post-processing subsystem.
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: Characters: 1–64 Case Sensitive: Yes Invalid Characters: Blank spaces and '.
Type	Determines where to save the folder documentation, as follows: File URL
Doc Path	Defines the directory where the folder documentation is saved. Valid Values: Characters: 1–255; (iSeries, AS/400 only): 1–21 Case Sensitive: Yes
Doc File	Defines the filename of the saved folder documentation. Valid Values: Characters: 1–64 Case Sensitive: Yes Invalid Characters: Blank spaces
URL	Defines the URL where the folder documentation is saved, in one of the following formats: http:// https:// ftp:// file://
Priority	Determines the order that Control-M processes jobs. A higher priority forces Control-M to reserve resources from the Resource Pool A type of quantifiable resource, which represents the total amount of resources from a physical or logical device that a job can access. to ensure that the job is submitted as soon as possible.
Critical	Determines whether the job is a critical-path job in Control-M, which ensures a resource allocation order. Critical jobs take precedence over Priority jobs. If you mark two or more jobs as Critical, the job with higher Priority receives resources first. Critical jobs take precedence for Lock Resources A type of prerequisite that controls the flow of the workflow, which represents a physical or logical device that folders, sub-folders, or jobs can exclusively access or share. that have Exclusive status, not Shared status. You cannot mark a job as Critical when the job is executing. (z/OS only) The parameter is called Emergency. If you create a job using a Control-M/EM utility and set the Critical parameter to 1, the job is marked as Emergency.