Notation For Messages - HP NonStop RDF J-series RVUs Management Manual

!i and !o
In procedure calls, the !i notation follows an input parameter (one that passes data to the
called procedure); the !o notation follows an output parameter (one that returns data to the
calling program). For example:
CALL CHECKRESIZESEGMENT (
!i,o
In procedure calls, the !i,o notation follows an input/output parameter (one that both passes
data to the called procedure and returns data to the calling program). For example:
error := COMPRESSEDIT ( filenum ) ;
!i:i
In procedure calls, the !i:i notation follows an input string parameter that has a corresponding
parameter specifying the length of the string in bytes. For example:
error := FILENAME_COMPARE_ (
!o:i
In procedure calls, the !o:i notation follows an output buffer parameter that has a
corresponding input parameter specifying the maximum length of the output buffer in bytes.
For example:
error := FILE_GETINFO_ (

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.
Italic Text
Italic text indicates 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 ]
28
segment-id
, error
filename1:length
, filename2:length ) ;
filenum
, [ filename:maxlen ] ) ;
123.00
!i
) ; !o
!i,o
!i:i
!i:i
!i
!o:i