Usage

Optional

Format

Check box

• Selected – job is critical
• Cleared – job is not critical

Alternate names

• Control‑M/EM Utilities: CRITICAL
• Control-M Report: CRITICAL
• Control‑M/Server Utilities: -critical
• Control‑M for z/OS: (none)
• Control‑M/EM API: critical

Alternate formats

Control‑M/EM Utilities

Valid values:

• 1 - Job is critical.
• 0 - Job is not critical. Default.

  EXAMPLE:

  <CRITICAL="1"/>

Control‑M/Server Utilities

Valid values:

• Y - Job is critical.
• N - Job is not critical. Default.

Computer specific information

For non-z/OS computers

Defining a job as critical ensures that a job that requires resources is submitted as soon as possible after all its In Conditions parameters are satisfied. As a result of a job being defined as critical, any Quantitative resources or Control resources that the job requires exclusively are reserved for the job as they become available. The preferential treatment given to a critical job is applied only after all the job’s In Conditions parameters are satisfied.

The Critical parameter takes precedence over the Priority parameter (a low-priority job defined as critical is given preferential treatment over a non-critical high-priority job). However, if two critical jobs are awaiting execution at the same time, the higher-priority job receives resources before the lower-priority job.

Critical path priority applies to contention between Quantitative resources and between Control resources with Exclusive status. The critical path priority does not apply to contention with Control resources with Shared status.

For non-z/OS computers, critical is available for jobs whose statuses are not Executing when editing details in the active Jobs database.

For more information about the Priority parameter, see Priority.

z/OS

The Critical parameter check box is replaced with a check box labeled Emergency. When selected, this marks the z/OS job as an Emergency job.

[For z/OS jobs] The Emergency check box is marked if the job definition is created as a result of a Control-M/EM utility and the Critical parameter was set to ‘1’ (see below).