Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop batch applications > Submit batch jobs > xJCL elements

The batch job state table

As the job scheduler and grid endpoint process a grid batch job, the job state updates in the job scheduler database. The diagram shows the relationship between states, and the following table lists the possible batch job states and the events that trigger transitions between states. We can view the current state of a batch job from the job management console, or retrieve it using the command line or EJB interface. If a failure occurs before a batch step initializes, then the batch job goes into execution failed state. Otherwise, it goes into restartable state.

Batch job states. The table includes each batch start state with its client command, system action, special condition, return code, and end state.

Start State	Client Command	SystemAction	Special Condition	Numeric return codes	End State
non-existent (delayed submit)	submit	n/a	Not applicable		pending submit
non-existent	submit	n/a	Not applicable		submitted
submitted	n/a	dispatch	Not applicable	0	executing
submitted	cancel	n/a	Not applicable	0	restartable
executing	stop	n/a	Not applicable	0	restartable
executing	cancel	n/a	Not applicable	4	cancel_pending
executing	n/a	caught application error*	Not applicable	4	restartable
executing	n/a	n/a	Infrastructure problem**	4	restartable/unknown
executing	suspend	n/a	Not applicable	4	suspend_pending
executing	n/a	job completed	Not applicable	4	ended
executing	n/a	n/a	Infrastructure problem in job setup***	4	restartable
suspend_pending	n/a	checkpoint	Not applicable	2	suspended
suspend_pending	n/a	n/a	Infrastructure problem**	2	restartable/unknown
suspended	resume	n/a	n/a	5	resume_pending
suspended	cancel	n/a	n/a	5	cancel_pending
suspended	Not applicable	n/a	Infrastructure problem**	5	restartable/unknown
resume_pending	Not applicable	job resumed	Not applicable	2	executing
resume_pending	Not applicable	Not applicable	Infrastructure problem**	2	restartable/unknown
restartable	restart	Not applicable	Not applicable	8	submitted
cancel_pending	Not applicable	job canceled	Not applicable	1	restartable
cancel_pending	Not applicable	Not applicable	Infrastructure problem**	1	restartable/unknown
restartable	purge	Not applicable	Not applicable	8	non-existent
execution_failed	purge	Not applicable	Not applicable	9	non-existent
ended	purge	Not applicable	Not applicable	7	non-existent

Notes for the batch job states table. The table includes each note with a description.

Note	Description
* Application error	The batch application failed at run time. The grid endpoints detected this failure.
** Infrastructure problem	An unexpected error has occurred. See the following example for infrastructure problem in job setup.
*** Infrastructure problem in job setup	An unexpected error that occurs when a batch job is set up for the first time by the grid endpoints. For example, if there is an unexpected database failure, the job goes into execution_failed state. In this condition, the batch job is run for the first time and no steps are processed yet. Batch jobs go into the restartable state under most failure conditions so that they can restart from checkpointed positions if the failure condition can be overcome. However, in this instance of a failure condition, a batch job goes into execution_failed state and cannot be restarted. Since this situation is a job setup scenario and work is not yet processed by the batch job, batch work is not lost as a result of failure. If jobs are in a non-final state on the endpoint, the scheduler puts the jobs into an unknown state under two conditions. The conditions are that the endpoint loses communications or the endpoint goes down. If the endpoint comes back up, the scheduler synchronizes the job status with the endpoint. If the endpoint goes down, all batch jobs are put into a restartable state and all compute- intensive jobs in an execution failed state. If the endpoint has only lost communication with the scheduler and the jobs continue to run, the scheduler updates its status. The status update is the final state of the jobs running on the endpoint at that point.

xJCL elements
Develop batch applications

+

Search Tips   |   Advanced Search