TNS/R Native Application Migration Guide

Introduction to Native Mode
TNS/R Native Application Migration Guide—523745-001
1-5
pTAL Compiler
Table 1-1 compares the tools used in the TNS and native development environments:
The following subsections describe the components of the native development
environment.
pTAL Compiler
The Portable Transaction Application Language (pTAL) is a dialect of TAL. pTAL does
not depend on TNS architecture-specific constructs. pTAL introduces new constructs
that replace TNS architecture-specific TAL constructs. The pTAL compiler reads pTAL
source code and creates native object code. The command line syntax of the pTAL
compiler is similar to that of the TAL compiler.
The pTAL compiler syntax-checking mode helps you convert TAL to pTAL. In this
mode, the compiler identifies most source code changes and suggests a method to
recode in pTAL.
The pTAL compiler can be run in the Guardian environment and on the PC as part of
the Enterprise Toolkit—NonStop Edition (ETK) or the Tandem Development Suite
(TDS).
Both ETK and TDS enable you to compile and link programs on a PC (for details, see
the pTAL Reference Manual). You can copy these programs to a NonStop system and
execute them in the Guardian and OSS environments.
Table 1-1. Development Environment Comparison
TNS Development Environment Native Development Environment
TNS C compiler, c Native C compiler, nmc
TNS c89 utility Native c89 utility
cprep and cfront for C++ Native C++ compiler, nmcplus
TNS COBOL85 compiler, COBOL85 Native COBOL85 compiler, NMCOBOL
TNS cobol utility Native nmcobol utility
TAL compiler pTAL compiler
Binder Native Link Editor, nld utility
Native Object File Tool, noft utility
Accelerator Not needed because native compilers produce
optimized RISC object code
Inspect symbolic debugger Inspect symbolic debugger
SQL compiler, SQLCOMP SQL compiler, SQLCOMP
DDL DDL
CROSSREF Not needed because native compilers have
directives or pragmas to support listings and
noft utility products cross-reference listings