Open System Services Management and Operations Guide (G06.29+, H06.07+)

Managing Servers
Open System Services Management and Operations Guide527191-005
4-15
Configuration Files Used for the OSS Name Servers
This file must be maintained by the system manager using the SCF ADD SERVER,
ALTER SERVER, and DELETE SERVER commands. ZOSSSERV must be present
before the root fileset is first mounted and before the first OSS name server is started.
Entries in the ZOSSSERV file must follow these rules:
There should always be a #ZPNS entry for the root OSS name server process,
$ZPNS. OSS name servers that manage other filesets must also have entries in
this file; use the SCF ADD SERVER Command to add these entries.
Primary and backup processor numbers should be assigned such that no single
processor failure affects more than one server process pair.
HP recommends that you specify processors not used by either the OSS Monitor
or the FSCK utility (as specified by the ZOSSPARM file FSCKCPU value).
Certain changes to the ZOSSSERV file take effect only when the corresponding server
is stopped and restarted.
When a default ZOSSSERV file is created by the OSS Monitor, it contains an entry for
the OSS name server process of the root fileset, $ZPNS.
Beginning with RVU G06.10, when HP shipped a system with the OSS environment
preconfigured, the root fileset OSS name server entry differed from the default, as
follows:
Beginning with RVU G06.15, when HP shipped a system with the OSS environment
preconfigured or you used the OSSSETUP utility to configure your system,
ZOSSSERV contained these initial OSS name server entries:
Attribute
Default Values When
ZOSSSERV Is Created by the
OSS Monitor
Initial Values When ZOSSSERV Was
Delivered on a Preconfigured
System
BACKUPCPU 1 0
CPU 0 1
INODECACHE 4096 4096
LINKCACHE 4096 4096
SERVER #ZPNS #ZPNS
SQLTIMEOUT 60 60
TYPE NAME NAME
Attribute
Preconfigured or Single-
Enclosure System Multiple-Enclosure System
BACKUPCPU 1 1
CPU 0 0
INODECACHE 4096 4096
LINKCACHE 4096 4096