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

STOPPED
No attempt is made to start the fileset when a system load occurs. No attempt is made to
start the fileset during a restart of the OSS environment, unless the fileset has been manually
started.
If the DESIREDSTATE option is omitted, the previous value for the fileset is unchanged.
FSCKCPU processor
specifies the processor number of the processor that should run the FSCK program when a
fileset recovery is automatically initiated, where processor is in the range 0 through 15 or
is -1. The value -1 indicates that the processor used by the copy of DP2 for the fileset catalog
should be used.
If the processor indicated by a nonnegative processor value is not available, then the
processor specified for the SUBSYS FSCKCPU option is used. If that processor is also
unavailable, the processor in which the OSS Monitor is running is used.
If the FSCKCPU option is omitted, the previous value for the fileset is unchanged.
FTIOMODE { UNBUFFEREDCP | DP2BUFFEREDCP | OSSBUFFEREDCP }
specifies the input/output buffering and fault tolerance for application file opens that use the
O_SYNC option:
DescriptionValue
Use unbuffered input/output with checkpointing. This behavior provides maximum fault
tolerance but with reduced performance.
UNBUFFEREDCP
Use disk-process-buffered input/output with checkpointing. This behavior provides fault
tolerance for single failures, with better performance than UNBUFFEREDCP. DP2 buffers
DP2BUFFEREDCP
file data and checkpoints the file state to its backup process to ensure recovery from
single failures.
Use OSS-buffered input/output with checkpointing. This behavior provides fault tolerance
for single failures, with better performance than DP2BUFFEREDCP. OSS filesystem
OSSBUFFEREDCP
processes and DP2 share responsibility for buffering file data; OSS provides the buffering
whenever possible. DP2 checkpoints the file state to its backup process to ensure recovery
from single failures.
If FTIOMODE is not specified, the default behavior is UNBUFFEREDCP.
MAXDIRTYINODETIME seconds2
specifies the approximate number of seconds that cached inodes of the fileset remain in the
OSS name server’s inode cache without being updated. seconds2 must be a value in the
range 1 through 600.
When the MAXDIRTYINODETIME option is omitted, the previous value for the fileset is
unchanged.
MAXINODES maxinodes
specifies the approximate maximum number of inodes that can be created for the fileset.
maxinodes must be a value in the range 100000 through 2200000; however, HP recommends
that you specify a value less than or equal to 1000000. If the MAXINODES option is omitted,
the previous value for the fileset is unchanged.
MNTPOINT { "directory" |'directory' }
specifies the pathname of the OSS directory that serves as the mount point for the fileset. The
specified directory must already exist in the OSS file system.
The quotation marks are required. If a pathname contains a quotation mark, either specify that
quotation mark twice or use the alternate set of marks to delimit the value.
Directory names are case-sensitive.
272 Open System Services Monitor