nld and noft Manual

noft Diagnostic Messages
nld and noft Manual—520384-003
11-17
Data Errors
Cause. noft found a file that has the specified name, but that file is not a text file.
Recovery. Use ENV on page 5-13 to find the filename. 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 filename from components, the file system
error number occurred.
Recovery. Use SYSTEM or VOLUME on page 5-48 to change to a subvolume with a
shorter name. If this error still occurs, contact your service provider.
Cause. This is an internal error that occurs during construction of a Guardian filename
from components. The length of the pathname plus the length of the filename was too
long for the destination array. Only the filename part will be used.
Recovery. Use CD on page 5-5 to set a shorter pathname.
Cause. You used LISTUNREFERENCED or LUR on page 5-32 while SET
SCOPEPROC was active. These commands are incompatible: if the scope has been set
to a specific procedure, then the procedure must be resolved. Rather than show an
empty list, noft gives this error so that you can reset the scope and reissue the
command.
Recovery. Remove the scoping of the procedure with SET SCOPEPROC * (see SET
on page 5-42).
*** 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.
*** DATA ERROR *** [1065]:
RESET SCOPEPROC before using LISTUNRESOLVED command.