Notation and Special Symbols
The following notation is used in the command and command modifier syntax diagrams. The notation is also used in messages printed in response to the help command.
[J
[, ... J or [
...
]{}
An element inside brackets is optional.
Several elements stacked inside brackets means the user may select anyone or none of these elements. For example:
[AJ [BJ
[CJ User may select A or B or C or none.
When brackets are nested, parameters in inner brackets may be specified only if parameters in outer brackets are specified.
For example:
[parm i [parm2 [parm3]}}
may be entered as parmi parm2 parm3 or
parmi or
parmi pal'm2
Optional parameters vhich are not positional are shown as fo1lovs:
[parmi][parm2]
Means that the immediately preceding item in the syntax diagram may be repeated any number of times. The [, ...
J
form means that each instance of the repeated item must be preceded by a comma.An element inside curly braces is required.
When several elements are stacked within braces
in a syntax statement, the user must select one of those elements. For example:
{A}
{B}
{C} User must select either A or B or C.
I I Vertical parallel lines indicate that any or none of the options may be used in any sequence.
However, the elements may not be repeated. For example:
IAI IBI
ICI The user may choose A, B, and C; or C and A, or B alone, etc.
UPPERCASE Represent literals which are to be entered exactly as shown except that they may be
entered in lower case. Also, if an abbreviation or alternate token is listed for the item, a substitution is allowed. Lastly, only the first n characters which establish uniquely what the literal is need be entered.
Special Character Literals
The special characters + / ( ) II = are literals to be entered exactly as shown in the syntax diagrams.
italics Items printed in italics are to be
replaced with user supplied information.
Delimiters
and
AbbreviationsAll keywords and options may be abbreviated to the shortest number of characters which make the token unique. Delimiters for keywords and options include spaces and/or semicolons (:). OthE'r delimiters may be specified in the descriptions and synta.x diagrams for individual commands and command lllodifiers.
CPPER and lower case command lines are equivalent.
Diagnostic User Interface 2-17
User Set Default Values
The user may specify default values which differ from the normal diagnostic system default values for cOlllmand modifiers using the set command.
The llser may set a "universar' default value for a modifier - that is, a value which will have effect at all times - or a default value which will take effect only when a particular diagnostic is run. In either case~ if another value for the modifier is given in a run command, that value will have effect only until the diagnostic named in the run command completes execution.
Modifier default values which have been changed, either universally or for individual diagnostics, using the set command can be reset to their diagnostic system default values using the def aul t command.
For Dlore information, please see the set command and the def aul t command descriptions in this document.
Designating Devices to be Tested
Usually. when a diagnostic program is invoked the device to be tested must be named. This can be done in one of two ways: either by using the logical name of the device or giving the physical path address of the device. That is. one of the two command modifiers Idev or pdev must be given with the run command, or must be set using the set command.
The form these strings take varies among the operating systems and even from one HPPA machine to another.
For example. under the )'IPE/iX operating system the logical name (Idev) of a device is a number (e.gq 3) while in the HP- UX operating system the logical name of a device is that of a special device file (e.g .. dsk/cOdO).
The physical path address (pdev) of a device is a series of numbers separated by various punctuation marks. Each number in the series corresponds to a physical connection along the electrical pathway to the device. For example~ an HPIB device adapter might have an address of 4.2 on an HP:3000 series 930, but an address of 2/8.0 on an HP9000 series 8.50.
It is assumed that the user of the diagnostic system knows enough about the operating system and machine b4~ing worked with to determine the correct Idev or pdev for the device being tested. A utility program. SYSMAP. is provided in some diagnostic installations and may be run through the DUl (SYSMAP may NOT be available in all installations) to help determine the desired Idev or pdev.
Running Multiple Diagnostics
Several diagnostic programs may be invoked simultaneously using the run command. To do this. the user simply names all of the diagnostics to be run along with the command modifiers for each in a run command.
Examples:
DU1> run xdiag Idev 0 loop 5 erronly ydiag pdev 4.3.2 \ DU1» errpause background outfile yout
DU1> qdiag Idev 3 infile qinf & rdiag ldev
° \
DU1» sc 4/5(20,23)
All but one of the programs must be run in the background; only one program may run in the foreground at anyone time.
It is suggested that the output of programs run in the background be redirected to all
outfiff. The
our
will not impose any order on the messages received from multiple diagnostic programs but will output each message as it is received.\Vhen nlultiple diagnostic programs are invoked. the
our
will do all the internal checks and initial set up it would usually do for each of the diagnostics. THEN it will launch the diagnostics one immediately after the other using the mechanisms provided by the operating system. Theour
will not wait for one of the diagnostics to complete before launching the next.The number of diagnostics which may be run simultaneously is dependent on the nUlllber of processes the operating system will allow anyone user to run simultaneously - the diagnostic system itself does not impose a limit.
Diagnostic User Interface 2·19