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

The TNS/E Native Development Environment

H-Series Application Migration Guide—429855-006

2-18

Setting Up a Cross-Platform Development

Environment on the PC

A typical solution might look like this:

Solution A

Project 1

source file

other items

Project 2

. . .

Using ETK, you can easily set up projects to be deployed on both the TNS/R and

TNS/E platforms. You can define a single solution consisting of multiple projects. The

projects can share source files or they can consist of exactly the same source code.

Each project can have different attributes defined for it (different compiler, different

target platform, and so on). Having both projects in the same solution simplifies

management of the project. For example, you can build all projects in a solution with a

single menu command. Following is an overview of the steps you might follow to create

a project to be executed on both platforms.

1. Start Visual Studio.NET and ETK.

2. Once in ETK, you can create a new project, open an existing project, or bring an

existing program into ETK as a new project. To bring an existing program into ETK,

you first create an empty ETK project, then add the existing source files to the new

project.

3. Define application settings, deployment settings, and project properties. For a new

ETK project, a set of default settings is defined. You can accept the defaults or

change them as desired. For a new project, you are presented with an Application

Wizard, which guides you through a sequence of dialog boxes that allow you to

define the various settings and properties. For an existing project, you use menu

commands to open the dialog boxes.

a. Specify application settings. These include:

•

Target environment (Guardian or OSS)

•

OS version (for example, H06.01)

•

Application type (executable PIC, executable non-PIC, library)

•

Language (COBOL, C, C++, or pTAL)

b. Specify deployment settings. The deployment settings specify information

about the host on which you intend to run the application. This includes the

host name, user name, target location and name (volume, subvolume, file

name of executable file).

c. Specify project properties. These include the target platform type (TNS/R or

TNS/E) and linker to be used to create the loadfile (nld, ld, or eld).

Figure 2-1 shows an example of the Project Properties screen.