Processing elements (PEs) have state and reason code (RC)
values that provide information about the status of the PE.
Table 1. Processing element states
| PE state |
Description |
| Constructed |
The PE is
initializing. |
| Restarting |
The PE is
restarting. |
| Running |
The PE is running. |
| Starting |
The PE is starting. |
| Stopped |
The PE is stopped. |
| Stopping |
The PE is stopping. |
| Unknown |
The application service cannot be contacted to determine
the current state of the PE. |
Table 2. Processing element reason codes
| Reason code |
Description |
| (-) None |
No reason code is available. |
| (A) Automatic |
The system automatically
moved the PE to this state. |
| (C) Crashed |
PE processing
stopped unexpectedly with a signal condition such as a segmentation
violation (SEGV). |
| (F) Failure |
The PE processing
completed, but it returned a completion code that indicates that a
failure occurred. |
| (H) Resource (host) failure |
The PE is transitioning to a new resource
because the resource it was running on experienced a failure. The application service that is
associated with the resource was removed or restarted. |
| (N) No feasible resource |
The application manager service cannot find a resource to run the PE. |
| (R) User request |
There was a user request
to move the PE to this state, for example, stopping the PE because
of a job cancellation request. |
| (V) Voluntary |
The PE stopped because its processing completed
successfully without any errors. |