Cisco Cisco Tidal Enterprise Scheduler 6.2 User Guide
C H A P T E R
4-31
Cisco Tidal Enterprise Scheduler HP OMU Integration Guide
6.2.1 SP3
4
Event ID Tables
Overview
Each event trigger used in Enterprise Scheduler has its own ID number. Job events use a different
numbering scheme than system events. A listing of each job event and system event are provided in
separate tables in the following sections:
numbering scheme than system events. A listing of each job event and system event are provided in
separate tables in the following sections:
•
•
Job Event Triggers
The following table lists the event triggers for various job events supported by TES.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 job events have an ID number
that begins with 12.
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 job events have an ID number
that begins with 12.
Table 4-1
Job Event Triggers
Event ID
Trigger
Event Type(s)
Description
12000
Job added to
schedule on demand
schedule on demand
Status Change/Job
Control
Control
The job was added to the production
schedule on an unscheduled basis.
schedule on an unscheduled basis.
12001
Job completed
Status Change
The job completed with a Completed
Normally or Completed Abnormally
status.
Normally or Completed Abnormally
status.
12002
Job completed
abnormally
abnormally
Status Change
The job completed with a Completed
Abnormally status. The job’s exit code
is non-zero
Abnormally status. The job’s exit code
is non-zero
12003
Job completed
normally
normally
Status Change
The job completed with a Completed
Normally status. The job’s exit code is
0
Normally status. The job’s exit code is
0