Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-20
Configuration Database Files Used for the OSS
Sockets Local Server
If your system is upgraded to a G06.17 or later G-series RVU, the OSS Monitor
automatically upgrades an existing ZOSSSERV file and creates a backup copy of your
original file in $SYSTEM.ZXOSSMON.ZOLDSERV.
Configuration Database Files Used for the OSS Sockets Local
Server
To start an OSS sockets local server, the OSS Monitor requires a ZOSSSERV file to be
in the subvolume $SYSTEM.ZXOSSMON.
The ZOSSSERV file is the OSS sockets local server configuration database, and it
contains an automatically created entry that identifies the characteristics of the OSS
sockets local server process.
This file must be edited by the system manager using the SCF ALTER SERVER
command. ZOSSSERV need not be configured before the root fileset is first mounted
or before the first OSS sockets local server is started. The default configuration for
ZOSSSERV that is created by OSSMON is complete.
Entries in the ZOSSSERV file must follow these rules:
•
There must always be a #ZPLS entry for the OSS sockets local server process,
$ZPLS.
•
Primary and backup processor numbers must be assigned such that no single
processor failure affects more than one server process pair.
HP recommends that you specify processors in the ZOSSSERV file that are not used
by either the OSS Monitor or the FSCK utility (as specified by the ZOSSPARM file
FSCKCPU value).
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 default OSS sockets local server process, $ZPLS.
MAXMQID 32 32
MAXMSG 32 * MAXMQID = 1024 32 * MAXMQID = 1024
MAXWAITTIME 0 0
MSGMSIZE 32000 32000
SERVER #ZPLS #ZPLS
TYPE LOCAL LOCAL
Attribute Single-Enclosure System
Multiple-Enclosure
System (page2of2)