During its execution, a job can have one or more conditions in addition to its state. Some job states can also appear as a condition if another applicable state has a higher priority. A state cannot appear as both a state and a condition simultaneously.
In addition to states that can appear as conditions, a job can have the following conditions:
Indicates that the job will be resubmitted automatically. The job’s state is FAILED.
Note: By default, CA WA Desktop Client displays failed jobs with an AutoResubmit condition in yellow.
Indicates that the job has been requested for bypassing. When the job's time and predecessor dependencies are met, the server bypasses the job and the job's state becomes BYPASSED.
Indicates that the job has been manually completed. The job's state is always COMPLETE.
Note: You can monitor for forced completions by specifying a notification in the Application or job definition. The notification can send an email, trigger an Event, run a JavaScript script, or send an SNMP trap. For more information about setting up notifications, see the Define Perspective Help.
Indicates that the job is overdue because it is late starting, it is late completing, or it exceeded a maximum execution time.
Note: By default, Desktop Client displays jobs with an Overdue condition in red.
Indicates that the job completed prematurely.
Indicates that the job runs only if it is requested.
Indicates that the job was requested. The job runs when its dependencies are met.
Indicates that the job is waiting for a time dependency to be satisfied. The job may be in a WAITING state.
|
Copyright © 2014 CA.
All rights reserved.
|
|