Understanding The Command Line Utility; Identifying Return Codes; Using The Noprompt Parameter; Using Event Log Files - Adaptec ICP5045BL User Manual

Understanding the Command Line Utility

The command line utility is used interactively or in batch mode. With interactive mode, enter
commands at the prompt. In batch mode, create scripts and run the script in the appropriate
shell. For example:
Environment
Windows
Linux/Unix
In either mode, if your command fails, you immediately see an error message of Command
failed. Other script messages that you can get are Command completed successfully, or
Command aborted.
Available commands are described on the following pages, in alphabetical order. To access a
list of commands, type <name of utility> and press Enter.
To access the online help for a specific command, type <name of utility> <command>, then
press Enter.

Identifying Return Codes

With either utility, the return values for each command are the same. The return values are as
follows:
0x00: SUCCESS
0x01: FAILURE - The requested command failed
0x02: ABORT - The command was aborted because parameters failed validation
0x03: INVALID_ARGUMENTS - The arguments are incorrect. (Displays COMMAND help)
0x04: UNSUPPORTED - The command is unsupported
0x06: INVALID_ADAPTER - The adapter specified does not exist (special case of
INVALID_ARGUMENTS)

Using the Noprompt Parameter

With either utility, the noprompt parameter for all commands are the same. Used mostly for
the purpose of scripting setup, this parameter overrides all user confirmations. To use the
noprompt feature, type <command> [noprompt], then press Enter.

Using Event Log Files

The Command Line Utility event log shows the results of a command in the form of the
following:
Status – success/failure/aborted/invalid arguments/unsupported/invalid adapter (for
●
details see
Return code – 0x00/0x01/0x02/0x03/0x04/0x06 (for details see
●
Additionally, when using the ROMUPDATE or DRIVERUPDATE commands, the event log
displays (when data is available) the old and new version of the firmware or driver being
updated.
Batch File
.bat
.sh
Identifying Return Codes.)
Chapter 2: Using the Command Line Utility
Run Script
CMD.EXE
sh / bash
Identifying Return
11
●
Codes.)