PAM Configuration and Management Manual

SCF for PAM
PAM Configuration and Management Manual—523349-003
3-3
SCF Object Definitions
SCF Object Definitions
SCF for PAM supports the PROCESS, LINE, PORT, MSAP, and SESSION objects,
which are defined here.
PROCESS Object
The PROCESS object is either the PAM manager process, $ZZPAM, which receives all
SPI requests from your application, or any PAM process that you create to manage
LINE objects.
A PROCESS name must be preceded by a dollar sign ($) and consist of a maximum of
seven alphanumeric characters, the first of which must be alphabetic.
LINE Object
The LINE object is used to define a PAM process. Each line controls one logical
interface (LIF) on the ServerNet adapter providing access to either the Ethernet or
token-ring LAN.
A LINE name must be preceded by a dollar sign ($) and consist of a maximum of
seven alphanumeric characters, the first of which must be alphabetic. An example of a
LINE name is:
$LAN01
Multiple PAM processes should not be configured to use the same LIF. If more than
one PAM process is configured to use a particular LIF, it might not be possible to start
ports or transfer data.
MSAP Object
The MSAP object (applicable only for PAM over token-ring LIFs) defines an access
point in PAM that provides message-system access to a SNAX process. The MSAP
object is configured permanently in the PAM process and is subordinate to the LINE
object. There is one MSAP object, #SNATR, which is used by the SNAX line handler.
An example of an MSAP name is:
$LAN01.#SNATR
You cannot add an MSAP object by using SCF for PAM. When PAM starts, it
automatically creates #SNATR.
PORT Object
The PORT object is used to define an access point that, when added and started,
provides access to a particular service. Which service is being accessed is determined
by the object subtype.