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

E Summary of OSS Processes
This appendix summarizes the system processes related to the Open System Services environment.
Table 19 Summary of OSS Process Information
Number of ProcessesStarted ByDescription
File Name in
$SYSTEM.SYSnn
Process Name
1 per processorProcessor loadlocal server 2OSSLS2$ZLSnn
Transport-provider process for OSS AF_UNIX Release 2 sockets (AF_INET, AF_INET6, and AF_UNIX Release 1
transport-provider sockets use different names). For more information, see “Interprocess Communication Facilities”
(page 35)
1 per processorProcessor loadFile managerOSSFM$ZFMnn
Manages OSS disk file cache. If this process terminates abnormally, it halts the processor in which it runs. For more
information, see “OSS File-System Components” (page 33).
1 process pair per system$ZPMON
(recommended) or
operator command
Message-queue serverZMSGQ$ZMSGQ
Manages message queues, which UNIX processes use to exchange data. Used with msgsnd(), msgrcv(), msgctl(),
and msgget() calls, interoperates with the ipcs and ipcrm commands. For more information, see “OSS Message
Queues” (page 39) and “The OSS Message-Queue Server” (page 92)
1 process pair per system$ZPMON
(recommended) or
operator command
Local serverOSSLS$ZPLS
Transport-provider process for OSS AF_UNIX Release 1 sockets (AF_INET, AF_INET6, and AF_UNIX Release 2
transport-provider sockets use different names). For more information, see “Interprocess Communication Facilities”
(page 35)
1 process per system (not
a process pair)
$ZZKRN (recommended)
or operator command
OSS monitorOSSMON$ZPMON
Manages filesets (ADD, START, STOP, DIAGNOSE) and servers (message-queue server, local server, transport agents,
name servers). The OSS monitor must be started before OSS can be started. After OSS is started:
• The OSS Monitor process can stop without affecting the running OSS system.
• The OSS monitor can start OSS filesets and servers, depending on how the OSS monitor is configured. OSS Monitor
configuration files are kept in the $SYSTEM.ZXOSSMON subvolume.
The OSS monitor must be running for the AUTOSTART feature to work, which automatically starts OSS filesets and
servers. For more information about AUTOSTART, see the “ALTER SERVER Command” (page 278). For more information
about the OSS monitor, see “Open System Services Monitor” (page 251).
Multiple process pairs per
system
$ZPMON (starts the
name server when the
Name serverNS$ZPNS,
$ZPNH, or
$process_name first fileset associated
with the name server is
started, stops the name
server when last fileset
associated with the name
server is stopped)
$ZPNS is default name for the ROOT, HOME, and TEMP filesets for single-enclosure or preconfigured systems. $ZPNS
is the default name for the ROOT and TEMP filesets for multiple-enclosure systems. $ZPNH is the default name for the
HOME fileset for multiple-enclosure systems. Other name server processes can be configured to manage other filesets.
Name server processes can use any legal process name. The OSS name server:
• Maintains the file and directory catalogs for the OSS environment
• Translates the file name mapping between the OSS pathname and the underlying Guardian filename
• Provides addressing information for AF_UNIX sockets.
For more information, see “The OSS Name Servers” (page 92) and “Starting (Mounting) or Restarting Filesets”
(page 146).
409