Administration Guide

Using a Single Database in a Transaction

The simplest form of transaction is to read from and write to only one database within a single unit of work. This type of database access is called a remote unit of work.

Figure 38. Using a Single Database in a Transaction

Figure 38 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:

• Accept the amount to transfer from the user interface
• Subtract the amount from the savings account, and determine the new balance
• Read the fee schedule to determine the transaction fee for a savings account with the given balance
• Subtract the transaction fee from the savings account
• Add the amount of the transfer to the checking account
• Commit the transaction (unit of work).

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 (see Chapter 13, Before Creating a Database)
2. If physically remote, set up the database server to use the appropriate communications protocol, as described in the Installation and Configuration Supplement
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 (the default) on the PRECOMPILE PROGRAM command, as described in the Application Development Guide.