PAM Management Programming Manual

PAM Management Programming Manual—142481
6-1
6
Event Messages
Event reporting enables the system operator to monitor and control the operation of the
PAM subsystem. The Event Management Service (EMS) collects, logs, and distributes
event messages that contain information that helps the operator to monitor the network
environment, analyze failures, and recognize and handle critical problems.
This section describes the content and meaning of all event messages generated by the
PAM subsystem. In this section, object types and all tokens and their values are
represented in Data Definition Language (DDL). For an explanation of DDL, refer to the
SPI Programming Manual.
Subsystem Processes That Report Events
The PAM subsystem reports events for the following objects:
•
The LINE object represents the logical interface (LIF) access. It has the same name
as the PAM process (for example, $PAM1).
•
The PORT object represents a programmatic interface that provides applications
with link-level service access points (LSAPs). Through the LSAPs, a client or an
application program can access a LAN through file-system procedure calls.
Table 6-1
lists the PAM event messages.
Table 6-1. PAM Event Messages (page 1 of 2)
Event
Number
Symbolic Name
(ZPAM-EVT-) Description
201 AGGR-SDU-NOT-DELIV Inbound aggregate SDU not delivered.
202 BAD-AGGR-SDU Outbound aggregate SDU bad.
203 CHKPT-FAILED Checkpoint operation failed.
204 CPU-SWITCHED Processor switched because of LIF.
205 DEV-DOWN LINE is STOPPED.
206 DEV-UP LINE is STARTED.
207 INTL-ERR Internal error detected.
208 IO-PROC-ABENDED Input/output process (IOP) failed to initialize.
209 PORT-CONFIG-ERR START/STOP PORT failed due to a
configuration error.
210 PORT-CONFIG-FAILED PAM could not configure a port.
211 SM-ERR Internal state machine error detected.
212 UNEXP-CTLR-RESP PAM process received invalid response from
Token-Ring ServerNet adapter.