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

If the REPAIR SERIOUS, REPAIR OPEN, or REPAIR ALL option was specified in the command,
this is an informational message only; no corrective action is needed.
214
MINOR 214 - Catalog/File Label Mismatch, Inode=inode-number
inode-number
indicates the affected inode.
Cause
For the indicated inode, either of the following is true:
1. The disk process’s copy of the number of links to the file is incorrect.
2. The file creation time or creation version serial number (CRVSN) in the fileset catalog does
not match that in the file label of the ZYQ file.
Effect
For Cause 1, FSCK sends a request to the disk process to correct the number. For Cause 2, FSCK
updates the inode with the values from the file label.
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.
215
MINOR 215 - Invalid Timestamp, Inode=inode-number
inode-number
indicates the affected inode.
Cause
One of the time fields (atime, ctime, mtime, or creationtime) in the indicated inode is
invalid.
Effect
The invalid time field is set to the current Coordinated Universal Time (UTC) in the new catalog.
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.
216
MINOR 216 - ZYQ File Conflict - filename
filename
indicates the affected file.
Cause
The inode corresponding to the indicated file does not refer to that file.
Effect
A currently unused inode is allocated, the ZYQ file is renamed to correspond to the new inode,
and the inode is placed in the OSS /lost+found directory.
350 Messages