User manual

1
Introduction
1-15
Entering Command Line Interface Commands
When coding a script, remember to code the appropriate character
sequences, which are described in Navigation Conventions on page 1-3.
Root> config port name 4 "Sam’s Tape Drive"<CR>
Root> maint port beacon 4 true<CR>
Limitation on Movements The commands that are entered are recorded in a history log.
The history log has limitations under the following conditions:
• If a command has more than 60 characters, the command runs,
but the command is not recorded in the history log, and the
position in the tree does not change, as shown in the following
example.
Root> config zoning addWwnMem TheUltimateZone 10:00:00:00
:C9:22:9B:64
Root>
Because the command is not recorded in the history, a subsequent
asynchronous command (navigation command) cannot depend on it.
• Whenever the position in the CLI command tree moves to a new
branch (for example,
config to maint, config to config.port,
or
config.port to config), the history log is cleared. In this case,
any asynchronous commands (for example, the up-arrow
command <ESC>[A or the up-arrow keyboard symbol) cannot
move the position back towards the root, as shown in this
example:
Root> config
Root.Config> port
Root.Config.Port> <ESC>[A
Root.Config.Port>
Parameters
Some command parameters accept character strings that include
spaces. Quotation marks are required when a string includes spaces.
Config.System> location Building_24_Room_16
Config.System> location "Building 24 Room 16"
If spaces are not included in a parameter that accepts a string, the
quotation marks are not required around that string.
To include quotation marks in a string, use the escape character (\)
before the quotation marks.