Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

The OSS Sockets Local Servers
The OSS sockets local servers vary and depend on whether the system is using AF_UNIX Release 2
software or AF_UNIX Release 1 software.
AF_UNIX Release 2 Software
Systems running J06.05 and later J-series RVUs and H06.16 and later H-series RVUs are using
AF_UNIX Release 2 software.
For systems using AF_UNIX Release 2 software, there is an OSS sockets local server 2 (LS2) server
for each processor. The default OSS local server 2 server name is $ZLSnn, where nn is the processor
number.
If there are no open AF_UNIX sockets in a processor, you can start and stop the OSS sockets local
server 2 servers for that processor using the OSS Monitor SCF commands START SERVER and
STOP SERVER (see “START SERVER Command” (page 313) and “STOP SERVER Command” (page 332)
for detailed information about these commands). You cannot add, modify, or remove these
processes.
AF_UNIX Release 1 Software
For systems using AF_UNIX Release 1 software, the OSS sockets local server can run as a single
process or as a fault-tolerant process pair. The server uses the default process name $ZPLS.
The backup server process preserves socket access if the primary server process fails. You can
control the processor in which the backup server process runs.
You can start and stop the OSS sockets local server using the OSS Monitor SCF commands START
SERVER and STOP SERVER (see “START SERVER Command” (page 313) and “STOP SERVER
Command” (page 332) for detailed information about these commands).
If the OSS sockets local server fails completely, you can restart it. Server failure can be detected
from the Event Management Service (EMS) messages issued to your system logs.
The OSS Transport-Agent Servers
There is one OSS transport-agent server (used for OSS sockets communication) for each processor
in your system. The process name is $ZTAnn, where nn is the processor number. Each OSS
transport-agent server is automatically started when the processor it runs on is started.
You can start and stop the OSS transport-agent servers using the OSS Monitor SCF START SERVER
command and STOP SERVER command. You cannot add, modify, or remove an OSS transport-agent
server.
If an OSS transport-agent server fails completely, you can restart it. Server failure can be detected
from the Event Management Service (EMS) messages issued to your system logs.
The OSS Resource Agent Servers
Beginning with the J06.14 and H06.25 RVUs, each processor in your system uses one resource
agent server for collecting OSS resource information. The process name is $ZRAnn, where nn is
the processor number. Each OSS resource agent server is automatically started when the processor
it runs on is started.
You can start and stop the OSS resource agent servers using the OSS Monitor SCF START SERVER
command and STOP SERVER command. (Wildcarding can be used to stop resource agent servers;
however, it cannot be used to start resource agent servers.) You cannot add or remove an OSS
resource agent server.
IMPORTANT: All of the information in this OSS Resource Agent Servers section is for HP NonStop
RVUs beginning with J06.14 and H06.25.
Introducing the OSS Servers 93