Enscribe Programmer's Guide

{ } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed,
of which one is actually displayed. The items in the list might be arranged either vertically, with
aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated
by vertical lines. For example:
obj-type obj-name state changed to state, caused by
{ Object | Operator | Service }
process-name State changed from old-objstate to objstate
{ Operator Request. }
{ Unknown. }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets
or braces. For example:
Transfer status: { OK | Failed }
% Percent Sign. A percent sign precedes a number that is not in decimal notation. The %þnotation
precedes an octal number. The %Bþnotation precedes a binary number. The %Hþnotation precedes
a hexadecimal number. For example:
%005400
%B101111
%H2F
P=%p-register E=%e-register
Notation for Management Programming Interfaces
The following list summarizes the notation conventions used in the boxed descriptions of error lists
in this manual
UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these names
exactly as shown. For example:
ZCOM-TKN-SUBJ-SERV
lowercase letters. Words in lowercase letters are words that are part of the notation, including
Data Definition Language (DDL) keywords. For example:
token-type
!r.. The !r notation following a token or field name indicates that the token or field is required. For
example:
ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING. !r
!o. The !o notation following a token or field name indicates that the token or field is optional. For
example:
ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !o
Change Bar Notation
Change bars are used to indicate substantive differences between this edition of the manual and
the preceding edition. Change bars are vertical rules placed in the right margin of changed portions
of text, s, tables, examples, and so on. Change bars highlight new or revised information. For
example:
The message types specified in the REPORT clause are different in the COBOL85 environment and
the Common Run-Time Environment (CRE).
The CRE has many new message types and some new message type codes for old message types.
In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and
LOGICAL-OPEN.