Notation For Messages - HP Neoview Messages Manual

Table of Contents

Advertisement

Parentheses, commas, semicolons, and other symbols not previously described must be typed
as shown. For example:
DAY (datetime-expression)
@script-file
Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required
character that you must type as shown. For example:
"{" module-name [, module-name]... "}"
Item Spacing
Spaces shown between items are required unless one of the items is a punctuation symbol such
as a parenthesis or a comma. For example:
DAY (datetime-expression)
DAY(datetime-expression)
If there is no space between two items, spaces are not permitted. In this example, no spaces are
permitted between the period and any other items:
myfile.sh
Line Spacing
If the syntax of a command is too long to fit on a single line, each continuation line is indented
three spaces and is separated from the preceding line by a blank line. This spacing distinguishes
items in a continuation line from items in a vertical list of selections. For example:
match-value [NOT] LIKE pattern
[ESCAPE esc-char-expression]

Notation for Messages

This list summarizes the notation conventions for the presentation of displayed messages in this
manual.
Bold Text
Bold text in an example indicates user input typed at the terminal. For example:
ENTER RUN CODE
?123
CODE RECEIVED:
The user must press the Return key after typing the input.
Nonitalic text
Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly
as shown. For example:
Backup Up.
lowercase italic letters
Lowercase italic letters indicate variable items whose values are displayed or returned. For
example:
p-register
process-name
[ ] Brackets
Brackets enclose items that are sometimes, but not always, displayed. For example:
Event number = number [ Subject = first-subject-value ]
8
123.00

Advertisement

Table of Contents
loading

Table of Contents