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

SEEPPROTECTED { ON | OFF }
specifies whether the fileset has OSS SEEP protection set or not.
ON
Specifies that the fileset is OSS SEEP-protected and OSS SEEP needs to be consulted for
file operations under this fileset that require access authorization. Only a member of both
the SOA group and Super group can change the setting of this attribute.
OFF
Specifies that the fileset is not OSS SEEP-protected.
The default value is OFF.
Considerations
• The ADD FILESET command applies only to filesets other than the root fileset.
• You cannot use the ADD FILESET command on filesets associated with an OSS name server
that is not currently configured.
• You can use the ADD FILESET command on filesets associated with an OSS name server that
is not currently running.
• You should not add all filesets to one OSS name server.
• A newly added fileset has no catalog files. The catalog files (PXINODE, PXLINK, and PXLOG)
are created the first time the fileset is started.
• The fileset READONLY attribute cannot be set when a fileset is first added. New filesets always
have a READONLY attribute value of FALSE. This attribute can be changed with the SCF ALTER
FILESET command.
• The pathname specified by the MNTPOINT option must be an existing directory, but the OSS
Monitor does not validate this until an attempt is made to start the fileset. Once validated, a
normalized version of the pathname is used for the mount point for sorting purposes, so the
apparent pathname for the mount point in an INFO FILESET command might not appear to
be the same as the specified pathname.
• The MAXDIRTYINODETIME option is meaningful only for filesets that use the BUFFERED LOG
option.
• A fileset with an updated (flushed) inode cache is considered “clean” instead of “dirty” and
does not need recovery after a failure. The more often the inode cache is flushed, the less
likely a fileset is to be corrupted by a failure and to need recovery after the failure.
The larger the value specified for seconds2, the more likely that a fileset recovery is needed
after a failure, but the faster fileset access becomes because fewer disk writes occur to update
the cache from memory. The smaller the value for seconds2, the less likely that a fileset
recovery is needed after a failure, but the slower fileset access becomes because more disk
writes occur to update the cache from memory.
Fileset recovery delays subsequent availability of the fileset, so the tradeoff for slightly faster
current access is increased probability of delayed access after a failure.
• The MAXINODES value specifies an upper bound on the number of inodes that can be created
in the fileset. It does not guarantee that MAXINODES number of inodes will be created in the
fileset. Specifying a large MAXINODES value increases the fileset recovery time in the case
of an outage. HP recommends that you specify a MAXINODES value less than or equal to
1000000.
• FTIOMODE must have a setting equal to or higher than the setting of NORMALIOMODE.
NORMALIOMODE settings are ranked, from highest to lowest:
UNBUFFEREDCP
DP2BUFFEREDCP
OSSBUFFEREDCP
262 Open System Services Monitor