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

message-queue server, and OSS transport-agent servers are started by the START SERVER
command.
• You must be a member of the super group (255, nnn) to use this command.
• The ADD SERVER command is intended to be used for OSS name servers of filesets other than
the root fileset.
• When Open System Services is first installed, the OSS Monitor adds the default OSS name
server for the root fileset the first time the OSS Monitor is run. The OSS sockets local server
or local server 2 servers, OSS message-queue server, OSS transport-agent servers, and OSS
resource agent servers are added, if needed, at the startup of the OSS Monitor process.
• HP recommends that you choose a large and equal value for both INODECACHE and
LINKCACHE attributes to minimize disk I/O and to increase performance. However, choosing
a large value for both INODECACHE and LINKCACHE attributes results in high memory usage
by the Name Server. A typical INODECACHE cache entry is 300 bytes and a typical
LINKCACHE cache entry is 120 bytes. As an example, setting the caches at 64000 results
in a total memory requirement for the two caches of approximately 26,880,000 bytes (25.6
MB).
• OSS SEEP considerations (J06.15/H06.26 and subsequent RVUs):
Only a member of both the SOA group and Super group can configure any of the OSS
SEEP-related attributes.
◦
◦ Adding a server with the SEEPENABLED attribute set to ON results in the creation of the
OSS SEEP, provided there is at least one SEEP-protected fileset mounted under this server.
◦ The setting of the OSS name server attributes for OSS SEEP configuration is unconditionally
audited and generates an EMS event.
◦ If the CPU specified through the SEEPCPU attribute is not available at startup, the OSS
SEEP is created using the backup CPU specified in the first word of
startup-param-text. If the backup CPU is not specified or available, the OSS SEEP
is started in the same CPU as the primary OSS name server.
◦ The startup message sent to the OSS SEEP includes the backup CPU, if specified. In the
case where the OSS SEEP is created using the backup CPU specified, the backup CPU
value is replaced with the configured value of SEEPCPU in the startup message sent to
the OSS SEEP.
◦ While attempting to start the OSS SEEP with the configured process name, if there is
already a process running with the same name, then the OSS name server stops the
process and starts the OSS SEEP with that name. An EMS event is generated to notify the
stopping of the running process.
Example
To add the OSS name server #ZPNS1 to the system, with processor 0 as the primary processor
and processor 1 as the backup processor or as the primary processor when processor 0 is
unavailable after 30 seconds during a automatic restart, a maximum of two attempts at restart, a
maximum of 4096 inode cache entries and 4096 link cache entries, and a timeout of 60 seconds
for responses from SQLCAT, enter the following command:
ADD SERVER #ZPNS1, CPU 0, BACKUPCPU 1, INODECACHE 64000, &
LINKCACHE 64000, SQLTIMEOUT 60, BACKUPCPUOK TRUE, &
MAXWAITTIME 30, AUTORESTART 2
ALTER FILESET Command
The ALTER FILESET command changes the configuration of a fileset administered through the OSS
Monitor. The information entered in the command is added to or altered in the ZOSSFSET file.
OSS Monitor SCF Command Reference Information 269