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

Beginning with the J06.05 and H06.16 RVUs, when the OSS Monitor creates a default ZOSSSERV
file, it contains a #ZLSnn entry for every possible per-CPU instance of the OSS sockets local server
2 server process, $ZLSnn. Currently, 16 CPUs are supported (00–15), and the ZOSSSERV entries
are #ZLS00–#ZLS15. These entries cannot be changed and have the following default values:
Default ValueAttribute
-1 (does not run as a process pair)BACKUPCPU
nnCPU
#ZLSnnSERVER
LOCAL2TYPE
The OSS Monitor updates the OSS sockets local server 2 server entries in the ZOSSSERV file each
time the OSS Monitor starts.
If your system is upgraded to either the J06.05 RVU (or later J-series RVU) or the H06.16 RVU (or
later H-series RVU), the OSS Monitor automatically upgrades an existing ZOSSSERV file.
Systems Running AF_UNIX Release 1 Software
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. For
systems running AF_UNIX Release 2 software, this entry is maintained to allow fallback to an
RVU that does not support AF_UNIX Release 2 software.
• 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.
Beginning with RVU G06.10, when HP shipped a system with the OSS environment preconfigured,
the #ZPLS entry matched the default, as follows:
Initial Values When ZOSSSERV Is
Delivered on a Preconfigured System
Default Values When ZOSSSERV Is
Created by the OSS MonitorAttribute
00BACKUPCPU
11CPU
#ZPLS#ZPLSSERVER
LOCALLOCALTYPE
114 Managing Servers