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

301
MINOR 301 - Invalid file in ZYQ Subvolume - filename.
filename
indicates the affected file.
Cause
The indicated file exists in a subvolume associated with this catalog, but it is not a valid OSS
file.
Effect
A currently unused inode is allocated, the invalid file is renamed to correspond to this inode,
and the inode is placed in the OSS /lost+found directory.
Recovery
If the REPAIR ALL option was not specified in the Subsystem Control Facility (SCF) DIAGNOSE
FILESET command, the catalog is still in an inconsistent state. Reissue the command with the
REPAIR ALL option.
If the REPAIR ALL option was specified in the command, this is an informational message only;
no corrective action is needed.
302
ERROR 302 - Invalid or Corrupt PXCKSTAT File
Cause
The PXCKSTAT file in the catalog subvolume is not a valid FSCK status file.
Effect
FSCK terminates abnormally.
Recovery
Check that PXINODE and PXLINK files still exist in the subvolume; rename appropriate PXINnnnn
and PXLInnnn files, if needed. Purge the PXCKSTAT file and reissue the command.
If the problem persists, set the SAVEABEND attribute of the FSCK program file using either the
Guardian Binder program (on a D40.00 system) or the nld command (on a D42.00 or
subsequent D4x-series system). Rerun FSCK to produce a saveabend file. Contact your service
provider and provide all relevant information as follows:
• Saveabend file
• 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.
303
ERROR 303 - Catalog Inconsistent
Cause
The catalog subvolume is missing a PXINODE or PXLINK file and the PXINnnnn, PXLInnnn, or
PXLOnnnn creation timestamps do not match those stored in the PXCKSTAT file.
Effect
The FSCK utility terminates abnormally.
FSCK Messages 353