noft Manual (G06.27+, H06.03+, J06.03+)

noft Diagnostic Messages
noft Manual—528273-003
4-22
Warnings
2009
Cause. In the Guardian environment, you used one of:
•
INNERLIST option of DUMPADDRESS or DA on page 3-6
•
DUMPOFFSET or DO on page 3-7
•
DUMPPROC or DP on page 3-9
Recovery. Use LISTPROC or LP on page 3-30 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 file name.
2010
Cause. The filename in FILE or F on page 3-17 is on a remote node. The data
must be transferred from the remote node to the noft execution node. For large files,
transfer might take a few minutes, but after the data transfer, will have no further
delays.
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.
2011
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.
2012
Cause. This error can occur only in the Guardian environment.
*** 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