H-Series Application Migration Guide (H06.03+)

H-Series Application Migration Guide—429855-006
1-1
1 Migration Overview
This section introduces the H-series development and execution environments, and
provides a summary of the tasks required to migrate an application from the G-series
environment to the H-series environment. Topics are:
•
Introduction to the H-Series Application Environment
•
G-Series-to-H-Series Migration Paths on page 1-3
•
H-Series Development Environments Overview on page 1-4
•
Summary of Migration Tasks on page 1-6
Introduction to the H-Series Application
Environment
In most respects, the H-series application environment is similar to the G-series
application environment.
What is Not Changing
The similarities between the G-series and H-series application environments ease the
transition to the new platform and facilitate the migration of applications to the new
environment. Similarities include:
•
Binary compatibility for TNS programs. Interpreted and accelerated execution
modes are supported.
•
Full support for TNS development tools in the Guardian environment. You can
continue to develop TNS applications in the Guardian environment on an H-series
system using familiar tools. (TNS tools are not supported in the OSS environment
on H-series systems.)
•
A native development environment that is similar to the TNS/R native development
environment. The C, C++, COBOL, and pTAL languages are supported.
°
TNS/E native development tools have all the same functionality as the TNS/R
native development tools. In some cases, the TNS/E tools have added
functionality.
°
In most cases, the same changes are required to migrate TNS applications to
TNS/E native mode as to migrate them to TNS/R native mode.
°
In most cases, no source code changes are required to migrate TNS/R native
mode programs to TNS/E native mode.
•
Debugging of snapshot files. You can debug TNS, TNS/R, and TNS/E snapshot
files.
•
Full support for native-mode cross-compilation on the PC.