SMARTMon-UX has standardized return codes (Windows users may know them better as error levels) that are returned to a calling program as the program exits. The codes are as follows:
Number |
Name |
Description |
0 |
Normal return code if no problems found with command. |
|
1 |
Generic exit code indicating command syntax error. |
|
2 |
Syntax error, but denotes invalid parameter for a command. |
|
3 |
Command unsupported for the selected device. |
|
4 |
Insufficient O/S resources to perform desired action. |
|
5 |
Test error message generated. |
|
6 |
Email attempted, but settings not configured properly. |
|
10 |
Scrub-family test completed, but with errors. |
|
11 |
Scrub-family test terminated early due to error(s). |
|
12 |
Scrub-family test terminated, pattern on disk is not random, disk has not been erased |
|
13 |
Write same command terminated with errors |
|
15 |
Similar to INVALID_PARAM, but parameters were determined to be invalid at runtime |
|
20 |
Windows-specific service routine general error. |
|
21 |
Terminated, command not supported on a SANtool device |
|
22 |
Action terminated by user (CTRL-C or killed, or quit) |
|
33 |
Terminated, program unsupported on this hardware |
|
254 |
SANTOOLS_CODE_1 |
Indicates programmer error. This is an error you should never get, but if you do, please forward it to us immediately. |
255 |
SANTOOLS_CODE_2 |
Indicates programmer error. This is an error you should never get, but if you do, please forward it to us immediately. |
These return codes are of value if you script SMARTMon-UX and wish to implement conditional logic based on their values. See the documentation on the -scrub family of commands to see the return codes that are passed back to the calling program in response to the command-line options sent to the peripheral(s).
Page url: http://www.santools.com/santool/index.html?return_codes.htm