SNAX/APC Configuration and Management Manual

SNAX/APC Configuration and Management Manual—138787
E-1
E
Event Management
The SNAX/APC subsystem provides information about events that occur in the
subsystem by issuing event messages. A management application can obtain these event
messages by opening an Event Management Service (EMS) distributor process and
requesting the messages. The application can also specify that a filter be applied to
select certain event messages.
This appendix describes the event messages that the SNAX/APC subsystem can issue
and specific programming considerations for dealing with SNAX/APC event messages
in an application.
For general information on how an application obtains event messages, refer to the
Event Management Service (EMS) Manual.
In this appendix, event message tokens and their values are represented in the Data
Definition Language (DDL). For a quick explanation of DDL, refer to the appendix
“Overview of DDL for SPI” in the SPI Programming Manual.
Before You Report a Problem
Some error messages are not easily recoverable and require you to seek additional help.
In these cases, follow the standard procedures at your site for contacting the appropriate
support personnel. These procedures might involve contacting the Tandem NonStop
Support Center or your local Tandem support representative.
Collect any relevant information before reporting the problem. The minimal
information required for reporting a problem against T9096 SNAX/APC includes:
1. System number and version procedure from the APCOBJ module; the version
procedure can be obtained by entering VPROC or BIND:
VPROC
Enter filename:
>$system-volume.subvolume.APCOBJ
2. Versions of all related products.
3. Problem description and symptoms—include a description of the problem and the
accompanying symptoms.
4. SNAX/APC trace file showing the problem—the trace file is assigned either at
SNAX/APC startup or when a dynamic trace is invoked. It is recommended that the
trace be taken specifying SELECT ALL so that support and problem resolution
personnel can see the entire picture. A trace of the problem is mandatory for
problem resolution.
If the problem seems to be in establishing sessions, specify tracing using the
SNAX/APC startup parameters (see Part I, SNAX/APC Planning and
Configuration).