IBM System Storage DS3000, Programming Manual

Page: 27 / 652

You cannot use double quotation marks (“ ”) as part of a character string (also called string literal ) within
a script command. For example, you cannot enter the string below in order to set the storage subsystem
name to “Finance Subsystem":
-c “set storageSubsystem userLabel=\”\”Finance\”Subsystem\”;”
In the Linux operating system and the Solaris operating system, the delimiters around names or labels
are single quotation marks (‘ ’). The UNIX versions of the previous examples are as follows:
-c 'set storageSubsystem userLabel=“Engineering”;'
-n “My”_StorageSubsystem
In a Windows operating system, if you do not use double quotation marks (“ ”) around a name, you
must insert a caret ( ^ ) before each special script character. Special characters are ^, |, <, and >.
Insert a caret before each special script character when used with the terminals
-n
,
-o
,
-f
, and
-p
. For
example, to specify storage subsystem CLI>CLIENT, enter this string:
-n CLI^>CLIENT
Insert one caret (^) before each special script character when used within a string literal in a script
command. For example, to change the name of a storage subsystem to FINANCE_|_PAYROLL, enter the
following string:
-c set storageSubsystem userLabel=\“FINANCE_^|_PAYROLL\”;”
Detailed Error Reporting
Error data collected from an error encountered by the CLI is written to a file. Detailed error reporting
under the CLI works as follows:
v
If the CLI must abnormally end running CLI commands and script commands, error data is collected
and saved before the CLI finishes.
v
The CLI saves the error data by writing the data to a standard file name.
v
The CLI automatically saves the data to a file. Special command line options are not required to save
the error data.
v You are not required to perform any action to save the error data to a file.
v
The CLI does not have any provision to avoid over-writing an existing version of the file that contains
error data.
For error processing, errors appear as two types:
v
Terminal errors or syntax errors that you might enter
v
Exceptions that occur as a result of an operational error
When the CLI encounters either type of error, the CLI writes information that describes the error directly
to the command line and sets a return code. Depending on the return code, the CLI also might write
additional information about which terminal caused the error. The CLI also writes information about
what it was expecting in the command syntax to help you identify any syntax errors that you might have
entered.
When an exception occurs while a command is running, the CLI captures the error. 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.
The name of the file to which error information is saved is
excprpt.txt
. The CLI tries to place the
excprpt.txt
file in the directory that is specified by the system property
devmgr.datadir
. If for any
reason the CLI cannot place the file in the directory specified by
devmgr.datadir
, the CLI saves the
excprpt.txt
file in the same directory from which the CLI is running. You cannot change the file name or
Chapter 1. About the Command Line Interface
1-7