OSI/AS Management Programming Manual

Event-Message Descriptions
Event Messages
056785 Tandem Computers Incorporated 6–3
Event-Message
Descriptions
The following pages explain in detail each event message that can be issued by the
OSI/AS subsystem. The descriptions appear in ascending order by event number; that
is, in ascending order by the ZOSI-EVT- or ZCOM-EVT- values.
Each description includes a syntax box containing the tokens that OSI/AS 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 OSI/AS event messages, or if their
values differ from one event message to another.
Tokens in OSI/AS 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 ZEMS-TKN-SUBJECT-MARK token always immediately precedes the subject
token of an event message. For more information on the subject token, refer to the
Event Management Service (EMS) Manual.
The notation used for simple tokens is a shorthand 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 OSI/AS 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.
Following the syntax box, the event-message tokens are described in the same order in
which they appear in the box. 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 ZOSI-TKN-CALLING-AE-TITLE token
is ZOSI-TNM-CALLING-AE-TITLE.
Some event messages contain error lists that report Guardian 90 errors. Although
these error lists contain Guardian 90 (ZGRD and ZFIL) tokens, the error lists
themselves are defined and composed by OSI/AS.
In the ZCOM-EVT-event descriptions, ZCOM-TKN-SUBJ-objecttype tokens represent
ZCOM event subjects. If objecttype is represented as PROC, a process is the subject of
the event. Otherwise, a communications object of the type objecttype is the subject of
the event.