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

noft Manual—528273-003
B-1
B Converting From Binder to noft
The nld and noft utilities listed in Table B-1 replace the Binder product to support the
object code 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.
For additional information, see:
•
nld Manual
•
TNS/R Native Application Migration Guide
Object Code File Differences
Because of file format differences between a TNS or accelerated object code file and a
native object code file, noft does not operate on TNS or accelerated object code files.
Unlike TNS and accelerated object code files, which can be both linkfiles and loadfiles,
native object code files are either linkfiles or loadfiles, but not both. For more
information on native object code files, see the nld Manual.
Table B-1. Corresponding Binder Tasks and Native Utilities
Binder Task Native Utility
Build a loadfile from separate object code files nld
Build and specify a user library nld
Reduce the size of object code files by removing their linking and symbolic
debugging information
nld
Display object code file contents noft
Produce load maps and cross-reference listings noft
Modify values in the code and data blocks of an object code file Not available.
Search, replace, or reorder code and data blocks in an object code file Not available.