DB2 Connect User's Guide

Remote Unit of Work

A remote unit of work lets a user or application program read or update data at one location per unit of work. It supports access to one database within a unit of work. While an application program can update several remote databases, it can only access one database within a unit of work.

Remote unit of work has the following characteristics:

For example, Figure 2 shows a database client running a funds transfer application that accesses a database containing checking and savings account tables, as well as a banking fee schedule. The application must:

Figure 2. Using a Single Database in a Transaction


Using a Single Database in a Transaction

To set up such an application, you must:

  1. Create the tables for the savings account, checking account and banking fee schedule in the same database as described in the Administration Guide.
  2. If physically remote, set up the database server to use the appropriate communications protocol, as described in the Quick Beginnings books
  3. If physically remote, catalog the node and the database to identify the database on the database server, as described in the Quick Beginnings books
  4. Precompile your application program to specify a type 1 connection; that is, specify CONNECT(1) on the PREP command, as described in the Application Development Guide.


[ Top of Page | Previous Page | Next Page ]