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

DESIREDSTATE
INODECACHE
LINKCACHE
MAXWAITTIME
SQLTIMEOUT
NOTE:
Beginning with the J06.15 and H06.26 RVUs, you might also need to reconfigure OSS
SEEP-related attributes for the OSS name server. For details of these attributes, see “ALTER
SERVER Command” (page 278). Only a member of both the SOA group and Super group are
allowed to set or alter the OSS SEEP-related attributes for the OSS name server.
3. If you changed only one or more of these attributes:
AUTORESTART
BACKUPCPUOK
MAXWAITTIME
you have completed the task. The changes take effect immediately.
4. If you changed only one or more of these attributes:
BACKUPCPU
CPU
INODECACHE
LINKCACHE
SQLTIMEOUT
SEEPENABLED
1
SEEPRESPONSETIMEOUT
1
use the SCF CONTROL SERVER command with the SYNC option for the OSS name server.
You have completed the task. The changes take effect immediately.
5. If you changed only one or more of these attributes:
SEEPPROGFILENAME
1
SEEPPROCESSNAME
1
SEEPSWAPVOL
1
SEEPCPU
1
SEEPPRI
1
SEEPPARAMTEXT
1
use the SCF CONTROL SERVER command with the SYNC option for the OSS name server.
The new attribute values take effect only when the OSS SEEP is started the next time.
6. Otherwise, use the following OSS Monitor SCF command to identify all filesets managed by
that server:
INFO FILESET $ZPMON.*, DETAIL
See the “INFO FILESET Command” (page 296) for a description of the command output.
7. Warn your users to make sure that all their files in affected filesets are closed and all OSS
shell sessions using those filesets are terminated. You can use a method similar to the one
described under “Manually Stopping the OSS File System and the OSS Environment” (page 47).
8. Do one of the following:
• If the OSS name server is the server for the root fileset, stop all filesets by entering the
following OSS Monitor SCF command:
1. Beginning with the J06.15 and H06.26 RVUs.
136 Managing Servers