Error Reporting - IBM Midrange System DS4000 Series Hardware Manual

– Invoking SMcli and specifying a storage subsystem, but not specifying the commands
or script file to execute, will cause SMcli to run in interactive mode. Use Ctrl-c to stop
SMcli execution.
Usage requirements that apply to Windows operating systems only:
– Insert a backslash (\) before each double quote character (") when the double quotes
are used as part of a name or command syntax (for example, -c "set
storageSubsystem userLabel=\"string\";").
– Insert a backslash (\) before each quote around a user label that contains spaces (for
example, -c "start logical driveCopy source=\"Mirror Repository 1\" target=trg9
priority=high;").
– Insert three backslashes (\\\) in front of the (") to display the backslash when used with
the -n, -o, -f, or -p option (for example, -n "Jason\\\" to specify storage subsystem
named Jason\).VolumeCopy
– Insert five backslashes (\\\\\) in front of the (") to use the backslash character as part of
the literal command string (for example, -c "set storageSubsystem
userLabel=\"Jason\\\\\";" to change the name of the storage subsystem to Jason\\).
– Insert a caret (^) before each special script character (^, &, |, <, >) when that character
is used with the -n, -o, -f, and -p options (for example, -n "CLI^&CLIENT" to specify
storage subsystem "CLI&CLIENT"). See the appropriate operating system scripting
documentation for a list of special script characters.
– Insert three carets (^^^) before each special script character when used within a literal
script command string (for example, -c "set storageSubsystem
userLabel=\"Finance^^^&payroll\";" to change the name of the storage subsystem to
Finance&Payroll).
Usage requirements that apply to UNIX operating systems only:
The entire command string must be enclosed in single quotes ('), although some simple
commands might also work with double quotes (").
Important: As a general recommendation, it is better to avoid using special characters in
order to stick to a simple command syntax.

8.1.4 Error reporting

When the CLI encounters an error, it writes information describing the error directly to the
command line and sets a return code. Depending on the return code, the CLI might also write
additional information about which parameter caused the error. The CLI will also write
information about what it was expecting in the command syntax to help you identify any
syntax errors you might have entered.
When an exception occurs while a command is running, the CLI captures the error and, at the
end of processing the command (after the command processing information has been written
to the command line), the CLI automatically saves the error information to a file.
Special command-line options are not required to save the error data. Additionally, if the CLI
must abnormally end CLI and script commands, error data is collected and saved before the
CLI finishes.
482
IBM Midrange System Storage Hardware Guide