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

The OSS Name Servers
Open System Services supports multiple OSS name server processes. This feature can improve
performance by allowing multiple processes to share the task of resolving OSS pathnames.
You can run as many OSS name servers as you need on a system simultaneously. Each fileset is
managed by only one OSS name server; however, one OSS name server can manage many
filesets. You can use OSS Monitor SCF commands to change the configuration of filesets and OSS
name servers on your system as the demands of your system vary.
An OSS name server can run as a single process or as a fault-tolerant process pair. The OSS name
server for the root fileset uses the process name $ZPNS; OSS name servers for all other filesets
can use any process name with a length of up to 5 characters plus the dollar sign.
If there is a backup server process, it preserves mounted fileset data as well as fileset access if the
primary server process fails. You can control the processor in which the backup server process
runs.
The OSS name servers are configured and controlled through OSS Monitor SCF commands. See
“Open System Services Monitor” (page 251), for more information about those SCF commands.
The OSS Message-Queue Server
The OSS message-queue server runs as a fault-tolerant process pair. The server uses the default
process name $ZMSGQ.
The backup server process preserves message-queue data as well as the queues themselves 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 message-queue 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 message-queue server fails completely, you can restart it. Server failure can be detected
from the Event Management Service (EMS) messages issued to your system logs.
NOTE: After the OSS message-queue server is started, the attribute values for resources such as
MAXMQID and MAXMSG cannot be dynamically changed. You can execute multiple SCF ALTER
SERVER commands, but that only changes the values stored in the OSS Monitor database. For
changed attribute values to take effect, you must stop the OSS message-queue server, and then
restart it.
Beginning with the J06.17 and H06.28 RVUs, resource limits for the OSS message-queue server
are increased. Table 6 lists the limits for various J-series and H-series RVUs.
Table 6 OSS Message-Queue Server Limits
New Default
2
New Maximum
2
Original Default
1
Original Maximum
1
Minimum
Resource
Name
1048576 (1 MB)1073741824 (1 GB)65535655351MSGMQB
(bytes)
256163843210241MAXMQID
409683886081024163841MAXMSG
320002000000 (~2 MB)32000320001MSGMSIZE
(bytes)
1
Prior to the J06.17/H06.28 RVUs
2
As of the J06.17/H06.28 RVUs
92 Managing Servers