Job Type

Defines the type of job that determines which fields are exposed in a job definition. The value of the job type is usually based on the platform for the job run. Jobs defined as Dummy provide instructions for Control-M such as post-processing actions.

Value: Batch Impact Manager

Job Name

Defines the name of the job processing definition and appears in the job definition and tracking displays, and enables you to identify the job, and order the job.

Description

Provides a description of the job in free text. A well written description can help you determine why the job was defined and how it fits into your business workflow.

What

Defines one or more parameters which determines what the job runs.

Determines the service name the following service parameters that are relevant for creating a service:

• Service Name
• Service must complete
• Service Priority
• Actions
• Job Run-Time Tolerance

Service Name

Logical name, from a user or business perspective, for the critical service. BMC recommends that the service name be unique.

Service must complete

Defines the time the critical service must be completed to be considered on time. The time can be specified either by a specific hour and/or day or on a specific hour and minute after the order time. This parameter consists of the following sub-parameters:

• By (Number of days): Defines by what time (in HH:MM), and in how many days, relative to the Order date, the service must complete.
• In (Number of hours, and number of minutes after): Defines in how many hours and minutes, the service must complete.

Service Priority

Defines the priority level of this service, from a user or business perspective.

Actions

Defines the automatic interventions, such as rerunning a job, displaying the critical service in BMC Service Impact Manager, or extending the service due time. The action is performed if the job finished too quickly, there is a job failure on service path, or the service finished late or too quickly.

• When: Defines the BIM event that triggers the action, as described in BIM Events
• Do: Defines the action, as described in Batch Impact Manager Service Actions

Job Run-Time Tolerance

Defines the type of deviation from the average completion time for a job in the service. If the run time falls within the tolerance set, it is considered on time, otherwise it has run too long or ended too early. The values are Percentile range or Average Run Time (in percentage or by minutes).

• Percentile range: Defines the number of standard deviations of job run in this service. Percentile Range is the default method for specifying Job Run-Time Tolerance.
• Average run time +/-: The percentage of the time (based on the average run time for the job) or the number of minutes that the job can be early or late, and still be considered on time.

For information on setting the service completion time, see Service must complete.

Where

Defines an area of the Properties pane for defining the Control-M/Server of the job.

Control-M/Server

Defines the name of the Control-M/Server (or Control-M for z/OS) that processes the job.

Run as

Identifies the user name with the authorization to execute the job. This parameter is used by the Control-M security mechanism.

Parent Folder

Defines the name of the folder that contains the job or Sub Folder.

Names of folders and Sub Folders may be up to 64 characters, with the exception of Control-M for z/OS folders which may be up to 8 characters. Folder names cannot contain the character “/”. SMART Folders in Control-M for z/OS can only contain jobs (not Sub Folders).

More

Defines an area of the Properties pane to click to define more parameters.

Run job on all hosts in group

Specifies that job submission details be broadcast to all agents within a defined Host Group. All available agents in the Host Group run an identical job, and each such job has a unique Order ID.

Variables

All variables are identified by the %% prefix. If %% is included in the value for a job processing parameter, Control‑M assumes that it is referring to a variable or function. You can add a variable, as described in Adding a variable.

Application

Provides a logical name for sorting groups of jobs. This parameter is used to supply a common descriptive name to a set of related job groups. The jobs do not necessarily have to run at the same time.

Sub Application

Indicates the name of the Sub Application where the job belongs logically. It is a sub-category of the Application parameter. For example, the Application is Finances, and the Sub Application is Payroll.

Created by

Indicates the Control‑M/EM user who defined the job.

Documentation

Defines a description related to the job, and is saved in a defined location. The Documentation area in the Properties pane includes information about where to find the Documentation. In a z/OS job, the Documentation is in a Doc Member located in a Doc Library. In a non-z/OS job, the Documentation depends on whether the type is File or URL. For a file, the description is located in a file located in a file path. For a URL, the Documentation is located in a URL address.

Type

Defines whether the documentation for an OS job is in a file or URL. See the following:

• URL: Defines the URL address where the documentation is located. The format starts with "http://", "ftp://", or "file://".
• File: Specifies the file that contains the job script.

Doc Path

For a z/OS job, Doc Library defines the name of the library where the Documentation (description) is saved. For a non-z/OS job, Doc Path defines the name of the file path where the Documentation is saved.

Doc File

For a z/OS job, defines the name of the member where the job Documentation (description) is saved. For a non-z/OS job, the Doc File is the name of the file where the job Documentation is saved.

Priority

Determines the order of job processing by Control-M in the Active Jobs database.

Critical

Determines whether the job is a critical-path job in Control-M, which ensures resources allocation order.