Distributed unit of work allows an application to access more than one database within a unit of work; that is, the application can switch between databases before committing the data. This gives an application programmer the ability to do work involving multiple databases, local and remote, at the same time.
DB2 Connect always lets you read multiple databases within a unit of work. Whether you can update multiple databases depends on the products you are using:
The above is true for native DB2 UDB applications and applications coordinated by an external Transaction Processing Monitor such as IBM TXSeries, CICS for Open Systems, Encina Monitor, and Microsoft Transaction Server.
If the application is controlled by a Transaction Processing Monitor such as IBM TXSeries, CICS for Open Sytems, Encina Monitor, or Microsoft Transaction Server, then you must use the DB2 Syncpoint Manager. With DB2 UDB Version 5.2 (including DB2 UDB EE, DB2 UDB EEE, and DB2 Connect EE), the DB2 Syncpoint Manager has been enhanced to support TCP/IP connections.
If the application is a native DB2 UDB application, then the DB2 Syncpoint Manager is not required for two phase commit.
If a common DB2 Connect Enterprise Edition gateway is used by both native DB2 applications and TP Monitor Applications to access host data over TCP/IP connections then the DB2 Syncpoint Manager must be used.
| Note: | If a single DB2 Connect Enterprise Edition gateway will be used to access host data using both SNA and TCP/IP network protocols and two phase commit is required, then the DB2 Syncpoint Manager must be used. This is true for both DB2 Applications and TP Monitor applications. |
In order to take advantage of distributed unit of work support, you must be familiar with the concepts described in the Administration Guide and the SQL statements described in the SQL Reference.
For more information about two-phase commit, see:
For more information about Transaction Monitors, and setting up a TP monitor environment, see: