NOFT reads and displays information from native object files. It is the native equivalent of BIND for native code programs written in Native C, Native C++, Native COBOL and PTAL.
NOFT can be run interactively from a TACL prompt in the Guardian environment or an OSS shell prompt or as a batch process issuing commands from a terminal or an obey file.
Determine the optimization level of procedures in a file
Display object code with corresponding source code
List shared run-time library (SRL) references in an object file
List unresolved references in an object file
List object file attributes
RISK NOFT commands are not destructive, but can be used to view native program code.
BP-FILE-NOFT-01 NOFT should be secured "UUNU".
BP-OPSYS-OWNER-02 NOFT should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 NOFT must reside in $SYSTEM.SYSTEM.
If available, use Safeguard software or a third party object security product to grant access to NOFT object files only to users who require access in order to perform their jobs.
BP-SAFE-NOFT-01 Add a Safeguard Protection Record to grant appropriate access to the NOFT object file.
Discovery Questions | Look here: | |
---|---|---|
OPSYS-OWNER-02 | Who owns the NOFT object file? | Fileinfo |
FILE-POLICY | Who is allowed to execute NOFT on the system? | Policy |
FILE-NOFT-01 | Is the NOFT object file correctly secured with the Guardian or Safeguard system? | Fileinfo Safecom |
Related Topics
Compilers
Securing Applications
Libraries, SRLs & Common Routines
NLD