WAN Subsystem Configuration and Management Manual

About This Manual
WAN Subsystem Configuration and Management Manual—522463-011
xxiv
Notation for Subnet
UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type 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
Notation for Subnet
The following describes the notation conventions for SUBNET and subnet used in this
manual.
UPPERCASE LETTERS. Uppercase letters indicate the NonStop TCP/IP, Parallel Library
TCP/IP, or NonStop TCP/IPv6 SCF SUBNET object. For example:
Port A is identified by logical interface (LIF) 018, which uses
a SUBNET on the TCP/IP process named $ZB018 in processor 0.
lowercase letters. Lowercase letters indicate the general networking term for subnet. For
example:
Multicast datagrams that have a Time-To-Live (TTL) value of 1
are forwarded only to hosts on the local subnet.
Change Bar Notation
Change bars are used to indicate substantive differences between this manual and its
preceding version. Change bars are vertical rules placed in the right margin of changed
portions of text, figures, 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.