Native Link Editor (NLD) User Program

NLD resolves references to the Shared Run-time Libraries that are specified when building an executable program in native languages.

Native C

Native C++

Native COBOL

Native TAL (PTAL)

The NLD utility links one or more TNS/R object files to produce an executable or non-executable native object file (file code 700). An executable native object file cannot be input to the NLD utility at a later time but a non-executable native object file can.

Link one or more TNS/R native object files to produce a loadfile or linkfile

Modify existing loadfiles

NLD cannot be run interactively. It is run from the native compilers or from a batch obey file containing NLD commands.

Securing NLD

BP-FILE-NLD-01 NLD should be secured "UUNU".

BP-OPSYS-OWNER-02 NLD should be owned by SUPER.SUPER.

BP-OPSYS-FILELOC-02 NLD must reside in $SYSTEM.SYSTEM.

If available, use Safeguard software or a third party object security product to grant access to NLD object files only to users who require access in order to perform their jobs.

BP-SAFE-NLD-01 Add a Safeguard Protection Record to grant appropriate access to the NLD object file.

	Discovery Questions	Look here:
OPSYS-OWNER-02	Who owns the NLD object file?	Fileinfo
FILE-POLICY	Who is allowed to execute NLD on the system?	Policy
FILE-NLD-01 SAFE-NLD-01	Is the NLD object file correctly secured with the Guardian or Safeguard system?	Fileinfo Safecom

Related Topics

Compilers

Securing Applications

Libraries, SRLs & Common Routines

NOFT