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: SLA Management, Dummy (z/OS)

Job Name

Defines the name of the Job processing definition.

Control-M rules:

• 1-64 characters
• Case sensitive
• Invalid characters: Single quotation marks, "$", "/", "*", "?", " "

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 Job flow. Control-M rules:

• 1-4000 characters
• Case sensitive

Control-M/Server

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

Host/Host group

Defines the name of the host or host group that processes the Job.

Service Name

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

Control-M rules:

• 1-64 characters
• Case sensitive
• Invalid characters: single quotation marks, blanks

  If the Job runs on any version of Microsoft Windows 2000, prohibited filename characters (such as \, /, or *)

Service/Complete by or Complete in

Defines the time in which 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:

• Regardless of order time: Overrides the order time of the service
• Relative to order time: a specific amount of time after the order time of the service
• Complete in/by:

  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.

Control-M rules:

By:

• Specific hour, in the format HH:MM, according to a 24-hour clock.
• Valid values range include 00:01 through 99:59

Number of days:

• Determine on which day the critical service must complete, relative to ODATE. The value is specified in terms of the number of days after the order date of the service.
• 0 represents the order date, 1 represents one day after the order date, and so on. Default: 0

In number of hours:

A specified number of hours.

Number of min after:

A specified number of minutes.

Service Priority

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

The priority can be set from 1 (highest priority) to 5 (lowest priority),and enables filtering according to priority in the Service Monitor window and the Web Client.

Service Actions

Defines the automatic interventions, such as rerunning a Job, displaying the critical service in SLA Management, or extending the service due time. The action is performed if the Job finished too quickly, there is a Job failure on the service path, or the service finished late or too quickly.

• When: Defines the SLA Management event that triggers the action.
• Do: Defines the action.

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).

• Job runs deviations: 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.

Control-M rules:

Percentile range: Drop-down list

Average run time +/-:

Percentage: 999

Minutes:999

Run as

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

Control-M rules:

• 1-30 characters
• Case sensitive
• Invalid characters: single quotation marks, blanks

Parent Folder

This is a read-only field. 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).

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.

Control-M rules:

• Case sensitive
• Invalid Characters: Blanks, Single quotation marks

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.

Control-M rules:

• 1-64 characters
• Case sensitive
• Invalid characters: Single quotation marks, Blanks

Scheduling Environment (z/OS only)

Indicates the JES2 workload management scheduling environment that is to be associated with the Job.

System Affinity (z/OS only)

Indicates the identity of the system in which the Job must be initiated and executed (in JES2).

Request NJE Node (z/OS only)

Defines the node in the JES network where the Job executes.

Prevent NCT2 (z/OS only)

Performs data set cleanup before the original Job run.

Control-D Category (z/OS only)

Defines the name of the Control-D Report Decollating Mission Category. If specified, the report decollating mission is scheduled whenever the Job is scheduled under Control-M.

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. For more information about adding a variable, see Adding a variable.

Control-M rules:

• Name: 1-40
• Value: 1-4000

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.

Created by

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

Control-M rules:

• 1-64 characters
• Case sensitive
• Invalid characters:

  Single quotation marks

  Blanks

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.

Doc Library (z/OS only)

Defines the name of the library where the Documentation (description) is saved.

Doc Member (z/OS only)

Defines the name of the member where the Job Documentation (description) is saved.

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.

Control-M rules:

• URL Length: Combines the length of Doc Member/ Doc File 64 characters and Doc Library/ Doc Path 255 characters
• File Length: 1-64 characters

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.

Control-M rules:

• Microsoft Windows and UNIX: 1-255 characters
• iSeries (AS/400): 1-21 characters
• OpenVMS: 1-60 characters
• Case sensitive

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.

Control-M rules:

• 1-64 characters
• Case sensitive
• Invalid characters: Blanks

Priority

Determines the order of Job processing.

Emergency Job (z/OS only)

Determines whether the z/OS Job is an Emergency Job.

Critical

Determines whether the Job is a critical-path Job, which ensures the resource allocation order.