A non-zero exit status code indicates that the job encountered one or more problems while trying to execute the request. Error messages are sent to stderr.
Table 4.2. Exit Status Code Values
| Exit Code | Description |
|---|---|
| 0 | Success. |
| 1 | The request failed. It may be possible to retry the request later after making the appropriate changes to the command arguments. |
| 2 | A retryable error happened. It may be possible to retry the request after a delay. |
| 3 | The request was cancelled by the user, or the DCS Client program has exited for some other reason (e.g. client system reboot). |
| 4 | The request was cancelled by a DCS administrator. |
| 5 | The request was cancelled for a lack of progress. This can happen if the DCS Client program was stopped or blocked for some reason (such as a control-Z typed at the terminal stopping the job, or blocking while writing to stdout when piped to another command such as a pager.) |
| 6 | The request failed to start before the job start timeout expired. |
| 7 | The DCS Client program lost the connection to the DCS request processor sometime after the request processing had started. It may be possible that the request has been partially, or even fully, completed. Examining the request log file with the dcsjlog(1NCAR) command may provide that information. The request may be retryable, but may require DCS administrator intervention if the request has triggered a bug in the request processor. |
| 8 | The NCAR scientist number is unknown. |
| 9 | The NCAR project number is bad or is invalid for the user. |
| 10 | One or more of the specifed DCS job ids were not found. |
| 11 | The dcswait command timed out before the target job(s) completed. |
| 254 | An internal error was detected in the DCS Client program. |
| 255 | An internal error was detected in a DCS server program. |