noft Manual (G06.26+)

noft Diagnostic Messages
noft Manual—528273-001
4-17
Data Errors
Cause. The Guardian file system error number occurred when the Guardian function
FILENAME_RESOLVE_ tried to build a directory name from existing pieces as a result
of processing the command SYSTEM or VOLUME on page 3-49.
Recovery. Verify that SYSTEM or VOLUME on page 3-49 specifies a valid node,
volume, and subvolume.
Cause. noft found a file that has the specified name, but that file is not a text file.
Recovery. Use ENV on page 3-14 to find the file name. Check the file content to be
sure it is a text file. If the file does not exist, check the original compilation location and
verify the file.
Cause. During construction of a Guardian file name from components, the file system
error number occurred.
Recovery. Use SYSTEM or VOLUME on page 3-49 to change to a subvolume with a
shorter name. If this error still occurs, contact your service provider.
Cause. This internal error occurs during construction of a Guardian file name from
components. The length of the path name plus the length of the file name was too long
for the destination array. Only the file name part will be used.
Recovery. Use CD on page 3-5 to set a shorter pathname.
*** DATA ERROR *** [1061]:
The Guardian file system error number number occurred while
trying to construct the filename qualifier.
*** DATA ERROR *** [1062]:
Source file is not a text file. Innerlist can not be done
with this file.
*** DATA ERROR *** [1063]:
The Guardian file system error number number occurred while
manipulating file name components.
*** DATA ERROR *** [1064]:
The path length exceeds the container size of number.