PAM Programming Manual

Introduction
PAM Programming Manual—142482
1-6
The PAM Subsystem’s Role Within the System
PROCESS Object
The PAM PROCESS object determines whether a PAM process is running in the
system. The PAM PROCESS object provides the interface to the ServerNet LAN
Systems Access (SLSA) subsystem for Ethernet and token ring. The PAM process also
generates Event Management Service (EMS) messages.
A PAM process is associated with a logical interface (LIF) in the SLSA subsystem.
When PAM is started either through a TACL RUN command or through the persistence
manager, the LIF is associated with the PAM process. The persistence manager is part of
the NonStop Kernel and starts generic processes including subsystem managers such as
the PAMMAN process during the system load and any time the processors on which a
PAM process is defined come back up after a failure.
For more information about the SLSA subsystem and LIFs, refer to the LAN
Configuration and Management Manual. For information about the persistence
manager, refer to the SCF Reference Manual for the Kernel Subsystem.
LINE Object
The LINE object controls access to the specified logical interface (LIF) for a LAN
adapter such as the Ethernet 4 ServerNet adapter (E4SA). The name of the LINE object
and the PAM process object is always the same. An example of a LINE name is $PAM.
PORT Object
The PORT object is a programmatic interface that provides applications with link-level
service access points (LSAPs). Through the LSAPs, a client or application process that
is running on a Himalaya S-series server can access a local area network (LAN).
Your application (other than SNAX over token-ring applications) uses the file system to
communicate with the PAM subsystem. How your application interacts with PORTs is
Figure 1-3. PAM SCF Object Hierarchy
006CDT .CDD
PROCESS
LINE
PORT
MSAP
ETHERNET
LLC1
LLC2
SNATR
SESSION