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

Cause
The value token followed the keyword SERIAL in the command line but is not a valid FSN value.
Effect
CVT terminates.
Recovery
List the files in the subvolume to see the FSN values used in their Guardian file IDs. Try the
command again with an FSN from those shown in the file IDs. See “Generated Catalog Files”
(page 165) for more information about FSN values.
***Invalid Subvolume Name*** - token
token
identifies the invalid subvolume name.
Cause
The value token followed the keyword IN in the command line, but it is not a valid Guardian
subvolume name.
Effect
CVT terminates.
Recovery
Check the command and correct it as necessary.
***Unexpected Argument*** - token
token
identifies the extra parameter.
Cause
The value token appears in the command line, but what precedes it already constitutes a complete
CVT command.
Effect
CVT terminates.
Recovery
Check the command and correct it as necessary.
FSCK Messages
The FSCK utility runs when you use the SCF DIAGNOSE FILESET or DELETE FILESET command. The
FSCK messages appear in the FSCK log file. The FSCK utility can issue the following kinds of
messages:
• Consistent-fileset messages, which indicate that FSCK found no relevant inconsistencies or
errors in a fileset
• Inconsistency and error messages, which indicate that FSCK found an inconsistency or an
error in a fileset or in fileset-related information
For more information about the inconsistencies that FSCK checks for, see Table 11 (page 162).
FSCK Consistent-Fileset Messages
If the FSCK utility finds no relevant inconsistencies or errors in a fileset, it issues one of the following
messages (listed in alphabetic order). After issuing one of these messages, FSCK clears the mounted
flag and the bitmap indicating the types of inconsistencies previously detected by the OSS name
server.
*** CATALOG AND ZYQ SUBVOLUMES HAVE BEEN PURGED ***
Cause
FSCK successfully deleted a fileset.
FSCK Messages 339