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

Managing Filesets
Open System Services Management and Operations Guide—527191-002
5-8
Automatic Restart of Filesets During OSS Monitor
Startup
Automatic Restart of Filesets During OSS Monitor Startup
The OSS Monitor uses the ZOSSFSET file to record the state of each fileset (for
example, STARTED, STOPPED, or DIAGNOSING). Whenever a fileset is started, an
entry is made indicating that the fileset is in the STARTED state. When the fileset is
stopped, the state of the fileset is changed to STOPPED.
When the OSS Monitor is started for the first time after a system load, it checks the
desired-state configuration for all filesets to determine which filesets it must start or
restart. Refer to Automatic Restart of Filesets by the Automatic Startup Service on
page 5-9 for more information.
When the OSS Monitor is restarted at any other time, it performs a restart sequence.
The OSS Monitor checks the recorded state of each fileset.
For each fileset that was left in the STARTED state, the OSS Monitor checks whether
the OSS name server for that fileset is still running. If that OSS name server is still
running and the fileset was left in the STARTED state, the OSS Monitor assumes that
the fileset is still in the STARTED state and is not corrupt.
If the OSS Monitor finds that a fileset was left in the STARTED state but its OSS name
server process is not running, one of the following might have occurred:
•
A serious problem has occurred.
•
A fileset was not properly stopped before the OSS Monitor last stopped.
•
An OSS name server failed while the OSS Monitor was not running.
That fileset might need repair.
If the OSS Monitor finds that a fileset was left in the UNKNOWN state, its OSS name
server might have failed while the OSS Monitor was not running. Again, that fileset
might need repair.
The OSS Monitor then attempts to restart each fileset suspected of needing repair, in
the order of the fileset mount points within the OSS file system directory structure,
beginning with the root fileset. If the OSS name server for a fileset reports that the
fileset cannot be restarted, the OSS Monitor runs the Guardian FSCK utility, then tries
again to restart the fileset.
The OSS Monitor restart sequence does not wait for the FSCK repair operation on a
fileset to finish; the restart sequences continues with other filesets. The OSS Monitor
does wait indefinitely for a repair operation to finish before attempting to restart the
fileset. If the attempt to restart the fileset fails, the OSS Monitor marks the fileset state
as UNKNOWN.
If the OSS Monitor is restarted while an OSS name server is running, the new instance
of the OSS Monitor continues to monitor the OSS name server and can recover from
any future failures of the OSS name server.