Table 4-1 Job Event Triggers
|
|
|
|
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
Launch
.
|
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 option 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
option 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.
<z_sys>sys<z_Star>*<z_ADMIRAL>ADMIRAL
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 PST 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 canceled the job
|
Job Control
|
The operator canceled 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 were not 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)
|
Status Change
|
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)
|
Status Change
|
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)
|
Status Change
|
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)
|
Status Change
|
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.
|
12040
|
Job has insufficient time to run before agent outage
|
Schedule Irregularity
|
Using the duration value of the job, the job will not complete before a planned outage on its agent.
|
12041
|
Job might run into agent outage window
|
Schedule Irregularity
|
Using the duration value of the job, the job may not complete before a planned outage on its agent.
|