Cisco Cisco Tidal Enterprise Scheduler 6.2 User Guide
4-37
Cisco Tidal Enterprise Scheduler HP OMU Integration Guide
6.2.1 SP3
Chapter 4 Event ID Tables
System Event Triggers
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.
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.
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.
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.
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.
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
An agent’s 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 is no longer connected.
agent, use the Agent Name variable in the assigned
action. You can use this event to warn users that an
agent 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.
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 Fault Tolerance
Guide for more information on Fault Tolerance.
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 Fault Tolerance
Guide for more information on Fault Tolerance.
Table 4-2
System Event Triggers
Event ID
System Event Trigger
Description