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.
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:
To use the successfully built DbtuTools framework the following requirements need to be met:
The Makefile is the central point for building the DbtuTools framework. Here the dependencies are defined.
Currently there are preconfigured Makefiles for the AIX, Linux and Solaris platform. Select the proper one and check the defaults of the first section - remarked as "Defaults for build environment".
|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:
|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>
|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.