FW 08.01.00 McDATA E/OS Command Line Interface User Manual (620-000134-740, November 2005)

1-14

E/OS Command Line Interface User Manual

Entering Command Line Interface Commands

Limitation on Movements As the commands are entered, they are recorded in a history log.

Note these limitations on movement that result from use of the

history log:

• 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. Because the command is not recorded in the history, a

subsequent asynchronous command (navigation command)

cannot depend on it.

Root> config zoning addWwnMem TheUltimateZone 10:00:00:00

:C9:22:9B:64

Root>

• 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.

Config.System> location "Building 24 \"Joe’s PlayLab\""

A null string can be created by using the quotation marks without

any space between them.

Config.System> location ""