PAM Configuration and Management Manual

Introduction

PAM Configuration and Management Manual—523349-003

2-13

Starting PAM Using the Persistence Manager

Starting PAM through the persistence manager is recommended. The persistence

manager starts the PAM process automatically when the system is brought up or the

processor is reloaded.

When starting the PAM process using the persistence manager, you can start it as a

process pair in either the fixed processor configuration or the dynamic processor

configuration. The dynamic processor configuration is recommended because the

persistence manager will start the process in either the specified primary or backup

processors, depending on which one is available first. (For more information about the

persistence manager, see the SCF Reference Manual for the Kernel Subsystem.)

The PAM subsystem must start after the ServerNet LAN Systems Access subsystem

(SLSA). Therefore, you must specify the STARTMODE as APPLICATION.

Starting PAM Using TACL

You can start the PAM process through a TACL RUN command, specifying the startup

parameters as command-line arguments. However, you must configure the LAN

adapters through the SLSA subsystem before starting the PAM process. For the

procedures for configuring the adapters, see the LAN Configuration and Management

Manual.

QUE-DEPTH (or Q) is the maximum number of application messages PAM

queues after it receives a queue-full indication from the

SLSA LAN driver. Queue depth must be within the range

of 256 through 4096. The default is 1024.

Note. Whenever you stop the PAM process by using SCF STOP PROCESS, you must disable

auto-restart in the persistence manager if you do not want the persistence manager to bring up

the PAM process automatically. For more information about altering the defaults in the

persistence manager, see the SCF Reference Manual for the Kernel Subsystem.