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

Migration Overview
H-Series Application Migration Guide—429855-008
1-3
G-Series-to-H-Series Migration Paths
supported and is enhanced on H-series systems. In addition the NonStop
Development Environment for Eclipse (NSDEE) is available for H-series RVUs.
G-Series-to-H-Series Migration Paths
Both the G-series and the H-series RVUs support TNS execution modes (interpreted
and accelerated) and native execution mode. This results in these possible migration
paths:
•
TNS mode on a G-series system to TNS mode on an H-series system
•
Native mode on a G-series system (TNS/R native mode) to native mode on an
H-series system (TNS/E native mode)
When migrating a G-series TNS program to an H-series system, you can also convert
the program to native mode on the H-series system (TNS/E native mode). See
Converting TNS Programs to TNS/E Native Mode on page 1-4
Additionally, the H-series RVUs support compilation and linking (but not execution) of
TNS/R native programs. You can compile and link TNS/R native programs on an
H-series system, then transfer the object files to a TNS/R server for execution.
Debugging of TNS/R native snapshot files can also be done on an H-series system.
Following are descriptions of the migration paths.
G-Series TNS Mode to H-Series TNS Mode
While native mode offers many benefits, you are not required to convert your G-series
Guardian TNS applications to TNS/E native mode to run them on an H-series system.
You can continue to run TNS object code and gain the performance benefits provided
by HP software that has been converted to TNS/E native mode. Most TNS programs
that run on a G-series system will run on an H-series system with no changes. For
exceptions, see the CAUTION on page 1-3.
CAUTION. If a program does any of the following, additional changes not described in this
guide will likely be required:
•
Executes procedures that are not documented in standard HP NonStop documentation.
(Most procedures are documented in the Guardian Procedure Calls Reference Manual.
That manual also contains a list of other manuals that document available procedures.)
•
Uses documented procedures, but passes parameters or options that are not documented
in the Guardian Procedure Calls Reference Manual.
•
Uses privileged NonStop operating system interfaces.
•
Accesses internal NonStop operating system data structures.
•
Directly accesses the contents of NonStop operating system internal data files (for
example, USERID or CONFIG).
•
Relies on behavior that is not documented in standard HP NonStop documentation.