System Debug Reference Manual (32650-90888)

22 Chapter2
User Interface
Command Line Overview
Another possibility for this is dat.
The prompt can be changed with the ENV command as follows:
$10 ($42) nmdebug > env prompt "mode ' > '"
nm >
Command names can be entered in either upper- or lowercase and may be followed by
their parameters, separated from one another by either blanks or commas. The
specifications of individual commands may also describe special parameters that are also
accepted.
Comments can be entered on any command line, and are introduced by the sequence /*.
Everything on a command line after the /* is ignored:
CMD1 parm1 /* this is a comment...
Long commands may be spread across several lines by using the command continuation
character "&". Command lines ending with this character are continued on the following
line. The special prompt cont > is used to indicate that command continuation is in
progress:
$nmdebug > wl 'This is a long &
cont > line broken into&
cont > three parts.'
This is a long line broken into three parts.
$nmdebug >
The semicolon separates multiple commands entered on the same line:
CMD1; CMD2; CMD3; ...
A command list can be formed by enclosing multiple commands within curly braces.
Command lists are syntactically single commands, and are frequently used as command
parameters:
b myproc, 1,, {CMD1; CMD2; CMD3}
Unterminated command lists, which are introduced with a left curly brace, can be
continued on successive input lines without the use of the command continuation
character. The command prompt changes to indicate that a multiline command list is
being read, and it displays the current nesting level of the braces. When the final closing
right brace is encountered, the prompt changes back to the normal command line prompt:
$nmdebug > if p1 > 0 then {