noft Manual (G06.26+)

noft Manual—528273-001
1-1
1 Introduction
The noft utility (or native object file tool) displays object files.
The ar utility (or archive tool) creates and maintains archives of object files.
The noft and ar utilities operate in the TNS/R native mode development environment
on TNS/R native object files—both PIC (position-independent code) and non-PIC (non-
position-independent code) files.
PIC and non-PIC native object 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.
Topics:
•
Native Object Files on page 1-1
•
noft on page 1-2
•
ar on page 1-3
Native Object Files
noft and ar operate on native object files. Native object files are in executable and
linking format (ELF), a standard format used for object files, with HP extensions. For
details on the structure of native object files, see Appendix C, Native Object File
Structure.
Native object 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 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