Open System Services Management and Operations Guide (G06.29+, H06.07+)

Open System Services Monitor
Open System Services Management and Operations Guide—527191-005
12-26
ALTER FILESET Command
If the READONLY option is omitted, the write permission granted to users of the
fileset is not changed.
REPORT filename3
specifies the Guardian filename for the report file to be generated when FSCK
performs an automatic recovery for this fileset; filename3 must be a Guardian
spooler location.
If the specified spooler is unavailable, FSCK uses a file-code-180 file (a C
language text file) named $SYSTEM.SYSnn.ZXdevicelabel as its outfile; nn
indicates the currently running system installation and devicelabel is the value
specified for the DEVICELABEL option of the fileset. If the file
$SYSTEM.SYSnn.ZXdevicelabel already exists, FSCK appends its new output
to the existing file. The CTOEDIT command can be used to convert the file code-
180-file to a file-code-101 EDIT file.
When the REPORT option is omitted, the previous value for the fileset is
unchanged.
Considerations
•
The ALTER FILESET command can be used only by super-group users (255,nnn).
•
You can use the ALTER FILESET command on a fileset that is not in the
STOPPED state. However, the changes do not take effect until the fileset is
stopped and restarted.
•
Assigning a new storage-pool file to a fileset has no effect on existing OSS files in
the fileset. New OSS files will be created only on disk volumes listed in the new
storage-pool file. Disk volumes with existing OSS files in the fileset remain a part of
the fileset’s storage pool even when they are not listed in the storage-pool file (are
not in the creation pool).
•
If a fileset is in the STARTED state, you cannot change its OSS name server
process.
•
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.