Build

To build the DbtuTools framework please verify the requirements first. Then have a look at the Makefile to ensure all defaults [more] match your environment.

Requirements

This package comes with some requirements to ensure successful build and usage of the DbtuTools framework.

For the build phase (can be done on another machine running the same platform as the target system) the requirements are:

• An installed version of the make tool (like nmake).
• A proper C compiler (like IBM's Visual Age C++).
• A proper Java Development Kit (JDK).
• The DB2 Software Development Kit / Application Development Kit.

To use the successfully built DbtuTools framework the following requirements need to be met:

• A proper Java Runtime Environment (JRE) version 1.2 or higher (for most tools).
• the DB2 software (the client components are enough, but JDBC 2.0 must be used).

Makefile

The Makefile is the central point for building the DbtuTools framework. Here the dependencies are defined.

Currently there is one preconfigured Makefiles for the Windows platform. Select the proper one and check the defaults of the first section - remarked as "Defaults for build environment".

Variable	Effect
C_COMPILER	This variable defines the name of the binary, which should be called as C compiler. The default should be ok for most environments.
JAVA_COMPILER	This variable defines the name of the binary, which should be called as JAVA compiler. The default should be ok for most environments.
DB2_LPP_PATH	Here you have to define the root path to the binaries of your DB2 installation. This depends on platform and DB2 version - for DB2 UDB Version 7.1/7.2 you can use the following: C:\Program Files\SQLLIB (under Windows) If you are unsure, look at the sqllib subdirectory of one of your DB2 instance owners and check the symbolic links. In my environment for example, /home/db2inst1/sqllib/bin/ points to /usr/IBMdb2/V7.1/bin/
PREP_DBALIAS	Some of the tools are using Embedded SQL to access the DB2 database(s). Therefore we have to do a "prepare" against an existing database. Right now, this should not have any influence to the database, but if you want to be on the safe side, it may be a good idea to create one for this approach: db2 CREATE DATABASE <name> make clean; make all db2 DROP DATABASE <name>
DBTUTOOLS_DEVEL_TRACE	Some of the sourcefiles contain additional code to write development traces to the STDERR stream. This is only for development and may be interesting for bug reporting. As a normal user, it makes sense to stay with the default value "0". Everything other than "0" activates the trace routines.