When the server manages a job, the job passes through multiple processing stages named states. Some states, such as job failure, require action.
At any time during the course of its execution, a job has one state and zero or more conditions. A job's state and conditions depend on the job's properties, user interaction, and the success or failure of the workload being executed. The job's details displays the job's state and conditions.
Some states can appear as both a state and a condition. When multiple states apply to a job, state priorities determine the job's state. For example, suppose that a job waiting for a predecessor (PREDWAIT) is held at the Application level (APPLHOLD). Since the APPLHOLD state has a higher priority than the PREDWAIT state, the job's state becomes APPLHOLD with a condition of PREDWAIT. If the Application is released from hold, the job's state changes to PREDWAIT.
A job can pass through the following states, from highest priority to lowest priority:
Indicates that the job has been bypassed. It is a final state. Before the job's predecessor dependencies have been met, the job has a Bypassreq condition, indicating that the job has been marked for bypassing.
Indicates that the job has completed successfully. It is a final state if the Application that contains the job completes. If the job was completed manually, it has a Forced condition.
Indicates that the job has failed. The job must be resubmitted or manually completed.
Note: Failed jobs that have an AutoResubmit condition are resubmitted automatically. By default, CA WA Desktop Client displays jobs with an AutoResubmit condition in yellow.
Indicates that the submission of the job resulted in an error. The job must be resubmitted or manually completed. Common causes of submission errors include the following:
Note: For information about what caused the submission error, see the job’s details.
Indicates that the external scheduler is down. The workload object must be completed manually.
Indicates that the job is currently running.
Indicates that the SAP job is defined on the SAP system.
Indicates that the SAP job has been released on the SAP system.
Indicates that the Oracle Applications job is inactive because the concurrent request is either disabled, suspended, or on hold.
Indicates that the job is monitoring for a condition to occur. For continuous monitoring, the server triggers an Alert each time the monitor condition is met. For non-continuous monitoring, the job completes when the monitor condition is met.
Indicates that the z/OS job is to be submitted outside CA Workload Automation DE, such as a job that is submitted manually by a user.
Indicates that the agent referenced in the job definition is down.
Indicates that the Application that contains the job is in a hold state. The job cannot run until the Application is released. Holding an Application does not affect jobs currently running but does prevent the server from submitting new jobs.
Indicates that the Application that contains the job is waiting for a previous generation of the same Application to complete. The job cannot run until the previous generation of the Application completes.
Indicates that the subApplication that contains the job is waiting for a previous generation of the subApplication to complete. The job cannot run until the previous generation of the subApplication completes.
Indicates that the job is waiting for the same job to complete in a previous generation of the Application. The job cannot run until the same job completes in a previous generation of the Application.
Indicates that the job is manually held. The job cannot run until the manual hold is released.
Indicates that the job is waiting for a predecessor. The job cannot run until the release condition is met or dropped.
Indicates that the job is waiting until a specific time for submission. This state is always paired with the Timewait condition. The job cannot run until the submission time is met or reset to the current time.
Indicates that the external job is waiting for its home job to complete in the home Application.
Indicates that the submission of this job has been delayed because the agent is quiesced.
Indicates that the job is waiting for one or more variable dependencies to be met. The job cannot run until all the required variable dependencies are met, dropped, or abandoned.
Indicates that the job is waiting to acquire resources. The job cannot run until all the required resource dependencies are met, dropped, or abandoned.
Indicates that the task requires manual completion.
Indicates that the job is ready to be submitted (all of its dependencies have been met). A workload object will not remain in this state.
Indicates that the server cannot determine the state of the workload object.
|
Copyright © 2014 CA.
All rights reserved.
|
|