Cisco Tidal Enterprise Scheduler 6.2 User Guide

12000

Job added to schedule on demand

Status Change/Job Control

The job was added to the production schedule on an unscheduled basis.

12001

Job completed

Status Change

The job completed with a Completed Normally or Completed Abnormally status.

12002

Job completed abnormally

Status Change

The job completed with a Completed Abnormally status. The job’s exit code is non-zero.

12003

Job completed normally

Status Change

The job completed with a Completed Normally status. The job’s exit code is 0.

12005

Job waiting for operator release

Status Change

All the job’s dependencies have been met. This event trigger only occurs when you select the Require operator release option in its job definition. The job is now waiting for the operator to release it.

12006

Job put on hold

Job Control

The operator put the waiting job on hold.

12007

Job waiting on resource

Status Change

All the job’s dependencies have been met and the job is waiting for an execution slot to become available.

12008

Job not ready by end of its time window

Schedule Irregularity

The end of the job’s time window was reached before its dependencies were met.

12009

Job launched

Status Change

The queue manager released the job from its queue to an agent, and the job entered the Launched status. Launch is the status prior to the job becoming Active.

12010

Job Active

Status Change

The job started running.

12011

Job Stopped

Job Control

The job was stopped by an operator.

12012

Error occurred while launching job

Status Change

The job status changed to Error Occurred. The job did not run.

12013

Job skipped

Schedule Irregularity

The job did not run because another occurrence of this job was already running. The job must have the concurrency option set to Skip in its job definition for this to occur.

12014

Job deferred

Schedule Irregularity / Status Change

Because another occurrence of this job was running when this job was ready to launch, the job is waiting for the previous occurrence to complete. The job must have the concurrency field set to Defer until completion in the Job Definition dialog box for this to occur.

12015

Agent unavailable for job

Status Change

The agent or the network has gone down prior to the job running. Therefore, the job cannot complete on this agent. If the job uses an agent list, this event trigger occurs in different ways based on the agent list:
Ordered, Random, Balanced, or Rotation Agent List: If the job uses any of these lists, the event trigger occurs when all agents in the list are unavailable to run the job.
Broadcast Agent List: If the job uses a broadcast list, the event trigger occurs for each agent in the list that is unavailable to run the job.

12016

Agent for job inactive

Status Change

The agent’s Enabled flag is set to disabled, or inactive. As a result, the job cannot launch on this agent. If the job uses an agent list, this event trigger occurs in different ways based on the agent list:
Ordered, Random, Balanced, or Rotation Agent List: If the job runs on any of these agent lists, the event trigger occurs if all agents in the agent list are inactive.
Broadcast Agent List: If the job runs on a broadcast list, the event trigger occurs for each agent in the agent list that is inactive.

12017

Job status changed

Status Change

Your job status changed. You can use this event trigger to catch all status changes for this job. The associated action occurs for all changes to the status of a job.

12018

Job might start later than expected

Schedule Irregularity

Other jobs which the job depends on are running behind schedule. This could cause your job to run later than expected. This event trigger occurs when one or all of the prerequisite jobs run longer than their estimated duration. The job might start later than originally forecast.

12020

Job might not be ready by end of its time window

Schedule Irregularity

The end of the job’s time window might not be reached before its dependencies are met. This trigger is activated approximately 7 seconds before the job’s estimated start time becomes later than the end of the job’s time window.

12021

Job running longer than expected

Schedule Irregularity

The job is running longer than its estimated duration value. The job continues to run unless you stop it with a Job Control action that is associated with this event trigger, or unless an operator stops it. You initially set the Estimated Duration value in the Job Definition dialog box when you create the job. TES adjusts the value to a historical average after each run of the job.

12022

Job running past end of its time window

Schedule Irregularity

The job is running past the time window set for it in its job definition. The job continues to run unless it is stopped with an associated job control action, or unless it is stopped by an user.

12023

Job might run past end of its time window

Schedule Irregularity

The job might run past the time window set for it in its job definition. The job will continue to run unless it is stopped with an associated job control action, or unless it is stopped by the user. This trigger is activated at the end of the job’s time window minus the job’s estimated duration.

12025

Job finished later than expected

Schedule Irregularity

The job ran longer than the time specified in the Estimated Duration field in its job definition.

12026

Job running longer than its maximum time

Schedule Irregularity

The job is running longer than its Maximum Duration value, as defined in its job definition. The job continues to run unless you stop it with a job control action that is associated with this event trigger, or unless it is stopped by an user.

12027

Job ran shorter than its minimum time

Schedule Irregularity

The job ran in less time than the time specified in the Minimum Duration field in its job definition.

12028

Operator reran the job

Job Control

The operator ran a job again after it already completed. Once set, this trigger will only apply to jobs that were not already in the schedule.

12029

Operator cancelled the job

Job Control

The operator cancelled the job before it had a chance to run.

12030

Operator aborted the job

