Distributed Name Service (DNS) Management Programming Manual

Event-Message Descriptions
Event Messages
6–16 46958 Tandem Computers Incorporated
Event-Message
Descriptions
The following pages explain in detail each event message issued by the DNS
subsystem. The descriptions appear in ascending order by event number; that is, in
ascending order by the ZDNS-EVT- values.
Each description includes a syntax box containing the tokens that DNS can place in the
message buffer (in addition to the common tokens listed in Table 6-2). Tokens appear
in the box if they are not present in all DNS event messages, or if their values differ
from one event message to another. In this subsection, a pair of ampersands (&&) is
used to indicate that a line was broken to fit within the margins of the page.
Tokens in DNS event messages are unconditional, conditional, or Tandem internal. In
the event-message descriptions in this section, all tokens are unconditional unless
labeled otherwise. An unconditional token is a token that is always present in a
particular event message. A conditional token is one that is sometimes, but not
always, present in a particular event message. Tandem internal tokens are listed in the
syntax box because your programs can encounter them when scanning the buffer;
however, they are not described, because your application programs should not use
their values. (All Tandem internal tokens are also conditional.) If an unusual event
occurs, you may need to furnish the values of Tandem internal tokens to your Tandem
representative.
The notation used for simple tokens is a shortened version of the essential information
given in the DDL TOKEN-CODE statement.
The syntax box also contains the text version of the event message, as provided by the
EMSTEXT procedure and displayed on the operator console. For DNS event
messages, there is no difference between the display format and the console-
compatible format of the text. For further information on the EMSTEXT procedure,
event-message text formats, and the standard event-message header, refer to the Event
Management Service (EMS) Manual.
Descriptions of simple tokens in this section do not identify the token numbers of the
tokens. However, the symbolic names of the token numbers can be derived from the
token names by simply replacing -TKN- with -TNM-. For example, the token number
of the ZDNS-TKN-SUBJECT token is ZDNS-TNM-SUBJECT. Appendix A provides a
complete list of all DNS token codes and gives the token type or token map name for
each.