About Job Executions and Runs

A job is defined by parameters, a schedule, and a target list. Each time a job runs, it creates an execution, which can be thought of as an instance of a job. This job instance has a lifecycle, hence, it has discrete states:

  1. Job is Scheduled

  2. Job is Running

  3. Job finishes in either Succeded or Failed state depending on what happened when the job actually ran

Because a job can run against multiple targets, each time a job runs, there can be more than one execution. For example, a job is runs once each day against five targets. This results in five executions per day, seven days a week. The set of executions on any given day is called a run.

Related Topics

About Job Executions and Runs

About Job Status

About Job Types

About Jobs

About Blackouts

About Steps

About the Jobs Purge Policy

Creating and Editing Jobs

Deleting Jobs

Filtering the List of Jobs

Single vs. Multiple Execution Runs

screenwatch iconUsing Regular Jobs

Viewing Job Results

Working with Multi-Task Jobs

Working with OS Command Jobs

Working with SQL Script Jobs

Enterprise Manager Information Roadmap