Chapter 8. Command-line interface and Script Editor 501
Usage guidelines
Follow these guidelines when using the Script Editor:
All statements must end with a semicolon (;).
Each base command and its associated primary and secondary parameters must be
separated with a space.
The Script Editor is not case-sensitive.
Each statement must be on a separate line.
Comments can be added to the scripts to make it easier for future reference and to
understand the purpose of the command statements.
Adding comments to a script
The Script Editor supports the following comment formats:
Text contained after two forward-slashes // until an enter character is reached.
For example, the comment The following command assigns hot spare drives is
included for clarification and is not processed by the Script Editor:
//The following command assigns hot spare drives.
set drives [1,2 1,3] hotspare=true;
Text contained between the characters /* and */.
For example, the comment The following command assigns hot spare drives is
included for clarification and is not processed by the Script Editor:
/* The following command assigns hot spare drives.*/
set drives [1,2 1,3] hotspare=true;
Important: A comment beginning with // with must an with an end-of-line character,
which is inserted by pressing the Enter key. If the script engine does not find an
end-of-line character in the script after processing a comment, an error message is
displayed and the script execution is terminated. This error commonly occurs when a
comment is placed at the end of a script.
Important: The comment must start with /* and end with */. If the script engine does
not find both a beginning and ending comment notation, an error message is displayed
and the script execution is terminated.
To Next Page
Loading...
Need help?
General