When working with step status, it is important that you understand how multiple jobs are used to process the steps in a procedure. For procedures other than type *NODE, at any given time, job activity may be in progress for multiple steps. Or, one job may have failed processing a step while other jobs may have already processed that step and continued beyond it. Node procedures only have one job.
Important! Before you take action to resolve a problem with status for a step, be sure you understand the current state of your environment as a result of completed steps and steps in progress, as well as the effect of any action you take.
The following table identifies the possible status values that can appear on the Work with Step Status display and the action to take to resolve reported problems.
|
Status Value |
Description and Action Required |
|---|---|
|
blank |
The procedure has started but processing has not yet started for the step. |
|
*ATTN |
The step requires attention. The value *ATTN can only appear in the collapsed view or on a summary row in the expanded view. If the procedure status is considered active, at least one job submitted by this step has a status of *FAILED, *CANCEL or *MSGW. If the procedure status is *FAILED or *CANCELED, this step has at least one job that has not started or has a status of *CANCEL or *FAILED. Action Required: Use F7 to see the expanded view. Determine the specific data resource group or data group for which the problem status exists. Then address the status indicated for that job. |
|
*ACTIVE |
The step is currently running. |
|
*COMP |
The step has successfully completed. |
|
*DSBLD |
The step has been disabled and did not run. |
|
*CANCEL or *FAILED |
One or more jobs used by the step ended in error. In the expanded view of status, the job is identified as *CANCEL or *FAILED. The status is due to the error action specified for the step.
The type of step program used by the step determines what happens to other jobs for the step and whether subsequent steps are prevented from starting, as follows:
When all asynchronous jobs for the procedure finish, the procedure status is set to *CANCELED or *FAILED, accordingly. If both canceled and failed steps exist when the procedure ends, the procedure status will be *FAILED. Action Required: Determine the cause of the problem using Resolving *CANCEL or *FAILED step statuses. |
|
*IGNERR |
The step ran and an error occurred, but processing ignored the error and continued. Action Recommended: Use option 8 (Work with job) to determine the cause of the failure. Consider whether any changes are needed for the procedure, step, or operating environment to prevent this error from occurring again. |
|
*MSGW |
The step ran and issued a message that is waiting to be answered. One or more jobs for the step ended in error. The step attribute requires that an operator respond to the message. Action Required:
|