Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing Filesets
Open System Services Management and Operations Guide—527191-002
5-24
FSCK Log File
If the FSCK utility fails, the fileset is put into the UNKNOWN state instead of the
STOPPED state.
If the DIAGNOSE FILESET command is issued with the OPTION STOP option and the
fileset being diagnosed has a problem that has not been corrected, a subsequent
mount of the fileset might fail.
FSCK Log File
The FSCK utility writes its output to a Guardian log file. Figure 5-4 on page 5-25 shows
two examples of FSCK log files.
The FSCK log file is created with the access permissions for the user ID of the OSS
Monitor process when that process was started.
You can specify a Guardian filename for the log file using the REPORT option of the
ADD FILESET Command, ALTER FILESET Command, or DIAGNOSE FILESET
Command. If you do not specify a filename for the log file, the log file is sent to the
spooler location specified for the REPORT attribute of the SUBSYS object. If no value
is specified in the ZOSSPARM file or if the specified spooler locations are unavailable,
the log file is put in the same volume and subvolume as the OSS Monitor code file,
OSSMON (normally a $SYSnn subvolume).