Cisco Cisco Tidal Enterprise Scheduler 6.2 User Guide

Page of 40
4-38
Cisco Tidal Enterprise Scheduler HP OMU Integration Guide
6.2.1 SP3
Chapter 4      Event ID Tables 
System Event Triggers
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 
<z_sys>sys<z_Star>*<z_ADMIRAL>ADMIRAL 
logging actions are not available because they access 
the database. However, the logging action can be used 
with the NT event log.
20018
Lost network connection to 
remote master
The network connection to the remote master was lost.
20019
Connection brought offline due to 
planned outage
The agent/adapter connection has entered a scheduled 
outage window.
20020
Connection brought online after 
planned outage
The agent/adapter connection suspended during a 
scheduled outage window has ended its outage. (Does 
not apply to connections that are disabled during the 
outage.) This event could apply to either the automatic 
enabling of the connection at the scheduled end of the 
outage or when an administrator manually enables the 
connection early.
Table 4-2
System Event Triggers
Event ID
System Event Trigger
Description