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

from OFF to ON, the OSS SEEP is started if there are any OSS SEEP-protected filesets
mounted.
◦ The new values of the SEEPPROGFILENAME, SEEPPROCESSNAME, SEEPSWAPVOL,
SEEPCPU, SEEPPRI, and SEEPPARAMTEXT attributes will be used when the OSS SEEP
gets started the next time.
◦ 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 the
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 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.
• The OSS name server issues an EMS event for each successful OSS name server attribute
change.
• To migrate a primary OSS name server to another processor, do the following:
Issue the ALTER SERVER servername command to modify the CPU attribute.◦
◦ Issue the CONTROL SERVER servername, SYNC command to migrate the primary OSS
name server to the processor specified by the CPU attribute.
• To migrate a backup OSS name server to another processor, do the following:
Issue the ALTER SERVER servername command to modify the BACKUPCPU attribute.◦
◦ Issue the CONTROL SERVER servername, SYNC command to migrate the backup OSS
name server to the processor specified by the BACKUPCPU attribute.
• To migrate primary and backup OSS name servers to different processors, do the following:
Issue the ALTER SERVER servername command to modify the CPU and BACKUPCPU
attributes.
◦
◦ Issue the CONTROL SERVER servername, SYNC command to migrate the primary and
backup OSS name servers to the processors specified by the CPU and BACKUPCPU
attributes.
• Because migration of a primary and backup OSS name server is performed as a nowaited
operation, although CONTROL SERVER with the SYNC option is successful, migration might
not happen immediately. The TACL STATUS command can be used to check whether the
primary and backup OSS name server are migrated to the processors specified by the CPU
and BACKUPCPU attributes.
Examples
• To update the INODECACHE attribute of the OSS name server for the ROOT fileset after
changing it with an ALTER SERVER command, enter:
CONTROL SERVER $ZPMON.#ZPNS, SYNC
• To reset the highwater mark for the inode cache used by the OSS name server for the ROOT
fileset to the value currently in use, enter:
OSS Monitor SCF Command Reference Information 291