noft Manual (G06.26+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- 2 noft Utility
- 3 noft Options
- Break Key
- ! (Exclamation Point)
- CD
- COMMENT
- DUMPADDRESS or DA
- DUMPOFFSET or DO
- DUMPPROC or DP
- DYNSTR2
- ENV
- EXIT or E
- FC
- FILE or F
- HELP or ?
- HISTORY or H
- LAYOUT
- LIBLIST
- LISTATTRIBUTE or LA
- LISTCOMPILERS or LC
- LISTOPTIMIZE or LO
- LISTPROC or LP
- LISTSOURCE or LS
- LISTSRLEXPORTS or LLE
- LISTSRLFIXUPS or LLF
- LISTSRLINFO or LLI
- LISTUNREFERENCED or LUR
- LISTUNRESOLVED or LU
- LOG
- OBEY
- OUT
- QUIT or Q
- RESET
- SET
- SHOW
- SYSTEM or VOLUME
- XREFPROC or XP
- 4 noft Diagnostic Messages
- 5 ar Utility
- 6 ar Diagnostic Messages
- A Sample nld and noft Session
- B Converting From Binder to noft
- C Native Object File Structure
- Glossary
- Index

noft Diagnostic Messages
noft Manual—528273-001
4-2
Fatal Errors
Cause. A file input or output error occurred or there is a bad end-of-file.
Recovery. Restart noft and then rebuild the object file.
Cause. An integrity check failed in the function name, probably because of an internal
error.
Recovery. Give the object file being examined and the series of commands that you
used to your service provider for analysis.
Cause. An internal table is corrupt.
Recovery. Restart noft and then the commands in question.
Cause. noft cannot allocate memory, probably because noft has an internal
problem.
Recovery. Give the object file being examined and the series of commands that you
used to your service provider for analysis.
Cause. noft cannot allocate memory, probably because noft has an internal
problem.
Recovery. Give the object file being examined and the series of commands that you
used to your service provider for analysis.
*** FATAL ERROR *** [4]:
Error reading object file: filename.
*** FATAL ERROR *** [6]:
Integrity problem detected in function name.
*** FATAL ERROR *** [7]:
Some problem initializing options.
*** FATAL ERROR *** [8]:
Some sort of problem allocating memory for table-name
*** FATAL ERROR *** [9]:
Some sort of problem reading table-name