Datasheet

B-32
DOS Utilities
Error Handling
Because the ACU scripting feature is designed to run without user
interaction, the ACU handles errors during record and playback by
simply exiting immediately whenever an error is detected.
Whenever the ACU encounters an error during record or
playback—for example, an unrecognized keyword in a script file—
it reports the error and exits. If a log file is opened, the ACU writes
the 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.
The table below lists the possible error codes returned by the ACU.
Code Description
0 ACU ran without 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 the Scripting
Features on page B-18 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 devices
attached to the selected controller.
7 Specified drive not found in system—The device 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.