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

Messages
Open System Services Management and Operations Guide—527191-005
A-46
Numbered Messages
•
A copy of the OSS fileset catalog files
•
Description of the problem and accompanying symptoms
•
Details from the message or messages generated
•
Supporting documentation such as Event Management Service (EMS) logs, trace
files, and a processor dump, if applicable
If your local operating procedures require contacting the Global Customer Support
Center (GCSC), supply your system number and the numbers and versions of all
related products as well.
26
filesetname
identifies the affected fileset.
Cause. The indicated fileset is corrupted. This can happen when the fileset was
started with the BUFFERED CREATE or BUFFERED LOG attribute set and its OSS
name server failed.
Effect. The indicated fileset cannot be started.
Recovery. Recover the fileset with the Subsystem Control Facility (SCF) DIAGNOSE
FILESET command using the REPAIR option. Restart the fileset with the SCF START
FILESET command.
27
Cause. A Subsystem Control Facility (SCF) START FILESET command was issued,
but the root fileset is not started yet. No other filesets can be started until the root
fileset is started.
Effect. The command is not processed.
Recovery. Use the SCF START FILESET command to start the root fileset, then
reissue the original START FILESET command.
OSS E00026 Repair is needed for corrupted fileset filesetname
OSS E00027 Root fileset is not started