PAM Management Programming Manual

Communicating With the PAM Subsystem

PAM Management Programming Manual—142481

2-2

Running an EMS Consumer Distributor

Before your management application can retrieve event messages generated by the PAM

subsystem and other subsystems, you must start an EMS consumer distributor process,

open this process for communication, and specify the source of event messages with a

CONTROL command. The EMS Manual provides complete instructions for taking these

steps.

To avoid receiving all event messages from all subsystems (something you will rarely

want to do), you must install a filter to select only those messages that your application

intends to act upon. You install your filter when you start the consumer distributor. Filers

are written in the EMS filter language, which is described in the EMS Manual.

Communicating With Other Subsystems

The PAM process uses the services provided by the ServerNet LAN Systems Access

(SLSA) subsystem, which configures and controls the Token-Ring ServerNet adapter

(TRSA) and the Ethernet 4 ServerNet adapter (E4SA). In addition, you must use the

SNAX/XF or SNAX/APN management interfaces to create LLC2 ports within a PAM

process.

Figure 2-1

shows the indirect relationship between the SNAX/XF and SNAX/APN

subsystems and the TRSA.

You can write a management application that communicates with the SLSA, SNAX/XF,

and SNAX/APN subsystems—or any other subsystem that has a management

programming interface—in addition to the PAM subsystem.

Figure 2-1. SNAX and the TRSA

Token Ring

Adapter

PAM SLSA

SNAX

Service Manager

SNAX

Line Handler

Process

008CDT .CDD