Tree Traversal Rules
Command headers are created by traversing down the command tree. A
legal command header from the command tree in figure 5-1 would be
:MMEMORY:INITIALIZE
. This is referred to as a compound header. As
shown on the tree, branches are always preceded by colons. Do not add
spaces around the colons. The following two rules apply to traversing the tree:
•
A leading colon (the first character of a header) or a terminator places the
parser at the root of the command tree. For example, the colon preceding
MMEMORY
(
:MMEMORY
) in the above example places the parser at the root
of the command tree.
•
Executing a subsystem command places you in that subsystem until a
leading colon or a terminator is found. The parser will stay at the colon
above the keyword where the last header terminated. Any command
below that point can be sent within the current program message without
sending the keywords(s) which appear above them. For example, the
colon separating
MMEMORY
and
INITIALIZE
is the location of the
parser when this compound header is parsed.
The following examples are written using HP BASIC 6.2 on a HP 9000 Series
300 Controller. The quoted string is placed on the bus, followed by a carriage
return and linefeed (CRLF). The three Xs (XXX) shown in this manual after
an
ENTER
or
OUTPUT
statement represents the device address required by
your controller.
Example
In this example, the colon between
SYSTEM
and
HEADER
is necessary since
SYSTEM:HEADER
is a compound command. The semicolon between the
HEADER
command and the
LONGFORM
command is the required
<program
message unit separator>
. The
LONGFORM
command does not need
SYSTEM
preceding it, since the
SYSTEM:HEADER
command sets the parser
to the
SYSTEM
node in the tree.
OUTPUT XXX;":SYSTEM:HEADER ON;LONGFORM ON"
Programming and Documentation Conventions
Tree Traversal Rules
5–8
Summary of Contents for 16501A LOGIC
Page 2: ...ii ...
Page 12: ...Contents 8 ...
Page 14: ......
Page 15: ...1 Introduction to Programming ...
Page 38: ...1 24 ...
Page 39: ...2 Programming Over HP IB ...
Page 45: ...3 Programming Over RS 232 C ...
Page 55: ...4 Programming Over LAN ...
Page 68: ...4 14 ...
Page 69: ...5 Programming and Documentation Conventions ...
Page 81: ...6 Message Communication and System Functions ...
Page 91: ...7 Status Reporting ...
Page 93: ...Figure 7 1 Status Byte Structures and Concepts Status Reporting 7 3 ...
Page 97: ...Figure 7 2 Service Request Enabling Status Reporting Key Features 7 7 ...
Page 100: ...Figure 7 3 Parallel Poll Data Structure Status Reporting Parallel Poll 7 10 ...
Page 105: ...8 Error Messages ...
Page 110: ...8 6 ...
Page 112: ......
Page 113: ...9 Common Commands ...
Page 116: ...Figure 9 1 Common Commands Syntax Diagram Common Commands 9 4 ...
Page 122: ...Figure 9 2 IST Data Structure Common Commands IST Individual Status 9 10 ...
Page 132: ...9 20 ...
Page 133: ...10 Mainframe Commands ...
Page 135: ...Figure 10 1 Mainframe Commands Syntax Diagram Mainframe Commands 10 3 ...
Page 136: ...Figure 10 1 continued Mainframe Commands Syntax Diagram continued Mainframe Commands 10 4 ...
Page 159: ...11 SYSTem Subsystem ...
Page 161: ...Figure 11 1 System Subsystem Commands Syntax Diagram SYSTem Subsystem 11 3 ...
Page 172: ...11 14 ...
Page 173: ...12 MMEMory Subsystem ...
Page 175: ...Figure 12 1 MMEMory Subsystem Commands Syntax Diagram MMEMory Subsystem 12 3 ...
Page 198: ...12 26 ...
Page 199: ...13 INTermodule Subsystem ...
Page 201: ...Figure 13 1 Intermodule Subsystem Commands Syntax Diagram INTermodule Subsystem 13 3 ...
Page 216: ...13 18 ...
Page 217: ...14 TGTctrl Subsystem ...
Page 219: ...Figure 14 1 Targetcontrol Subsystem Commands Syntax Diagram TGTctrl Subsystem 14 3 ...
Page 220: ...Figure 14 1 continued Targetcontrol Subsystem Commands Syntax Diagram TGTctrl Subsystem 14 4 ...
Page 233: ...Part 3 15 Programming Examples 15 1 Programming Examples ...
Page 234: ......
Page 235: ...15 Programming Examples ...