nld and noft Manual

noft Diagnostic Messages
nld and noft Manual—520384-003
11-20
Warnings
Cause. In the Guardian environment, you used the INNERLIST option of
DUMPADDRESS or DA on page 5-6, DUMPOFFSET or DO on page 5-8, or
DUMPPROC or DP on page 5-10.
Recovery. Use LISTPROC or LP on page 5-27 with the DETAIL option to see the
name of the source file. Verify that the source file is the same edit file that was used
when the module was compiled. Verify that the current default subvolume does not
have a file with the same filename.
Cause. The filename in FILE or F on page 5-15 is on a remote node. The data must
be transferred from the remote node to the noft execution node. For large files this
might take a few minutes. After the data has been transferred, there will be no
additional delays for this file.
Recovery. If numerous FILE commands will be done for files on a remote node, it
might be faster to execute noft on the remote node.
Cause. This error can occur only in the Guardian environment.
Recovery. Check the result in the Guardian Procedure Calls Reference Manual
(see SEGMENT_ALLOCATE_). Based on that information, take appropriate action.
Cause. This error can occur only in the Guardian environment.
Recovery. Check the result in the Guardian Procedure Calls Reference Manual
(see SEGMENT_DEALLOCATE_). Based on that information, take appropriate action.
*** WARNING *** [2009]:
Cannot convert line number to Tandem edit line number.
*** WARNING *** [2010]:
Command execution time is increased when object file is on
different node.
*** WARNING *** [2011]:
SEGMENT_ALLOCATE_ had the following result: result
*** WARNING *** [2012]:
SEGMENT_DEALLOCATE_ had the following result: result