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

noft Manual—528273-003
1-1
1 Introduction
The noft utility (or native object code file tool) displays object code files.
The ar utility (or archive tool) creates and maintains archives of object code files.
The noft and ar utilities operate in the TNS/R native mode development environment
on TNS/R native object code files—both PIC (position-independent code) and non-PIC
(non-position-independent code) files.
PIC and non-PIC native object code files are generated by the native C, native C++,
native COBOL, and pTAL compilers. For information on these compilers, see these
manuals:
•
C/C++ Programmer’s Guide
•
COBOL85 for NonStop Systems Manual
•
pTAL Reference Manual
For general information about PIC, see the DLL Programmer’s Guide for TNS/R
Systems.
In the TNS/R native development environment, the functions that noft provides are
similar but not identical to the functions that the Binder product provides in the TNS
development environment. For migration information, see Appendix B, Converting
From Binder to noft.
Native Object Code files
noft and ar operate on native object code files. Native object code files are in
executable and linking format (ELF), a standard format used for object code files, with
HP extensions. For details on the structure of native object code files, see Appendix C,
Native Object Code File Structure.
Native object code files are either linkfiles or loadfiles, but not both.
Native compilers produce only linkfiles. You can use both linkfiles and loadfiles as
noft input.
Native object code files in the Guardian environment have a file code of 700.
Can Be Linked to Produce a Loadfile Can Be Loaded for Execution
Linkfiles Yes No
Loadfiles No Yes