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

25
OSS E00025 Name Server server detected invalid data.
server
is the server name of the affected OSS name server.
Cause
An OSS name server received invalid data from the OSS Monitor. The OSS Monitor might be
malfunctioning.
Effect
The command cannot be processed.
Recovery
Reissue the command. If the problem persists, contact your service provider and provide all
relevant information as follows:
• Saveabend file
• 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
OSS E00026 Repair is needed for corrupted fileset filesetname
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
OSS E00027 Root fileset is not started
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.
28
OSS E00028 Failed in moving catalog files
OSS Monitor Messages 369