TNS/E Native Application Conversion Guide

Introduction to Native Mode

TNS/E Native Application Conversion Guide—529659-003

1-9

Native Object File Tool (enoft Utility)

The native object file tool, enoft, reads and displays information about native object

files. You can use enoft to:

•

Determine the optimization level of procedures

•

Display object code with corresponding source code

•

List object file attributes

•

List unresolved references

enoft runs in the Guardian and OSS environments. The enoft syntax and

capabilities are nearly identical in each environment.

ETK

The Enterprise Toolkit - NonStop Edition (ETK) is an integrated development

environment that enables you to build NonStop applications, on a PC running the

Windows operating system, for execution on a Integrity NonStop server. ETK is an

extension package to Visual Studio.NET and provides a graphical user interface (GUI)

in which you use menus and dialog boxes to select tools and options. ETK was

introduced with the G06.20 RVU and coexists with the Tandem Development Suite

(TDS) in subsequent G-series RVUs. In the H-series RVUs, only ETK is supported.

You must convert TDS projects to ETK projects when converting G-series TNS

programs to H-series native mode as described under ETK Migration Tool.

ETK supports the native C/C++, pTAL, and COBOL cross compilers and related tools.

The cross compilers can compile programs for the Guardian and OSS environments.

TNS compilers and tools are not available on the PC.

ETK Migration Tool

If you are still using TDS on a G-series system, you must convert to ETK when

converting to an TNS/E native mode. A migration tool is available to help you convert

TDS projects to equivalent ETK projects. The tool plugs into TDS. It can be obtained

from IPM Scout at no charge.

The terminology used by TDS and ETK differs somewhat. TDS works with “projects,”

which contain multiple “targets.” ETK works with “solutions”, which contain multiple

“projects.” TDS projects are mapped to ETK solutions, and TDS targets are mapped to

ETK projects.

The migration procedure involves converting TDS targets to ETK projects, then adding

the projects to an ETK solution. The ETK solution could be a newly created solution or

an existing solution.

Note. The TDS-to-ETK migration tool runs as part of TDS; therefore, you must install the tool

and perform the migration on a G-series system with TDS installed. The migration tool does

not require ETK to perform the migration.