NonStop Development Environment for Eclipse 4.0 User Guide HP Part Number: 732674-001 Published: October 2013 Edition: NSDEE 4.0 and later versions, J06.10 and subsequent J-series RVUs, H06.
© Copyright 2012, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Warranties The information contained herein is subject to change without notice.
Contents 1 Introduction.............................................................................................11 New and changed features for NSDEE 4.0................................................................................11 Related documentation............................................................................................................11 2 Before you begin......................................................................................13 3 Getting started...............
DependencyHandling.........................................................................................................49 TARGET_SYSTYPE..............................................................................................................49 NSDEE_DEPLOY_SYSTEM, NSDEE_DEPLOY_USER, NSDEE_DEPLOY_DEST, NSDEE_DEPLOY_FILENAME................................................................................................49 SQL/MX_COBOL_PREPROCESSOR_LOC...................................................
Disabling specific code analysis errors and warnings...........................................................100 Disabling erroneous syntax warnings..................................................................................101 Specifying locations for C/C++ headers, COBOL COPY libraries, and pTAL source files................103 Instructing NSDEE not to build source files...............................................................................104 Excluding a single COPY library................
New File from Template....................................................................................................138 New Folder.....................................................................................................................138 New C/C++ Class Wizard...............................................................................................138 New Header File.............................................................................................................
NonStop Tools menu........................................................................................................152 Context menu for NonStop Project Explorer.........................................................................152 Icons...................................................................................................................................152 7 Support and other resources....................................................................
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 Remote Makefile Project wizard.........................................................................................32 Build Settings wizard dialog..............................................................................................33 Properties for MakeCar project..................................................................................
52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 Create New Configuration dialog......................................................................................95 Symbols tab of the Path and Symbols property page...........................................................100 Disabling record field errors............................................................................................
11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Remote Settings page settings (SQL/MX) ..........................................................................135 Remote Settings page settings (SQL/MP) ..........................................................................135 Import Existing Code wizard settings................................................................................136 Remote Makefile page settings....................................................................
1 Introduction The NonStop Development Environment for Eclipse (NSDEE) is a set of Eclipse plug-ins that extend Eclipse's C/C++ Development Tooling (CDT) to provide an integrated development environment (IDE) for developing NonStop applications on Windows. NSDEE supports building applications and editing source files both locally (on Windows) and remotely (on NonStop).
• SQL/MX Programming Manual for C and COBOL • Inspect Manual for information on debugging TNS/R applications • Native Inspect Manual for information on debugging TNS/E applications • TACL Reference Manual for information on NonStop variables, commands, and built-in functions • ODBC/MX Client Driver manuals for information on ODBC driver error messages All these manuals are available in the NonStop Technical Library (NTL) at: www.hp.
2 Before you begin NSDEE provides capabilities for building applications on both local Windows and remote NonStop systems. Local Windows-hosted builds require a make program (as provided by Cygwin or Msys) and cross compilers for building NonStop applications on Windows. Remote NonStop-hosted builds typically require make (OSS) or gmake (Guardian) and native compilers for NonStop systems. To use NSDEE for either local or remote builds, you must install both Eclipse Juno 4.
3 Getting started This chapter provides an introduction to how to use NSDEE, from creating and building projects to enabling C/C++ features based on indexing. Preparing the Workbench The scenarios described in this chapter assume that you: • Are familiar with basic Workbench features, such as views and perspectives. • Are familiar with Workbench terminology, such as context menu, which refers to the pop-up menu that appears when you right-click in a view.
a. b. c. d. Select Add... to open the Add Cross Compiler Location dialog. Verify the Location: where the cross compilers are installed. Ensure that the Auto-detect root folders radio button is selected. Select OK. If the cross compilers are installed at non-standard locations, see “Configuring Tool Locations” (page 66) for information on how to add those locations to your Tool Location preferences. 3. Select the SQL/MX Preprocessors tab to show all SQL/MX preprocessors on your system, if any.
6. Select the Connect button to verify the connection. NOTE: 7. A password prompt appears before the connection completes. Select OK to save the connection configuration and close the Preferences dialog. NOTE: NSDEE provides the Connect button to test new connection configurations. However, the Configure Connections dialog and the Connect button are not necessary to establish connections because NSDEE automatically establishes connections as needed. 8.
a. b. c. d. 3. Enter a name for your project in the Project name: field. Optionally, deselect the Use default location checkbox and enter a location to store your project. By default, if a location is not specified NSDEE stores your project in a top-level directory in your workspace directory. Select Hello World ANSI C Project in the NonStop Executable folder. This creates an initial source file that declares main() and prints a text string. Under Toolchains:, select C-C++ TNS-E Tools.
On the Basic Settings dialog: • Configure author and copyright information to be placed in the comment header of the source file. • Configure the text string used in the print statement of the source file. • Set the name of the initial source directory. These fields can also remain unchanged. 4. 5. 18 Select Next > to open the Initial Build Settings dialog.
Leave the default settings unchanged except for the Cygwin/Msys bin: combo box. Set it to the bin directory for either Cygwin or Msys. If the combo box pull-down contains no entries, refer to “Specifying tool locations” (page 14). If you select the Configure Locations... link to the right of the combo box, the Cygwin/Msys tab of the Tool Location preferences dialog opens. NOTE: The Cygwin/Msys bin: combo box is provided for your convenience.
6. Select Next >. The resulting Remote Settings dialog opens. Specify a transfer location on a NonStop server for final build objects. If you chose SQL/MP or SQL/MX on the previous page, specify NonStop server locations for SQL compiles. If you added a connection configuration (see “Configuring connections to NonStop systems” (page 15)), you can choose that system from the Target system/user (-h/-u): combo box drop down and provide a target destination and file name.
The Advanced settings... button opens project properties for the project you are about to create. Change tool options, environment variables, and other project settings in Project properties. These settings are available after you create a project by selecting your project in the NonStop Project Explorer view and then selecting Properties from the context menu. Leave this page unchanged. 8. Select Finish. NSDEE creates your project.
If the existing source base consists of ETK projects, consider using the Import ETK Projects wizard. The Import ETK Projects wizard imports not only your sources, but also many tool settings such as compiler and linker options. For details, see “Importing ETK projects” (page 73). This section provides examples of how to create managed projects from existing sources for two scenarios: • Creating a project and using the sources outside your workspace using a sample program Car.
4. In the Initial Build Settings dialog, do not change the defaults. Specify either a Cygwin or Msys bin using the Cygwin/Msys bin: combo box if you want NSDEE to prepend the corresponding bin to PATH before builds. The following dialog shows the Msys bin specified. 5. 6. Select Next >. The resulting Remote Settings dialog opens. To deploy Car to a NonStop system, enter a remote system and user, and specify a remote location. Select Finish.
3. Select OK in the C Element Filters dialog. To hide .project and .cproject, return to the C Element Filters dialog. The .project and .cproject files define attributes of the Car project, including any customizations. If you save your projects in a Source Configuration Management system, you must save these files in addition to your source code.
3. 4. Select Next >. In the Initial Build Settings dialog, do not change the defaults. Specify either a Cygwin or Msys bin using the Cygwin/Msys bin: combo box if you want NSDEE to prepend the corresponding bin to PATH before builds. The following dialog shows the Msys bin specified. 5. 6. Select Next >. The resulting Remote Settings dialog opens. To deploy GeneralCpp to a NonStop system, enter a remote system and user, and specify a remote location. Select Finish.
3. 4. 5. In the Import wizard, expand the general folder and select File System. Select Next > to continue to the File system wizard. Enter in the File system wizard From directory: field: C:\Examples\GeneralCppSources 6. 7. 8. A folder for GeneralCppSources will appear in the left-hand list box. Expand the folder but do not select its check box. Under GeneralCppSources, select the check boxes for the include and source directories. Select Finish.
a. b. c. d. 3. 4. 5. 6. Enter Car in the Project name: field. Deselect the Use default location check box and enter: C:\Examples\ MultiProjectCarApp\Car Select Empty Project in the NonStop Executable folder. Under Toolchains:, select C-C++ TNS-E Tools. Select Next > to open the Initial Build Settings dialog. In the Initial Build Settings dialog, do not change the defaults. To prepend the corresponding bin to PATH before builds, specify either a Cygwin or Msys bin using the Cygwin/Msys bin: combo box.
4. In the Tool Settings tab of the Settings page, under C++ Compiler (TNS/E), select the Includes category to open the Includes page. 5. 6. In the Includes page, select the Add button to the right of Include paths (-I). In the Add directory path dialog, enter in the Directory: field: ../../CarParts/src 7. 8. Select OK to dismiss the Add directory path dialog and apply the change. Select the Miscellaneous category under C++ Linker (TNS/E). 9. To the right of Other objects, select the Add button 10.
11. Select OK to dismiss the Add file path dialog and apply the change. 12. Make a similar change to the Release build configuration. In the Configuration: combo box at the top of the page, change the configuration to Release. 13. In the Miscellaneous page for the C++ Linker (TNS/E), select the Add button Other objects. 14. In the Add file path dialog, enter in the File: field: to the right of ../. ./CarParts/Release/CarParts.tlo 15. Select OK to dismiss the Add file path dialog and apply the change. 16.
TIP: The Console view separates build output for each project. Because the Car project built last, its build output is shown in the Console view. If you select CarParts in the NonStop Project Explorer view, the Console shows build output for CarParts. TIP: Building Car and CarParts produces more output than the default Console view can display. By default, the Console view limits output shown to 500 lines. Increase this from the preference page available from Window→Preferences→C/C++→Build→Console.
You must create your own directory, sources, and makefile. Creating a local makefile project from existing sources This section provides an example of creating a makefile project from existing sample sources for a simple application named Car. To get the sources for Car, unzip the file: eclipse install directory\plugins\com.hp.nsdee_4.0.n\Examples.zip The following example assumes Examples.zip is unzipped to C:\Examples.
Creating a remote makefile project Remote makefile projects are hosted on a NonStop system where the source files and makefiles reside. Creating a remote makefile project allows you to edit remote source files and launch builds from NSDEE. Remote makefile projects are created either from scratch or with the project to build existing source using existing makefiles. To create a remote project, from the NonStop Development perspective: 1.
Figure 2 Build Settings wizard dialog 9. The Build Settings dialog enables the setting of an alternative command to gmake (Guardian) or make (OSS) to drive builds and alternative names for the build targets all and clean. Change these settings only if needed. 10. Select the Create makefile check box if you want NSDEE to create an initial makefile. 11. The Default editor: combo box is shown only for Guardian projects. Use it to select the default editor to use for source files in your project.
Adding folders and files to projects NSDEE provides a number of wizards for adding folders and files to a project. All of these wizards are available from the New sub-menu of the NonStop Project Explorer view context menu. Table 1 (page 34) summarizes the wizards available and their capabilities.
Figure 3 Properties for MakeCar project Not all project properties are specific to building your project. Properties specific to builds typically have the Configuration: combo box shown in Figure 3 (page 35), which allows you to choose the configuration to view or modify. The entries under C/C++ Build allow you to configure different aspects of your builds. Table 2 (page 35) lists a brief summary of what you can configure using each entry under the C/C++ build node.
3. 4. 5. 6. 7. In the Properties dialog, expand C/C++ Build and select Settings. In the Settings page, select the Tool Settings tab (if the Tool Settings page is not already displayed). In the Tool Settings page, select the Includes category under C++ Compiler (TNS/E) to display Include path (-I) settings (which should be empty). At the top of the Include path (-I) settings, select the Add... icon path dialog. In the Add directory path dialog, enter one of the following: to open the Add directory ..
Building a project To build a project, perform the following steps from the NonStop Development perspective: 1. In the NonStop Project Explorer, select the project you want to build. 2. Check which build configuration (typically Release or Debug) is active. From the context menu of the NonStop Project Explorer, select Build Configurations→Set Active. The Set Active sub-menu displays a list of build configurations, with a check mark next to the active build configuration.
TIP: Hover your mouse over the deploy icon on the tool bar to see which project will deploy. For example, if you selected project Hello World and the active build configuration for that project is Debug, then the tool tip reads: "Deploy 'Debug' for project 'Hello World'". TIP: The pull-down menu next to the deploy icon changes the current build configuration and initiate a deploy in a single step. This action also initiates a build, if needed, before attempting to transfer a project final build object.
4 Concepts This chapter supplements the "Concepts" chapter of the C/C++ Development User Guide, providing details specific to NonStop development. NSDEE overview NSDEE extends Eclipse's C/C++ Development Tooling (CDT) to enable its use for developing NonStop applications, including applications built with C, C++, COBOL, pTAL, SQL/MP, and SQL/MX.
Selecting a local project type from File→New menu opens a new project wizard. The following types of projects are available: • NonStop Executable — A project that manages builds of an executable file. • NonStop Dynamic Link Library — A project that manages builds of a library that can be dynamically loaded at run time. • NonStop Linkfile — A project that manages builds of a linkfile, which is a collection of object files that can be linked into another project build.
Figure 4 NonStop Development perspective Views The views shown in Figure 4 (page 41) are: • The NonStop Project Explorer view, which provides access to your NonStop projects and their associated properties and files. Also use the NonStop Project Explorer view to select projects to build and to select build configurations to use in builds. For details, see “NonStop Project Explorer view” (page 128).
Preferences Preferences allow you to change the default behavior of Eclipse. Change preference settings using the Preferences dialog Window→Preferences. Many preference settings in Eclipse apply to NSDEE, particularly those under the General and C/C++ categories in the Preferences dialog. Preferences specific to the NonStop Development perspective are available under the NonStop Development category. For more information about NonStop Development preferences, see “NonStop Development” (page 143).
Icon Description Invokes make deploy for a local project where the deploy makefile target transfers a just built executable to a NonStop server. The pull-down menu for this action lets you choose which build configuration to deploy. Debugs configurations. Runs configurations. Runs the last configuration. Opens the File Search dialog. Building NonStop projects Eclipse defines two build actions that you can invoke from several places in the IDE — Build Project and Clean actions.
Building with make on Windows To build with make on Windows, either Cygwin or Msys must be installed. Both are available on the NSDEE installation media. The path to the bin directory containing the make program must be part of your PATH environment variable. A Cygwin or Msys bin directory can be added to PATH either outside of NSDEE (for example, by adding bin to your Windows PATH) or by NSDEE prepending a bin path to PATH when builds are launched.
user, then the origin is set to USER: CONFIG. If the user deletes a USER: CONFIG variable which was updated over a BUILD SYSTEM variable such as COMP_ROOT, then that variable is reset as a BUILD SYSTEM variable with the original definition. If the user deletes a variable which was not a BUILD SYSTEM variable (but one created by the user) such as PROJECT_LIB, then the variable is just deleted from the list of environment variables.
Table 3 Build variables and environment variables (continued) Variable Name Type Local Projects Type (Remote) property page. You can use these variables to create custom deploy targets. NSDEE_DEPLOY_FILENAME SQLMX_COBOL_PREPROCESSOR Purpose environment Managed Used as argument to -Wcobol="CONSULT..." for projects using SQL/MX. NOTE: Many more build variables are set up by Eclipse and CDT available to use in makefiles and in the Tool Settings tab of the Settings property page.
used to set COMP_ROOT. For TNS/E, NSDEE_SYS_INCLUDE_PATH is set to COMP_ROOT\user\include, for TNS/R, it is set to COMP_ROOT\include. The value of NSDEE_SYS_INCLUDE_PATH shows up under an Includes list which looks similar to a top-level folder under a project as shown in Example 1 “Project Includes folder”. Example 1 Project Includes folder NOTE: The indexer uses the NSDEE_SYS_INCLUDE_PATH associated with the first build configuration set for a project.
behavior in the new project wizard or in the Tool Locations property page by either leaving the Cygwin/Msys location combo empty (to disable this behavior) or by setting it to either a Cygwin or Msys bin directory. Deploy.jar and NSDEE_POSIX_BIN Deploy.jar is a program that transfers files from Windows to NonStop. It is typically invoked by a deploy makefile target. Deploy.jar uses NSDEE_POSIX_BIN to workaround a limitation of launching a Java application with the Msys bin directory first in PATH.
HOST_PASS — used if none of the above are set. HOST_PASS is the environment variable you set if all tools use the same host and user settings (for simplicity). If you fail to set one of the above environment variables when invoking make outside of NSDEE, the command using nsdee-auth as an argument to, -Wsqluser (for example) fails and the output includes a message such as the following from nsdee-auth: C:\e3.7\eclipse\plugins\com.hp.nsdee_1.0.0\Tools\nsdee-auth.
Figure 6 Settings for projects with SQL/MP compilation, SQL/MX compilation, and no SQL compilation SQL/MX_COBOL_PREPROCESSOR_LOC For COBOL projects with SQL/MX, NSDEE sets the environment variable SQLMX_COBOL_PREPROCESSOR_LOC to the location of the SQL/MX preprocessor for COBOL as specified in the Tool Locations project property page. SQLMX_COBOL_PREPROCESSOR_LOC is used in the -Wcobol="CONSULT..." argument in the Miscellaneous page of the COBOL Compiler tool to pass the location of esqlcli.
Figure 7 Setting the location of SQL/MX Preprocessor for COBOL Multi-user environments When a project is developed in a shared environment where the project sources reside on each user’s private Windows system, each user must customize the project settings to their individual system environment.
This table lists the three automatically-generated makefiles that are written to the top-level build directory: Makefile Purpose makefile The primary makefile for a build configuration. It contains the build rules for "all", "clean", and "deploy". objects.mk Contains definitions of USER_OBJS and LIBS, two build macros that are set to out-of-project object files and libraries, respectively, that are passed to the linker for the final link step. sources.
Example 3 Sample build rule for Door.o in subdir.mk src/Door.o: ../src/Door.cpp @echo 'Building file: $<' @echo 'Invoking: C++ Compiler (TNS/E)' c89 -Wcplusplus -g -Woptimize=1 -Ww -Wsystype=oss -c -Wversion3 -o "$@" "$<" && c89 -Wcplusplus -g -Woptimize=1 -Ww -Wsystype=oss -c \ -Wversion3 -WM "$<" | grep -v -e '$(NSDEE_SYS_INCLUDE_PATH_ESC)' -e \ 'Door.cpp' | sed -e 's/[ ].*CarParts\\Debug\\\.\.\// ..\//g' >src/Door.
In Example 3 “Sample build rule for Door.o in subdir.mk”, the remaining output from sed is written to Debug/src/Door.d, the same directory Door.o is written to, and the dependency file path is written to Debug/src/subdir.mk in the form: CPP_DEPS += \ ./src/Door.
testmx.ec: "testmx.mxh" "testmx2.mxh" Because the SQL/MX preprocessor does not specify the locations of header files, NSDEE performs a final pass over the dependency file, adding paths to the dependencies through -I directives specified in the invocation of the compiler. Example 4 “Sample build rule for testmx.c ” shows an example of the contents of a subdir.mk file with a rule for building testmx.c using the source testmx.ec which has dependencies on SQL/MX header files in mxprog/mxheaders.
Tool chains A tool chain is a group of tools used to build an application for a particular target architecture. The term “tool chain” more specifically refers to a list of tools defined for a managed project and the options that are passed to those tools when they are invoked during builds. To view the tool chains associated with a project, open the Settings property page. A project can have two tool chains at most, one for TNS/R and one for TNS/E.
Figure 9 Miscellaneous option category for the C Linker All tools include a Miscellaneous options page to specify most tool options. Explicitly defined tool options, such as the Verbose check box in Figure 9 (page 57), are for common options and are provided for your convenience. Alternately, enter -Weld=-verbose directly in the additional options box. Option categories are required for the following entities: • Object files from other projects.
NOTE: If you select the Destination option group of the Deploy Tool, all fields are disabled,although they may contain values. This is due to a limitation in CDT's interface for specifying options. NSDEE works around this limitation by providing the Settings (Remote) property page, to change settings in the Destination options group. Tools for a simple C project with SQL/MP For projects that use SQL/MP, NSDEE provides a deploy tool and compiler tool definitions which include SQL/MP settings.
Figure 11 Tools with SQL/MP settings NOTE: All options settings related to remote NonStop systems and locations are disabled on options pages due to a CDT limitation. To change values for such settings, go to the Settings (Remote) property pages. TIP: Turn off SQL preprocessing options for any source file or any source directory by selecting the source file or directory and opening the Settings page. To turn off SQL preprocessing options, deselect the Build with SQL/MP preprocessor check box.
Figure 12 Creating a project with SQL/MX support Figure 13 (page 60) shows the tool chain for a simple C project with SQL/MX. Figure 13 Tool chain for simple C project with SQL/MX NOTE: All option settings related to remote NonStop systems and locations are disabled on options pages due to a CDT limitation. To change values for such settings, go to the Settings (Remote) property pages. The C/C++ SQL/MX Preprocessor tool invokes the C compiler with options for preprocessing SQL/MX statements in .ec or .
build configuration. Figure 14 (page 61) shows where the sqlmx.c file is written for a Debug build of sqlmx.ec. Figure 14 Location of SQL/MX preprocessor output The C/C++ SQL/MX Compile tool invokes the C compiler with options for performing an SQL/MX compile. The deploy target for the main makefile or SQL/MX builds results in both an SQL/MX compile and an invocation of Deploy.jar.
Customizing managed builds Although managed builds generate makefiles, you can still customize managed builds. NSDEE provides two separate mechanisms for customizing managed builds. The first mechanism involves writing your own version of top-level makefile targets. The second mechanism involves using project properties to add commands to be invoked before and after Build Project and Deploy Project actions.
Figure 15 Adding pre-build and post-build steps Example 7 “Build Output with pre-build and post-build steps” shows the pre-build and post-build targets added to the main makefile on the next build as a result of setting the project properties. This example also shows how the "all" target depends on "pre-build", and the rule for the final executable (Car.txe in this case) invokes the post-build step with $(MAKE) --no-print-directory post-build.
Example 7 Build Output with pre-build and post-build steps # All Target all: pre-build main-build # Main-build Target main-build: Car.txe # Tool invocations Car.txe: $(OBJS) $(USER_OBJS) @echo 'Building target: $@' @echo 'Invoking: C++ Linker (TNS/E)' c89 -Wcplusplus -Wsystype=guardian -Wcall_shared -o "Car.txe" $(OBJS) $(USER_OBJS) $(LIBS) @echo 'Finished building target: $@' @echo ' ' $(MAKE) --no-print-directory post-build . . . pre-build: -@echo 'Pre-build action' -echo "Build is starting...
@echo 'Finished building: $@' @echo ' ' $(MAKE) --no-print-directory my-post-deploy NSDEE does not create these targets. You must create these targets in a makefile.targets file as a top-level file in the project. The main makefile includes the deploy targets defined with this method. Example 9 “Sample definitions of my-pre-deploy and my-post-deploy” shows sample definitions that print some text, but can be defined in more useful ways.
5 Tasks This chapter provides step-by-step procedures for many common tasks in NSDEE. Configuring Tool Locations NSDEE project properties and new project wizards present a list of available tools. Figure 16 (page 66) shows an example of these settings as seen in the Tool Locations property page for a managed project that builds an SQL/MX application. Configure the values available on property pages and in new project wizards using the Tool Locations preference page.
Figure 17 Add Cross Compiler Location dialog 3. The Location: field contains the location where all NonStop cross compilers are typically installed and the Auto-detect button is selected. Select OK. 4. Back on the Tool Locations preference page, select OK. The locations of any newly installed compilers are added to the list.
1. 2. 3. 4. Select Configure Tool Locations... from the NonStop Tools menu. On the Tool Locations preference page, select the Cygwin/Msys tab. On the Cygwin/Msys page, enter the Cygwin bin directory path in the Cygwin bin: field or the Msys bin directory path in the Msys bin: field. Alternatively, select Browse... to open a directory browser to find the location. Select OK.
Figure 20 Network Connections preferences page 2. 3. On the preference page, select Add/Remove... In the Add or Remove Connection Configurations dialog, enter an IP address or a system name in the System: field and click the Add button. TIP: If one or more remote connections are already configured and you want to reuse the settings from an existing configuration, select it in the list of connection configurations, then select Copy, and then OK.
4. To dismiss the Add or Remove Connection Configurations dialog, select OK. The system or IP address you entered appears in the System: combo box. TIP: If this is the first configured connection, enter the system name in the System: combo. However, you must select Add/Remove... to add additional systems. 5. 6. 7. Enter a user name or alias in the User name: field. Select the preferred protocol.
5. 6. After making changes, select OK to return to the Preference dialog. Select OK to apply your changes and dismiss the Preferences dialog. For more information on SSH and SFTP, see the NonStop SSH Reference Manual. Changing Telnet and FTP settings To change Telnet and FTP settings, from the NonStop Development perspective: 1. To open the Network Connections preference page (Figure 20 (page 69)) select NonStop Tools→Configure Connections.... 2.
Table 4 Telnet/FTP settings (continued) 5. 6. Setting Description Service or window name: button Enter the service name (such as TACL or OSH) or a static window (such as #WIN05) to choose when logging in. Enter Choice> prompt: combo box Choose On if Telserv is configured to show the Enter Choice> prompt during login. Authentication: combo box Choose On if Telserv is configured to prompt for user name and password during login.
Figure 24 Export Connection Configurations dialog 3. 4. 5. In the Export to: field, enter the file path to write exported configurations. Or leave the default setting, the connections file in your home directory. Optional: Select Overwrite existing file without asking if you are not crned about overwriting an existing file. Select Finish. Importing connection configurations To import connection configurations exported from another workspace, from the NonStop Development perspective: 1.
Figure 26 ETK import wizard Eclipse and NSDEE projects have more constrained structures than ETK projects. NSDEE projects are typically confined to the directory structure under the top-level directory of the project. Build output is typically written to a subdirectory of the project and external project files are referenced in compiler and linker options and are not directly part of the project. ETK project structures are less constrained and can vary greatly among solutions.
For insolvable problems with imported ETK projects, HP encourages you to contact your HP Support representative. Importing one or more ETK projects To import one or more ETK projects associated with a solution, from the NonStop Development perspective: 1. Select Import ETK Projects... from the NonStop Tools menu. 2. In the Import ETK Projects wizard, enter the path of the solution file associated with the ETK projects. Or select Browse... to browse for the solution file.
NOTE: NSDEE 2.x local projects cannot share the same workspace with an NSDEE 4.0 project with the same name. To import an NSDEE 2.x project as an NSDEE 4.0 project, you must import the NSDEE 2.x project into another workspace. NOTE: NSDEE 2.0 remote projects cannot be directly imported into NSDEE 4.0. They must be imported into NSDEE 2.1 first, then imported into NSDEE 4.0. NOTE: You can import NSDEE 2.1 remote projects into an NSDEE 4.0 workspace using the normal import mechanism.
5. 6. Select Add project to working sets if desired. For information on working sets, see the Eclipse Workbench Guide. Select Finish to import all selected NSDEE 2.x projects as NSDEE 4.0 projects. If the import completes without errors or warnings, the following dialog appears. Dismiss the dialog by selecting OK). If the import completes with errors or warnings, a dialog similar to Figure 30 (page 77) appears. To open the log and view the contents, select the link.
Creating Windows-hosted projects with managed builds To create a Windows-hosted project with managed builds using cross compilers and tools, from the NonStop Development perspective: 1. Select one of the following menu items from the New submenu of the File menu: • C Project • C++ Project • COBOL Project • pTAL Project A new project wizard opens, such as the NonStop COBOL Project wizard Figure 31 (page 78), that is specific to the chosen menu item. Figure 31 NonStop COBOL Project wizard 2. 3. 4.
5. 6. • NonStop User Library — A project that builds a NonStop user library (TNS/R only). • NonStop Makefile Project — An application using a makefile provided by you. Select either one or both tool chains in the Toolchains list, depending on whether you want to build for TNS/R, TNS/E, or both. Select Next > to continue to the Initial Build Settings page of the wizard: Figure 32 Initial Build Settings page (COBOL executable project) 7.
12. In the Additional languages: row, choose any additional languages you intend to use in the project. This results in the addition of cross compilers to the project tool chain. You can add tools after project creation using the Tool Chain Editor property page. 13. In the SQL tools: row, select SQL/MX or SQL/MP if the project source contains SQL statements. This results in the addition of SQL-specific tools being to the project tool chain. 14.
Figure 33 Select Configurations page (managed build project) 17. Select Finish to dismiss the wizard and create your project. Creating Windows-hosted makefile projects To create a Windows-hosted project for which you will supply the makefile, perform the following steps from the NonStop Development perspective: 1.
Figure 34 Initial Build Settings page (makefile project) 7. Depending on your tool chain selections, a TNS/E tools root: row, a TNS/R tools root: row, or both are displayed. Select the root directories of the RVUs to build your project for TNS/E and TNS/R. If a tools root combo box is empty, select the Configure locations... link to establish cross compiler and tools system locations. These settings are used to determine where the C/C++ indexer looks for system headers and, optionally, to set COMP_ROOT.
Figure 35 Select Configurations page (makefile project) 11. Select Finish to dismiss the wizard and create your project. Creating Windows-hosted projects from existing source To create a project using an existing source base, perform the steps in one of the following procedures: • “Creating Windows-hosted projects with managed builds” (page 78) • “Creating Windows-hosted makefile projects” (page 81) with a slight change to change to step 3.
Figure 36 Import Existing Code wizard 2. 3. 4. 5. 6. 7. Enter a project name in the Project Name group box. Enter the location of your source base in the Existing Code Location group box, or select Browse... to browse for the location. In the Tools root: row, select the root directory of the RVU to build your project. If the tools root combo box is empty, select the Configure locations... link to establish the cross compiler and tools system location.
Figure 37 Remote Makefile Project wizard 2. 3. 4. 5. 6. 7. 8. Enter a project name in the Project name: field. Select the remote NonStop project host system using the Build system: combo box. To add systems to the combo box, select Edit... to open Network Connection preferences. In the Platform: row, select OSS to use OSS tools, or Guardian to use Guardian tools. Enter the project file system location in the Project location: field, or select Browse... to browse for the location.
Figure 38 Build Settings page 9. Optional: Set a non-default build command and non-default Build and Clean makefile target names. 10. If a makefile does not exist under the remote project location, select the Create makefile check box to have NSDEE create an empty makefile for you. 11. If you selected the Guardian platform in step 4, select the default editor to open Guardian source files in the Default editor: combo box. This generates extensions for source files in remote projects.
Figure 39 Run Configurations dialog After a run configuration is created and saved, it can be used to run applications without changing information in the run configuration. The following sections describe: • “Creating a run configuration” (page 87) • “Launching an application using a saved run configuration” (page 90) Creating a run configuration To create a run configuration, perform the following steps from the NonStop Development perspective: 1. Select Run Configurations...
d. e. Enter a path to the executable you want to run in the NonStop executable's path on NonStop system: field (or select Browse... to browse for executables on the remote system). Optional: If the program you want to run is on your local Windows system and you want to transfer it to the NonStop system prior to launching it, select the check box for Local executable to be transferred to NonStop path specified above:, then enter the local path of the executable (or select Browse...
Figure 41 Environment page for OSS launches Figure 42 Environment page for Guardian launches b. Select the top radio button to enter environment variables settings (OSS) or DEFINEs, ASSIGNs, and PARAMs settings (Guardian) directly in the text box below it. For OSS, these settings will be issued directly in the shell.
NOTE: Standard Input and Output options and the Launch in background option are ignored for NSDEE projects. Those options are specific to applications run locally on Windows. 8. To save your new run configuration, you can select Run, which will both save the run configuration and launch your application. Alternatively, you can select Apply and then Close to save your run configuration but postpone launching your application.
1. 2. 3. In the NonStop Projects Explorer view, select a project that you want to change TARGET_SYSTYPE for. Select Properties from the context menu of the NonStop Projects Explorer view. Select the Build Variables entry under C/C++ Build (see Figure 45 (page 91)). Figure 45 Build Variables property page 4. Select the Show system variables check box, then select TARGET_SYSTYPE (see Figure 45 (page 91)). 5.
Figure 47 (page 92) shows the Tool Settings page for a C project with SQL/MX and managed builds. Figure 47 Tool Settings tabbed page When you select the main entry for a tool on the left of the Tool Settings page, the right side of the page displays the command the tool invokes as well as the options that will be passed to the tool. To edit options passed to a tool, select one of the categories below the tool on the left.
6. 7. 8. Select the Add button to open the Enter Value dialog. Enter –WIEEE_float in the Enter Value dialog, then select OK. Select OK to apply your change and dismiss the Properties dialog. Specifying DEFINES for SQL/MP tables Cross compilers provide the –Wdef_obey= option for passing in an Obey file which sets up DEFINEs. You can, for example, use ADD DEFINE statements to map logical SQL table names to physical table names and avoid hard coding SQL table names in source code.
9. Select the Add button to open the Enter Value dialog. 10. Enter –Wdef_obey=C:\mydefines.txt in the Enter Value dialog, then select OK. 11. Select OK to apply your change and dismiss the Properties dialog. Building for both OSS and Guardian When you create a project with managed builds, the initial project is set up to build for OSS or Guardian, but not both.
Figure 52 Create New Configuration dialog 4. 5. 6. 7. 8. 9. Enter a name for the build configuration (such as Debug Guardian) and optionally enter a description. Make sure Existing configuration is selected and that the configuration specified to the right of it is Debug. As a result, all settings in the Debug configuration are copied to your new configuration. Select OK to add the new configuration and dismiss the Create New Configuration dialog.
Example 10 Incorrect errors for new project source file You can remove the erroneous errors by forcing the indexer to run: 1. In the NonStop Project Explorer view, select the project associated with the source file. 2. Select Index→Rebuild from the NonStop Project Explorer view context menu. Erroneous errors and warnings for SQL Statements By default, CDT’s C/C++ code analysis marks SQL statements in C/C++ source with errors and warnings.
Example 11 Example of errors and warnings shown for SQL statements The .sqlmxStatements.txt and .sqlmpStatements.txt files are read only when Eclipse is started. You must restart Eclipse after creating a project before erroneous errors are removed from editors. Example 12 “Errors for get_dept_rec” shows the same editor and file as Example 11 “Example of errors and warnings shown for SQL statements” does, but after restarting Eclipse. Though many erroneous errors have been removed, some still remain.
Example 12 Errors for get_dept_rec Example 13 “Errors for get_dept_rec removed” shows the same editor and file as Example 12 “Errors for get_dept_rec”, but after get_dept_rec has been added to .sqlmxStatements.txt. The editor still shows errors and warnings. The next two sections explain how to remove these errors and warnings.
Example 13 Errors for get_dept_rec removed TIP: You can view the #define macros loaded by CDT by opening the Paths and Symbols project property page and selecting the Symbols tab, as shown in Figure 53 (page 100).
Figure 53 Symbols tab of the Path and Symbols property page Disabling specific code analysis errors and warnings You can selectively disable code analysis errors and warnings using project properties for code analysis. For example, Example 13 “Errors for get_dept_rec removed” in the previous section shows a C/C++ editor that marks SQL record fields as errors, as the code analyzer does not have definitions of those fields. To disable that type of error: 1.
Figure 54 Disabling record field errors Disabling erroneous syntax warnings When the C/C++ indexer shows erroneous syntax warnings (as shown in Example 13 “Errors for get_dept_rec removed”, you cannot disable the warnings using the Code Analysis property page as shown in the previous section. You have the option of disabling these warnings altogether or making them less obtrusive.
Figure 55 C/C++ Index Markers annotation preferences 4. 102 Tasks Deselect one or all of the check boxes for Vertical ruler, Overview ruler, and Text as. Figure 56 (page 103) shows the same editor and file shown in Example 13 “Errors for get_dept_rec removed” with the result of deselecting Text as but keeping the less obtrusive markers in the vertical and overview rulers so that legitimate syntax errors can still be detected.
Figure 56 Syntax warnings after “Text as” deselected 5. Select OK to apply your changes and dismiss the Preferences dialog. Specifying locations for C/C++ headers, COBOL COPY libraries, and pTAL source files For managed builds, NSDEE provides an Includes settings category for all cross compiler tools and SQL/MX preprocessor tools. Specifying the locations of files to be included in builds similar for all of these tools for including C/C++ headers, COBOL COPY libraries, or pTAL SOURCE files.
Figure 57 Includes settings page Instructing NSDEE not to build source files By default, managed builds build source files in a given project. You can exclude one or more source files from being built using source file properties. This section discusses how to exclude COBOL COPY libraries from builds; however, the same file properties discussed can be used to exclude C, C++, and pTAL sources from builds as well.
Figure 58 Exclude a single COPY library from a build 5. Select OK to apply the change and dismiss the Properties dialog. The file excluded from the build is shown with a pin through it, as a reminder in Figure 59 (page 105): Figure 59 File excluded from build (pin indicator) Excluding all sources in a folder To exclude a folder containing only COBOL COPY libraries from a build, perform the following steps from the NonStop Development perspective: 1. Select the folder in the NonStop Project Explorer view.
Figure 60 Exclude a folder from a build 5. Select OK to apply the change and dismiss the Properties dialog. The folder that will be excluded from the build is shown with a tack in it following. (The tack indicates only that the folder has non-default properties set on it.
Figure 62 Specifying locations of COPY libraries to include in build (for COBOL compilers) 6. Select OK to apply the change and dismiss the Properties dialog. The file that will not be built with SQL/MP options is shown with a tack in it, as shown in Figure 63 (page 107). The tack is shown for any file that has non-default settings.
Figure 64 Turn off SQL/MP folder 6. Select OK to apply the change and dismiss the Properties dialog. The folder that will not be built with SQL/MP options is shown with a tack in it, as shown in Figure 65 (page 108). The tack is shown for any folder that has non-default settings.
4. In the Includes tabbed page of the Paths and Symbols page, select either C or C++ depending on whether the include directory contains C or C++ source. (Select C++ if the include directory contains both.) Figure 66 Paths and Symbols page with C++ selected 5. Select Add... to open the Add directory path dialog: 6. Enter the path of an include directory you want the C/C++ indexer to search. If you enter a project relative path, select the Is a workspace path check box.
Figure 67 Paths and Symbols dialog Changing the system headers indexed when changing build configurations By default, the C/C++ indexer does not regenerate the index when you change build configurations. This is reflected in the path shown for system headers under a project's top-level Includes directory. The index is not regenerated by default because, depending on the size of your code base, regenerating it may take several minutes, particularly when, say, you change from building for TNS/R to TNS/E.
5. Guide. To change the configuration used by the indexer, select a different build configuration in the combo box in the Build configuration for the indexer group box. Select Apply, then OK, to apply the change and dismiss the Properties page. NOTE: effect. A CDT defect requires that you select both Apply and OK for the change to take Forcing a rebuild of the C/C++ index Sometimes you may want to force a rebuild of the C/C++ index if it appears that the indexer has not run or needs to be run again.
Linking libraries in managed builds To link an application against libraries, use the normal mechanisms that compilers provide by putting the options in the list of Additional options in the Linker tool's Miscellaneous page. You also need to link against librld.so to enable your application to load dynamic libraries. For example, if your TNS/E C application needs to link against two shared libraries, one named stdll.tso in project StaticDLL and the other named dydll.
use the appropriate build directory, such as Release, that matches the build configuration you selected for the current project using the Configuration combo box.) 10. To add librld.so to the final link, select the Libraries entry under the C Linker (TNS/E) and select the Add button for Libraries (-l) to open the Enter Value dialog. 11. Enter rld in the Enter Value dialog as shown in Figure 72 (page 113).
Adding and customizing build targets You can add build targets to any type of NSDEE project, including projects that use managed builds. You can also customize predefined build targets for managed builds. How to add and customize build targets is described in the following sections: • “Creating a makefile.
1. 2. 3. Close the text editor open on makefile.targets. Select makefile.targets in the NonStop Project Explorer view. Select Open With→Other... from the context menu of the NonStop Project Explorer view to open the Editor Selection dialog: Figure 75 Editor Selection dialog 4. 5. In the Editor Selection dialog, select Makefile Editor. Select OK to dismiss the dialog and open makefile.targets in the Makefile editor. The Makefile editor will now be the default editor for makefile.
Figure 76 Create Make Target dialog 4. Select OK to add the target and dismiss the dialog. Figure 77 (page 116) shows a target named my_target added to the project Car in the Make Target view. Figure 77 Make Target View 5. Double-click the new target to launch a build with that target. For example, if you were to double-click the my_target target shown in the above figure, NSDEE would invoke make my_target.
1. 2. 3. 4. Select the project of interest in the NonStop Project Explorer view. Select Properties from the context menu for the NonStop Project Explorer view to open the Properties page for the selected project. Select C/C++ Build on the left to open the C/C++ Build page on the right of the Properties dialog. Select the Behavior tabbed page and replace clean with clean-all. Figure 78 Changing clean to clean-all 5. Select OK to apply the change and dismiss the Properties dialog.
Figure 79 Example of output form make clean-all Creating custom deploy targets You can create custom deploy targets for both local managed and makefile projects. The advantage of creating custom deploy targets is that, if you use, for example, sftp (an Open SSH program for file transfers available with Cygwin), you can create much more flexible and complex deploy targets.
Figure 80 Changing the default deploy target name 5. 6. 7. Select OK to save your change and close the Properties dialog. Create a top-level file named makefile.targets. (For details, see “Creating a makefile.targets file for managed builds” (page 114)). Add text similar to the following to makefile.targets (Remember to use a hard tab before the echo command): custom_deploy: all echo -e "put ./Car.
**** Build Finished **** The custom_deploy target above shows only a few of the many sftp commands available. Additionally, you can issue ssh commands to execute commands on NonStop servers if sftp does not provide all the commands you need. For custom Guardian deploy targets, sftp is not as flexible; however, you can combine both sftp and ssh commands to get the same custom_deploy target behavior. Example 14 “Custom Guardian deploy target” shows an example of a custom_deploy target from Guardian.
2. In the C Element Filters dialog, deselect .*resources. 3. Select OK in the C Element Filters dialog. Using NSDEE with SCM tools: examples and procedures You can use local projects with a software configuration management (SCM) tool in one of two ways. The first is to use an Eclipse plug-in provided for use with an SCM tool to check-in and check-out files directly in Eclipse.
a. b. 4. Return to Eclipse and select the project you added files or directories to in the NonStop Project Explorer view. Select Refresh from the context menu. NSDEE detects the new files and directories. To check out changes to a project contributed by others: a. Use the SCM tool to update with the change. b. Select Refresh from the context menu of the NonStop Project Explorer view. NSDEE detects any changed files and updates them.
to the repository. That perspective is particularly useful for viewing file history and for comparing and merging file versions. To see HelloWorld in the SVN Repositories view (in the SVN Repository Exploring perspective): 1. In the SVN Repositories view, select file:///C:/svn-repository 2. Select Refresh from the context menu. 3. Expand file:///C:/svn-repository (if it is not already expanded). 4. Select the HelloWorld directory under file:///C:/svn-repository. 5. Select Refresh from the context menu.
network drives mapped to Samba mount points so you can drag and drop folders and files between NonStop and your Eclipse project. This also allows you to open and edit remote files directly in Eclipse in the same manner you would open and edit local files. To create a linked folder to a network drive, consider the following scenario: Say you have drive S: mapped to an OSS location on a NonStop system and you want to create a linked folder (NonStopFolder) to that location in a project named TestProj.
NOTE: Accessing OSS files via Samba imposes some restrictions on file names. For details, see the Samba on NonStop User Manual. This manual is available in the NonStop Technical Library (NTL) at: www.hp.com/go/nonstop-docs Performance considerations for using Samba with Eclipse Samba is considered a chatty protocol. Though its performance is good in a local intranet, it can be slow over the internet.
6 Reference The NonStop Development perspective is an extension of the C/C++ perspective. This chapter provides reference information about the many ways in which the C/C++ perspective is extended in NSDEE. Views and editors The NonStop Development perspective provides the same views and editors available in the C/C++ perspective with the addition of COBOL and pTAL editor views and the addition of the NonStop Project Explorer view.
Figure 85 Show View dialog with C/C++ specific views Many of the views shown in the NonStop Development perspective are available in the General folder shown in the above figure, whereas the Make Target view is available in the Make folder shown above. NOTE: You can restore the NonStop Development perspective's default views and default view locations by selecting Window→Reset Perspective.... Figure 86 (page 127) shows the one view specific to NonStop available from the Show View dialog.
NonStop Project Explorer view The NonStop Project Explorer view displays the contents of your projects, whether they are remote or local to Windows. Projects are displayed in a tree structure, where the root node is your project folder, and where your project folder contains additional folders and files which may or may not be in your local workspace.
C/C++ editor The C/C++ editor provides a rich set of features for editing C and C++ source files. For details, see the C/C++ Development User Guide. Outline view The Outline view provides an outline of C/C++ methods in the currently active C/C++ editor and can be used to quickly navigate to methods in the active editor. For details, see the C/C++ Development User Guide.
Toolbars available in a terminal view Connect Toolbar toggle button to connect to a remote system configured setting. Disconnect Toolbar toggle button to disconnect an active remote connection. Settings Toolbar push button to open the Terminal settings dialog. Toggle command input field Toolbar toggle buttonto open or close the command input field. New terminal drop down Toolbar drop down button to open a new connection in the same view or open a new Terminal view.
To use SSH: • Open the Terminal Settings dialog by clicking on the Settings push button on the toolbar. • Select SSH from the Connection Type drop down menu. • Enter the host, user, and password. • Click OK. Target Management terminal limitations • The Guardian command tedit is not supported. • The block mode is not supported. • For SSH connections, the OSH command exit terminates the connection instead of taking you back to the TACL prompt. SSH connections usually take you to an OSH prompt.
For more information about Target Management, see http://www.eclipse.org/tm/tutorial/ index.php. New project wizards NSDEE provides separate project wizards for local and remote projects, as well as one import wizard that creates local makefile projects from existing source. This section describes each of these wizards. Local new project wizards Four separate new project wizards can be used for local projects. Each is language-specific but almost identical otherwise.
Table 7 Project types (continued) Setting Description NonStop User Library Select Empty Project to create a managed project that creates a user library (TNS/R only). NonStop Makefile project Select Empty Project to create a makefile project where you supply the makefile. Basic Settings page The Basic Settings page appears only if you select a hello world executable project on the first wizard page.
Table 8 Initial Build Settings page settings (managed builds) (continued) Setting Description SQL tools: Select the SQL/MX or SQL/MP button if your project sources include SQL. Otherwise, select the None button. SQL/MX Preprocessor Locations The combo boxes in this group are only enabled when you select the SQL/MX button. Use the combo boxes to specify the location of C/C++ and/or COBOL preprocessors. NSDEE use these locations to set the environment variables MXSQLC (for C/C++) and MXSQLCO (for COBOL).
Table 10 Remote Settings page settings (no SQL) (continued) Setting Description be passed separately to the -h and -u options, respectively. Target destination (-dir): Optional. Remote directory or subvolume where locally built object is transferred on the selected NonStop system (passed to -dir option for Deploy tool). Target file name (-r): Optional. File name that is given to the remote copy of the transferred file (passed to –r option of Deploy tool).
Table 12 Remote Settings page settings (SQL/MP) (continued) Setting Description user can be passed separately to the –Wsqlhost and -Wsqluser options, respectively. Target file name (-Wsqlprog=): Optional. Specifies the file name given to the final build output when it is copied to a NonStop system (passed as argument to –Wsqlprog=). Working subvolume (-Wsqlwork=): Optional. Specifies the working directory to use on the NonStop system (passed as argument to –Wsqlprog=).
Table 14 Remote Makefile page settings Setting Description Project name: Enter name for top-level project folder. Build system: NonStop system where project files reside and where project is built. Project Location: Location of project on NonStop system. Platform: Choose the OSS or Guardian button based on the platform that your project sources reside on. Connect to Build System... Select this button to establish a connection to the system you select from the Build system: combo.
New File from Template The New File from Template wizard is an extension of the New File wizard by CDT which provides a choice of templates (initial file content) to be used when creating a file. NSDEE extends this wizard to work with remote NSDEE projects in addition to local projects. NOTE: This wizard can only create remote Guardian files using the default file type for the remote Guardian project. To create a file from a template for a non-default file type for Guardian, use the New Source File wizard.
New Source Folder The New Source Folder wizard creates a new source directory for projects with managed builds. It is important to use this wizard for projects with managed builds because it automatically precludes issues with nested folders in builds by setting filters for nested source folders. You can view and edit these filters from the Source Location tab of the Paths and Symbols property page. For details, see the C/C++ Development User Guide. NOTE: This wizard does not support remote projects.
you enter details of where you want files transferred to. The lower Options group box provides various options for file transfer. Table 5 describes the selections you can make in each of the three areas. Table 17 Transfer Files wizard controls Control Description Project and file selection area Directories for project: combo and project directories tree Combo selection sets project shown in the project directory tree. Select a directory to show its files to the right.
Table 18 Import ETK Projects wizard settings Setting Description Solution file: Enter the path to an ETK solution file. Projects: Lists all projects associated with the ETK solution file you enter in the Solution file: field. Deselect any projects you don’t want to import. Copy projects into workspace Copy the files in the ETK projects into your workspace. If your ETK projects are not self-contained, not copying project files may be a better option.
Remote file browser NSDEE provides a remote file browser that is opened by the Browse… button in many dialogs. The name of the browser varies according to what type of object you are browsing for. When you are browsing for a file, for example, the browser name is Choose a file. Figure 88 (page 142) shows the remote browser when opened to choose a Guardian file.
NonStop Development The NonStop Development preference page provides one preference setting, which is the default selection for OSS or Guardian for dialogs that give you a choice of platform. Code Templates The Code Templates preference page provides a link to the C/C++ Code Templates page, where you can change the templates applied to new files you create. NSDEE adds COBOL and pTAL source file templates to those provided by CDT (see Figure 89 (page 143)).
Table 20 Network Connection settings (continued) Setting Description Settings… button (SSH/SFTP) Select to change default settings for SSH and SFTP. Telnet/FTP button Select to use Telnet and FTP protocols. Settings… button (Telnet/FTP) Select to change default settings for Telent and FTP. Connect (Disconnect) button Select to connect (when button name is Connect) or disconnect (when button name is Disconnect) from the currently selected system.
Table 22 Secure Shell Settings dialog settings (continued) Setting Description OK button Apply all changes and dismiss dialog. Cancel button Cancel all changes and dismiss dialog. Telnet/FTP settings The Telnet/FTP Settings dialog lets you configure how Telnet and FTP connect to NonStop systems. To open it, select the Settings… button to the right of the Telnet/FTP button on the Network Connections preference page. Table 23 (page 145) describes settings in the Telnet/FTP settings dialog.
Table 24 Cross Compiler page settings (continued) Setting Description Modify... button Opens the Modify Cross Compilers Location dialog. Delete... button Deletes selected rows from list of RVUs. The Add Cross Compilers dialog lists the RVUs for cross compilers and linkers that can be added. Table 25 (page 146) describes the settings on this page. Table 25 Add Cross Compiler dialog settings Setting Description Location: field Directory under which there are one or more RVUs.
Table 27 Add SQL/MX Preprocessor Location dialog settings (continued) Setting Description Use the above location as root folder* button Select to add a single preprocessor. The location specified must have as the last directory in its path a name that conforms to preprocessor naming conventions. Set the above non-standard location as root folder Select to specify a non-standard directory as the location of the for button SQL/MX preprocessor.
Table 29 Transfer File Wizard preference page settings (continued) Setting Description Options group Group for setting file transfer option preferences. Overwrite existing remote files check box Overwrite remote files if they already exist. Transfer only if modified locally since previous transfer check box Do not transfer local file unless it has been modified since a previous transfer.
Discovery Options The Discovery Options page provides settings for local SQL/MP or SQL/MX C/C++ projects. The settings assist you in turning off warnings and errors shown for SQL statements in C/C++ editors. For details, see “Removing erroneous errors and warnings in C/C++ editors” (page 95). Environment The Environment property page lets you configure what environment variables are set when you build your project and is available for local projects only.
For your convenience, OSS man pages for many tools are available via Help→Help Contents under the entry for NonStop Cross-Compilers and Tools man pages. Cross compilers and tools use almost all the same options as the native OSS versions of the same tools. PC-specific options are documented in the help file provided with NonStop cross compilers and tools. You can also access PC-specific help from the top-level page for NonStop Cross-Compilers and Tools man Pages using the View buttons.
Destination for Deploy Target group This group is available for SQL/MX projects and projects that do not use SQL. Use this group to specify the NonStop system and location where you want the Build Deploy action to transfer your final build object. System for SQL/MX Preprocessor (INVOKE Processing) group This group is available for SQL/MX projects. Use it to specify the NonStop system for SQL/MX INVOKE preprocessing. System for SQL/MP Compile and Deploy group This group is available for SQL/MP projects.
Refactoring History The Refactoring History property page records all refactoring done for a given project and provides facilities for perusing this history. For details, see the C/C++ Development User Guide. Remote Settings The Remote Settings property page is for remote projects only. It lets you change the NonStop system that hosts a remote project. Run/Debug Settings The Run/Debug Settings property page is not supported for NonStop projects.
Table 30 NonStop icons Icon Location Description Tool bar Opens NonStop C++ Project wizard by default. Its pull-down menu allows selection of the project wizard to be opened. Tool bar (pull-down) Shown in the new project icon menu, these icons open one of the new project wizards for NonStop. Run Configurations dialog, Tool bar (pull-down) Represents NonStop run configurations in the Run Configurations dialog.
Table 30 NonStop icons (continued) Icon 154 Reference Location Description NonStop Project Explorer pTAL editor pTAL source file. NonStop Project Explorer NonStop executable file in a remote project. Export wizard NonStop Tools menu Transfer Files export wizard for transferring local project files to NonStop systems. Import wizard NonStop Tools menu Import NSDEE 2.x project as an NSDEE 4.0 managed project. Import wizard Import ETK project as an NSDEE 4.0 managed project.
7 Support and other resources Supported Release Version Updates (RVUs) This document supports NSDEE 4.0 and all subsequent versions of NSDEE until otherwise indicated in a replacement publication. This version is available on J06.10 and subsequent J-series RVUs, and H06.21 and subsequent H-series RVUs. Intended audience This document is intended for developers who are using the NonStop Development Environment for Eclipse (NSDEE). Related information Refer to “Related documentation” (page 11).
A Sample programs and projects Sample programs and projects are included with the NSDEE product. To access these files, unzip the Examples.zip file located at: \plugins\com.hp.nsdee_4.0.0\ Examples.zip can be unzipped to any location, for example C:\Examples. This file contains the following projects: CarSources.
B Tips on setting up password free logins with Open SSH If you install Open SSH with Cygwin, you can use the sftp program to provide more flexible and better performing deploy targets for both managed builds and makefile project builds. For details, see “Creating custom deploy targets ” (page 118). Using sftp in your deploy target, however, requires that you set up passphrase logins for SSH so the deploy target can run sftp in batch mode without having to supply a password.
If the alter user command complains that it does not know your user ID, then use the add user command. For example: % alter user swdev.doon, publickey key1 fingerprint f7:7a:7e:4b:e9:39:c4:85:9c:e5:22:e9:a0:75:07:08 alter user swdev.doon, publickey key1 fingerprint f7:7a:7e:4b:e9:39:c4:85:9c:e5:22:e9:a0:75:07:08 Error, user swdev.doon not found % add user swdev.doon add user swdev.doon OK, user swdev.doon added % alter user swdev.
Figure 91 Using Cygwin Open SSH settings with NSDEE 159
Index Symbols 256-bit encryption enabling for SSH, 72 A add cross compiler, 146 add SQL/MX preprocessor, 146 adding folders and files to projects, 34 B basic settings, 133 binary parsers page, 150 binary tabbed page, 149 browsing files, 142 build artifact page, 150 build directory makefiles written to, 51 build settings page, 137 build steps page, 150 build variables, 44 specifying, 36 build variables property page, 148 builders property page, 148 building projects, 37 builds adding tools to, 151 managed,
importing projects, 73 example files for NSDEE, 31 examples, 156 exporting connection configurations, 72 F file browsing, 142 G getting started how to use NSDEE, 14 I icons build icon, tips on using, 37 deploy icon, tips on using, 38 NonStop project explorer view, 128 NonStop-specific icons in Eclipse, 152 run icon, tips on using, 38 import existing code wizard, 136 importing connection configurations, 73 ETK projects, 73 import ETK projects wizard, 140 import existing code wizard, 136 import NSDEE 2.
initial build settings, makefile projects, 134 initial build settings, managed builds, 133 logging, 149 make settings, 148 properties, 148 remote settings, 134 no SQL settings, 134 settings for SQL/MP, 136 SQL/MX settings, 135 resources property, 148 select configurations, 136 settings, 149 settings (remote), 150 SQL/MX preprocessors, 146 tool chain editor, 151 tool settings, 149 perspective NonStop development, 40 portmapper error Windows firewall, 44 preference page code templates, 143 network connections
enabling 256-bit encryption, 72 support, 155 T tasks view, 129 technical support, 155 telnet/FTP settings, 71 terminal view, 129 tips build icon, 37 deploy icon, 38 relaunching a run configuration, 38 tool chain editor property page, 151 tool locations preference page, 145 specifying, 14 tool settings pages, 149 Tools Changing options, 35 tools changing options, 35 NonStop tools menu, 139 NonStop C, C++, COBOL, and pTAL projects, 132 remote makefile project, 136 transfer files, 139, 147 transfer files wiz
