Cisco Cisco Tidal Enterprise Scheduler 6.2 User Guide
4-36
Cisco Tidal Enterprise Scheduler HP OMU Integration Guide
6.2.1 SP3
Chapter 4 Event ID Tables
System Event Triggers
System Event Triggers
The following table lists the event triggers for various system events supported by TES.These event
triggers are associated with system events through the System Event Definition dialog box.These event
triggers are supported throughout the various integration channels.Using the event ID number displayed
in the Windows application log you can reference its meaning from this table All system events have an
ID number that begins with 20.
triggers are associated with system events through the System Event Definition dialog box.These event
triggers are supported throughout the various integration channels.Using the event ID number displayed
in the Windows application log you can reference its meaning from this table All system events have an
ID number that begins with 20.
12040
Job has insufficient
time to run before
agent outage
time to run before
agent outage
Schedule
Irregularity
Irregularity
Using the duration value of the job, the
job will not complete before a planned
outage on its agent.
job will not complete before a planned
outage on its agent.
12041
Job might run into
agent outage
window
agent outage
window
Schedule
Irregularity
Irregularity
Using the duration value of the job, the
job may not complete before a planned
outage on its agent.
job may not complete before a planned
outage on its agent.
Table 4-1
Job Event Triggers
Event ID
Trigger
Event Type(s)
Description
Table 4-2
System Event Triggers
Event ID
System Event Trigger
Description
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.
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.
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.
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.
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.