TNS/R Native Application Migration Guide

Introduction to Native Mode
TNS/R Native Application Migration Guide—523745-001
1-8
Native Link Editor (nld Utility)
Native Link Editor (nld Utility)
The native link editor, or nld utility, links one or more native object files (files generated
by the native compilers or nld) to produce either an executable or linkable native
object file. (For more information, see Native Object File Format on page 1-13.) nld
can also modify process attributes, such as HIGHPIN, of executable native object files
and strip nonessential information from native object files.
nld is used instead of Binder for native object files. Binder and nld have a different
syntax and operate on different object file types, but perform essentially the same
operations.
Unlike Binder, nld cannot replace individual procedures and data blocks in an object
file or build an object file from individual procedures and data blocks. nld operates on
procedures and data blocks, but only in terms of an entire object file.
nld does not support the Binder product’s SELECT SEARCH behavior. In most cases,
you can use archive files (files created by the ar utility) to replace this behavior. For
more information on the differences between Binder and nld, see the nld and noft
Manual.
nld runs in the Guardian and OSS environments and on the PC as part of ETK or
TDS. nld syntax and capabilities are nearly identical in each environment.
Native Object File Tool (noft Utility)
The native object file tool, or noft utility, reads and displays information about native
object files. You can use noft to:
•
Determine the optimization level of procedures
•
Display object code with corresponding source code
•
List object file attributes
•
List unresolved references
noft runs in the Guardian and OSS environments. The noft syntax and capabilities
are nearly identical in each environment.