Reference Guide

Unless specified otherwise, enter all commands, options, arguments, and command line switches in
lowercase letters.
Command Line Option Delimiters
The following table lists some examples of valid and invalid DTK command lines.
Table 3. Command Line Option Delimiters
Valid /
Invalid
DTK Command Line Example
valid
syscfg --option1 --option2 syscfg --asset --floppy
invalid
syscfg --option1=argument --
option2 --option3
syscfg --asset=R910 --floppy --
bootseq
valid
syscfg -o=filename --option1 --
option2
syscfg -o=/tmp/myfile.txt --floppy
--bootseq
valid
syscfg -l=filename --option1 --
option2
syscfg -l=/tmp/myfile.txt --floppy
--bootseq
invalid
syscfg -i=filename --option1 --
option2
syscfg -i=/tmp/myfile.txt --floppy
--bootseq
valid
syscfg --option=argument
bmcoption
--option1= argument
syscfg --embnic=on pcp --
hostname=webserver
NOTE: Do not combine options that specify report or set actions in a command line instance.
Other Delimiters
The following table lists the other delimiters:
Table 4. Other delimiters
Delimiter Example Description
White space (space or tab)
syscfg --
option=argument1
argument2
considers
argument1
and
argument2
as two arguments.
A string surrounded by double
quotation marks regardless of
the white space contained
within, is interpreted as a single
SYSCFG argument.
syscfg --
option="argument1
argument2"
considers
argument1
and
argument2
a single argument.
A double quotation mark
preceded by a backslash (\") is
syscfg --
option="\"argument"
considers "argument as the
argument.
17