TNS/R Native Application Migration Guide

Developing a Migration Strategy
TNS/R Native Application Migration Guide523745-001
2-2
Preparing Programs for Migration
Another issue to consider when migrating is the effort required to migrate the program.
It is not a trivial matter to migrate programs that rely significantly on TNS hardware and
process architecture. For example, a program that explicitly manipulates the P-register
probably requires significant changes to migrate to native mode.
Preparing Programs for Migration
You must complete these tasks before migrating a program to native mode:
Compile programs with a D20 or later TNS compiler version and resolve any
C-series to D-series migration issues.
Run your programs successfully on a system running a D20 or later version of the
operating system and resolve any C-series to D-series migration issues.
Run your program successfully on a RISC-based system and resolve any
hardware variances between TNS and TNS/R systems.
Convert your C or C++ program to use the 32-bit or wide data model, if it does not
do so already. For details, see Converting Code to Use 32-Bit Pointers and
Integers on page 3-6.
This manual assumes that you have completed these tasks. for information on
C-series to D-series migration, see:
Guardian Application Conversion Guide
D-Series System Migration Planning Guide
For information on hardware variances, see the Accelerator Manual.
This manual describes changes required to migrate a program to native mode. It does
not describe changes for other products and subsystems such as NonStop SQL/MP,
NonStop Transaction Services/MP, and HP TCP/IP, which must be made regardless of
whether a program runs in TNS mode or native mode. Depending on the RVU from
which you are migrating your program, additional changes might be required. For more
information, see a product or subsystem’s documentation set and the RVU
documentation.
Planning System Resources
In general, native object files use the same or slightly fewer disk resources than
accelerated object files (object files produced by a TNS compiler and processed by the
Accelerator). Likewise, native processes use comparable processor memory to TNS
processes running in accelerated mode.
The TNS/R native environment is only available on systems running D4x and G-series
versions of the operating system. These systems include the NonStop S-series
servers.