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

• The ALTER SERVER command can be used only by super-group users (255,nnn).
• For the OSS message-queue server, a BACKUPCPU value of -1 means the server is to use for
its backup process the processor specified by the TACL PARAM BACKUPCPU (see “PARAMs
Used by the OSS Monitor” (page 53)). If the TACL PARAM BACKUPCPU is not defined or is
invalid, the OSS message-queue server automatically picks an available processor with the
next higher or lower processor number than the primary processor. When the TACL PARAM
BACKUPCPU specifies a valid processor number, the OSS Monitor tries to add that processor
to the OSS message-queue server configuration before bringing up the OSS message-queue
server.
• The INODECACHE, LINKCACHE, MSGMQB, MAXMQID, MAXMSG, MSGMSIZE, and
SQLTIMEOUT parameters are not valid when the OSS sockets local server is specified in an
ALTER SERVER command.
• The INODECACHE, LINKCACHE, and SQLTIMEOUT parameters are not valid when the OSS
message-queue server is specified in an ALTER SERVER command.
• The following types of OSS servers cannot be modified and are not a valid server type for the
ALTER SERVER command:
◦ OSS transport-agent servers
◦ OSS local server 2 servers (#ZLSnn)
◦ OSS resource agent servers
• Total system-wide OSS message-queue server memory is internally limited to 16 GB of actual
usage. Beginning with the J06.17 and H06.28 RVUs, it is possible to specify combinations
of MSGMQB, MAXMQID, MAXMSG, and MSGMSIZE attribute values that exceed the 16
GB internal memory limit. In the rare circumstance in which the 16 GB internal memory limit
is exceeded, out-of-memory errors are generated before reaching the specified attribute values.
• 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.
◦
◦ Changes to the OSS name server attributes do not take effect until an SCF CONTROL
SERVER command is issued. SEEPENABLED and SEEPRESPONSETIMEOUT take effect at
that point; the other OSS SEEP attributes do not take effect until the next time the OSS
SEEP is started.
◦ Altering the OSS name server's SEEPENABLED attribute 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 or modification 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
284 Open System Services Monitor