PAM Management Programming Manual

Introduction
PAM Management Programming Manual—142481
1-9
Interactive Interfaces
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
similar to how an application interacts with files; the application can open PORTs,
perform reads and writes to exchange data with a remote LAN entity, then close them.
The PORT object provides the following types of LSAPs:
Figure 1-5
shows the relationship between application types and port interfaces.
Ethernet The Ethernet PORT allows direct access to the DIX-compatible Ethernet
interface (using a protocol type field instead of a length field as in IEEE
802.3). Multiple Ethernet-type PORT objects can be configured, one for
each Ethernet protocol type. Access to the Ethernet interface is made
through file-system procedure calls and a formatting library that is used to
format aggregate service data units (SDUs).
LLC1 The Logical Link Control, Type 1 interface (LLC1) PORT gives LLC1
applications access to the LLC type 1 connectionless (IEEE 802.2) level-2
interface. Multiple LLC1-type PORT objects can be configured, one for
each LLC LSAP. Access to the LLC1 interface is made through file-
system procedure calls and a formatting library that formats aggregate
service data units (SDUs).
The LLC1 interface also provides send-and-receive access to LLC2
frames in TRSA and E4SA. The implementation of the LLC2,
connection-oriented protocol is the responsibility of your application.
Figure 1-5
shows the relationship between the applications, the LLC1
interface, and the adapters.
LLC2 The Logical Link Control, Type 2 interface (LLC2) PORT gives SNAX
over token ring access to the LLC type 2 connection-oriented (IEEE
802.2) level 2 interface. The PAM process adds the LLC2 PORT when
SNAX opens a SAP through the SNATR MSAP.