TNS/R Native Application Migration Guide

Open System Services (OSS) API and Utilities
Migration Tasks
TNS/R Native Application Migration Guide—523745-001
10-3
Specifying Compilation System Components
Specifying Compilation System Components
The TNS and native compilation systems use different components, as described in
Section 1, Introduction to Native Mode. Table 10-1 on page 10-3 describes the
changes required to use the native C compilation system components.
To use the native COBOL85 compilation system components, you must change certain
flags (for example, the TNS COBOL85 compiler runs the Binder utility, but the native
NMCOBOL compiler runs the nld utility). You must also use the nmcobol utility
instead of the cobol utility. For details, see the COBOL85 for NonStop Systems
Manual.
Table 10-1. Changes Required to Use Native C Compilation System (page 1 of 2)
Changed TNS
c89 Utility Flag Reason for Change Action Required
-O Accelerator unnecessary
because native compilers
generate RISC instructions.
Flag now specifies native
compiler optimization level.
Remove flag. Use default native compiler
optimization level of 1 during migration.
-Waxcel Accelerator unnecessary
because native compilers
generate RISC instructions.
Remove flag.
-Wbind nld utility used instead of
Binder for native programs.
Remove flag.
Some -Wbind arguments (such as for
setting object file attributes) have
corresponding native c89 or nld
flags.
Specify corresponding native c89 flags
or pass corresponding arguments to nld
using -nld flag.
See nld(1) and c89(1) reference
pages for details.
-Wccom All compiler pragmas and
arguments must be
specified using c89 flags so
they can be validated.
Remove flag.
Most -Wccom arguments (such as
pragmas) have corresponding native c89
flags. Specify corresponding c89 flags.
See c89(1) reference pages for details.
-Wcfonly cfront function performed
by component of native
compilers.
Replace with -WP flag.