noft Manual (G06.26+)

noft Manual—528273-001
B-1
B
Converting From Binder to noft
The nld and noft utilities listed in Table B-1 on page B-1 replace the Binder product
to support the object files created by the native C, C++, COBOL, and pTAL compilers.
nld and noft are used in the same part of the development process as Binder. You
can perform most, but not all, tasks previously performed by Binder with nld and
noft.
nld and noft have different syntax and semantics than Binder. Unlike Binder, nld is
not an interactive tool. It executes a command based on what you specify on the
command line or in a command file.
Topics:
•
Object File Differences on page B-1
•
Comparing Binder Commands to noft Options on page B-2
For additional information, see:
•
nld Manual
•
TNS/R Native Application Migration Guide
Object File Differences
Because of file format differences between a TNS or accelerated object file and a
native object file, noft does not operate on TNS or accelerated object files.
Unlike TNS and accelerated object files, which can be both linkfiles and loadfiles,
native object files are either linkfiles or loadfiles, but not both. For more information on
native object files, see the nld Manual.
Table B-1. Corresponding Binder Tasks and Native Utilities
Binder Task Native Utility
Build a loadfile from separate object files nld
Build and specify a user library nld
Reduce the size of object files by removing their linking and symbolic
debugging information
nld
Display object file contents noft
Produce load maps and cross-reference listings noft
Modify values in the code and data blocks of an object file Not available.
Search, replace, or reorder code and data blocks in an object file Not available.