SmartSetup Scripting Toolkit Deployment: HP Integrity Servers with Linux

Table 6-7 Custom Script File Options (continued)
ValueOption
• OpenVMS
• TRU64
• Linux
• Solaris
• Netware
• HP
• Windows_SP2
Error Reporting
When using the cpqacuxe utility, any errors that are encountered are logged to the error.ini
file or the specified error file. Error codes are also returned to the calling process, allowing
scripting clients to key off the return code instead of having to parse the error file.
The error file displays the error code, error message, and if possible, lists the controller, array,
or logical drive associated with the error.
The format of the error file is as follows:
Line1:ACU Configuration Replication Error Line2:ERROR: (<error code>) <error description>
Line3:Controller: Slot # | SerialNumber # | WWN #
Line4:Array: #
Line5: Logical Drive: #
Table 6-8 Error Codes
ReasonErrorCode
Success
Success
0
Problem spawning ACU process (user is not authenticated
to use ACU or ACU is already running).
General error
1
Error opening capture file.
Failure opening capture file
'%s'
2866
Error opening input file.
Failure opening input file '%s'
2867
Error opening error file.
Failure opening error file '%s'
2868
The specified command is missing or in the incorrect place
in the file.
‘%s’ command expected
2869
The specified command is not a valid scripting command.
'%s' is not a supported command
2870
The specified command does not belong in the Controller
section of the script file.
'%s' is not a Controller command
2871
The specified command does not belong in the Array section
of the script file.
'%s' is not an Array command
2872
The specified command does not belong in the LogicalDrive
section of the script file.
'%s' is not a Logical Drive
command
2873
A command found in the HBA section is not a valid command
for this section.
’%s' is not an HBA command
2874
The specified command is used more than once in the same
section. It should only be used once per section.
More than one '%s' command
cannot exist in the same section
2875
No controllers were detected. This error applies to input
mode only.
No controllers detected
2821
Input mode cannot be run on internal controllers without
slot information online. For Windows, this means the System
Management Driver has to be loaded.
Slot information is not
available
1102
62 Utilities Reference