Job Control

The operator aborted the job while it was running. The job could have taken too many resources, or some other problem could have occurred to justify the abort.

12031

Operator override of job dependencies

Job Control

The operator launched the job, even though all of its dependencies weren’t met.

12032

Job status is LAUNCH on startup.

Job Control

A job status of Launched means that a request to launch the job has been sent to the agent, and is pending notification from the agent that the job has started executing.

12033

Job added to schedule based on calendar

Status Change/Job Control

The job was added to the production schedule automatically.

12034

Job orphaned

Status Change

The master lost connection to the agent running the job and can not determine the job’s current status.

12035

Job rerun would exceed maximum reruns

Job Control

Rerunning the job would exceed the maximum reruns allowed.

12036

Job completed with specified exit code(s)

Job Control

The job completed within the specified exit code range. The exit code can denote normal or abnormal status for a job to trigger different actions.

12037

Job completed normally (output pending)

Job Control

Job completed normally (output pending) The job has completed normally but the job output is still being gathered and is not yet available.

12038

Job completed abnormally (output pending)

Job Control

Job completed abnormally (output pending) The job has completed abnormally but the job output is still being gathered and is not yet available.

12039

Job externally defined (output pending)

Job Control

Job externally defined (output pending) The job status was determined by an external user or program and the job output is still being gathered and is not yet available.

12043

Job not ready by start time

Schedule Irregularity

The job’s scheduled start time was reached before the job was ready to launch due to other dependencies.

20001

System queue limit set to zero

The system queue’s (master queue under which all other queues reside) limit has been set to zero, eliminating the possibility for any jobs to enter the production schedule.

20002

Any queue limit set to zero

A queue’s limit was set to zero. This may have been done to prevent jobs of a certain class from running. Note that a queue can be set to accept a certain class of jobs based on the queue’s filters. To refer to the queue in an alert message, use the Queue Name variable in the assigned action.

20003

System queue reached its job limit

The number of jobs running in the overall system queue has reached the overall system queue limit, and no other jobs can run until a slot becomes available. Slots become available when a job running in the queue completes, or the queue’s limit is increased. When this trigger occurs, it indicates that either too many jobs are being scheduled for the capacity of the system, or the system capacity has been underestimated, and the system queue limit needs to be raised.

20004

Any queue reached its job limit

A queue cannot launch any more jobs until a slot becomes available in the queue. This may indicate that a certain class or type of job is overloading the system. To refer to the queue in an alert message, use the Queue Name variable in the associated action.

20005

Agent reached its job limit

The number of jobs an agent is executing is equal to its job limit. The agent cannot start any more jobs until other jobs complete. To refer to the agent in an alert message, use the Agent Name variable in the assigned action. This system event can notify users when an agent is operating at capacity.

20006

Compile started

The production schedule compile has started. Compiling usually begins at midnight, when the master is started on a new day, or when you select the Create Schedule menu item from the Operations menu. You can use this system event to notify users that a new schedule is being created.

20007

Compile finished

The production schedule compile has completed. Compiling time is based on, among other factors, the number of jobs. Use this system event to alert users that a new schedule is in effect.

20008

Master paused.

The master was paused. Waiting jobs are suspended until the master resumes operation. You can use this system event to notify users that the master was temporarily paused, and jobs will not launch until the master resumes.

20009

Master resumed.

The master has been resumed from paused state. You can use this event to notify users that the master has resumed launching jobs. Depending on how long the master was paused, many jobs may have their dependencies met at once, which may cause a spike in system resource utilization.

20010

Lost connection to agent/adapter

An agent/adapter network connection was lost. To refer to the agent, use the Agent Name variable in the assigned action. You can use this event to warn users that an agent/adapter is no longer connected.

20011

Master program shut down

The master has been shut down normally. You can use this system event to notify users that all waiting jobs will not run until the master restarts.

20012

Backup master took over

A fault occurred on the primary master (such as the master going down, or a network failure occurred) which caused scheduling to be transferred to the backup master. You can use this system event to warn users that the backup master took over the scheduling process. Any jobs that were manually updated after the last database replication update prior to the takeover will have to be re-entered. See the TES Fault Tolerance Guide for more information on Fault Tolerance.

20013

Primary master started.

The primary master has started. You can use this system event to notify users that jobs will resume being launched. Depending on how long the Master was stopped, many jobs may have their dependencies met at once, which may cause a spike in system resources.

20014

New production day

The master has recognized a new production day for which jobs are automatically compiled. You can use this event to trigger initializing variables used in dependencies.

20015

Lost connection to fault monitor

The network connection to the fault monitor was lost.

20016

Lost connection to backup master

The network connection to the backup master was lost.

20017

Lost connection to database

The connection to the database was lost. Operator alerts and TES logging actions are not available because they access the database. However, the logging action can be used with the Windows event log.

20018

Lost connection to remote master

The network connection to the remote master was lost.