PAM Management Programming Manual

Introduction
PAM Management Programming Manual—142481
1-3
The PAM Subsystem’s Role Within the System
•
PAM clients on page 1-3
•
A file-system interface on page 1-3 for applications that need to access the port
•
A message-system interface (on page 1-3) that enables the SNAX Extended Facility
(SNAX/XF) or the SNAX Advanced Peer Networking (SNAX/APN) products to
access the TRSA
•
The Subsystem Programmatic Interface (SPI) on page 1-4 for management
applications and event management
•
The management interfaces on page 1-3 for interactive control-and-inquiry
•
The ServerNet LAN Systems Access (SLSA) Subsystem on page 1-4
•
The PAM Process on page 1-4
•
The PAM Manager (PAMMAN) Process on page 1-5
•
Communications adapters including:
•
MFIOB (Multifunction I/O Board/Ethernet) on page 1-6
•
FESA (Fast Ethernet ServerNet Adapter) on page 1-6
•
E4SA (Ethernet 4 ServerNet Adapter) on page 1-6
•
TRSA (Token-Ring ServerNet Adapter) on page 1-6
PAM Clients
PAM clients are subsystems or user applications that access the port interface or the
LLC2 interface by using file-system or message-system calls. Examples of applications
include AppleTalk and Open System Interconnection (OSI) subsystems and customer
applications. The SNAX I/O process is a client that accesses the PAM LLC2 interface
using message-system calls.
File-System Interface
The file-system interface is a set of internal procedure calls that enables applications to
communicate with ports on the PAM process.
Message-System Interface
The message-system interface is a set of internal procedure calls that enables the
SNAX/XF and SNAX/APN products to communicate with the PAM process.
Management Interfaces
The PAM management interfaces consist of the Subsystem Control Facility (SCF) and
Subsystem Programmatic Interface (SPI). SCF provides an interactive interface for
control-and-inquiry and accesses the PAM subsystem through SPI.