Determining why a utility failed to complete
If an online utility job completes normally, it issues return code 0. If it completes with warning messages, it issues return code 4. Return code 8 means that the job failed to complete. Return code 12 means that an authorization error occurred.
Procedure
To determine why a utility failed to complete:
Use the following list of possible scenarios to help resolve
the problem:
| Problem | Solution |
|---|---|
| DB2® terminates the utility job step and any subsequent utility steps. | Submit a new utility job to execute the terminated steps. Use the same utility identifier for the new job to ensure that no duplicate utility job is running. |
| DB2 does not execute the particular utility function, but prior utility functions are executed. | Submit a new utility step to execute the function. |
| DB2 places the utility function in the stopped state. | Restart the utility job step at either the last
commit point or the beginning of the phase by using the same utility
identifier. Alternatively, use the TERM UTILITY command to terminate
the job step and then resubmit it. Related information:
|
| DB2 terminates the utility and issues return code 8. | One or more objects might be in a restrictive
or advisory state. Resolve that status and resubmit the job. Also, a DEADLINE condition in REORG might have terminated the reorganization. |