
13-25
Using the Array Configuration Utility
error message to the log file. Otherwise, it displays the message on
the screen.
Upon exit, the ACU returns its exit status in the DOS environment
variable ERRORLEVEL. When the ACU is run within a DOS batch
file, that batch file can examine the ACU’s exit status using the DOS
command IF ERRORLEVEL n. The batch file can use this command
to test the ACU success or failure status. The batch file can test for a
specific error using a series of If ERRORLEVEL n commands.
Table 13-7 lists the possible status codes returned by the ACU.
Table 13-7 Error Codes
Code Error/Information Meaning
0 You ran ACU and
made no changes.
The ACU exited with no errors
(success) and no report is required.
1 No Controller Found. The ACU did not detect any
controllers in the system.
2 Syntax or logical error
in the script file.
The ACU encountered an invalid
command or keyword in the specified
script file.
3 Unable to open file. The ACU was unable to open the
specified script or log file.
4 Error in the command
line parameters.
You passed an invalid command-line
switch to the ACU. (See Using Script
Mode on page 13-8 for the list of valid
command switches.)
5 Unable to read system
configuration.
The ACU was unable to get the
configuration information from the
specified controller.
6 No drives detected. The ACU did not detect any disk
drives attached to the selected
controller.
7 Specified drive not
found in system.
The disk drive you specified does not
exist on the selected controller.
8 Specified array size
too small.
You specified an array size that is
smaller than the minimum size
allowed for this array.
9 Specified array size
too big.
You specified a array size that is
larger than the maximum size allowed
for this array.
Commentaires sur ces manuels