Skip Job rule

The following table describes the Skip Job rules, and the job waits for its prerequisite conditions only, and then finish immediately. This affects the calculation of the all services depending on it:

Field

Description

For all jobs meeting the following criteria:

Control-M

Name of the Control-M whose jobs will be included in this exception definition.

Application

Name of the application whose jobs are included in this exception definition.

Sub Application

Name of the Sub Application whose jobs are included in this exception definition.

Job Name

Name of the job that is included in this exception definition.*

Mem Name

Name of the member name (for z/OS) that is included in this exception definition.

Mem Lib

Name of the member library (for z/OS) whose jobs is included in this exception definition.

Folder

Name of the container into which job processing definitions are organized.

Folder Lib

Name of the library that contains the job’s folder.

Host ID

Name of a host computer to which a job was submitted.

Run as

Identifies the user name for whom the job is executed.

Created by

Indicates the Control-M user who defined the job.

Calendar details (click Advanced) Applies to Service Assumption

Calendar

Details of the Control-M and calendar to be used to schedule the job.

Period

Name of one or more periods for this exception definition, which can be selected from a list. Special month rules are not supported.

Parent Topic

What-If scenario simulation