Filter
Top Products
Chapter 10. Running Your Own Applications
Various types of applications can access DB2 databases:
v Applications developed using the DB2 Software Developer’s Kit that
include embedded SQL, APIs, stored procedures, user-defined functions or
calls to the DB2 CLI.
v ODBC applications such as Lotus Approach.
v JDBC applications and applets.
v Net.Data macros containing HTML and SQL.
An application on a DB2 client can access a remote database without knowing
its physical location. The DB2 client determines the location of the database,
manages the transmission of the requests to the database server, and returns
the results.
In general, to run a database client application, use the following steps:
1. Ensure the server is configured and running.
Be sure that the database manager is started on the database server to
which the application program is connecting. If it is not, you must issue
the db2start command at the server before starting the application.
2. Ensure that you can connect to the database that the application uses.
3. Bind the utilities and the applications to the database. See “Binding
Database Utilities” for information about binding the utilities.
4. Run the application program.
Binding Database Utilities
You must bind the database utilities (import, export, reorg, the command line
processor) and DB2 CLI bind files to each database before they can be used
with that database. In a network environment, if you are using multiple
clients that run on different operating systems or are at different versions or
service levels of DB2, you must bind the utilities once for each operating
system and DB2-version combination.
Binding a utility creates a package, which is an object that includes all of the
information that is needed to process specific SQL statements from a single
source file.
© Copyright IBM Corp. 1993, 1999 119