Host and AS/400 database servers require DB2 Connect to participate in a distributed transaction originating from PC, UNIX, and Web applications. In addition, many of the multisite update scenarios that involve host and AS/400 database servers require that the Syncpoint Manager (SPM) component be configured. When a DB2 instance is created, the DB2 SPM is automatically configured with default settings.
The need for SPM is dictated by the choice of protocol (SNA or TCP/IP) and
use of a TP monitor. The following table provides a summary of
scenarios that require the use of SPM. The table also shows that DB2
Connect is required for any access to the host or AS/400 from Intel or UNIX
machines. In addition, for multisite updates, the SPM component of DB2
Connect is required if the access is via SNA or uses a TP monitor.
Table 8. Host and AS/400 multisite update scenarios that require SPM
| TP Monitor Used? | Protocol | SPM Needed? | Product Required (choose One) | Host and AS/400 Database Supported | ||
|---|---|---|---|---|---|---|
| Yes | TCP/IP | Yes |
|
| ||
| Yes | SNA | Yes |
|
| ||
| No | TCP/IP | No |
|
| ||
| No | SNA | Yes |
|
|
| Note: | A distributed transaction can update any mix of supported database
servers. For example, your application can update several tables in DB2
UDB on Windows NT, a DB2 for OS/390 database and a DB2/400 database all within
a single transaction.
For more information about two-phase commit, as well as instructions for setting up for several popular TP monitors, refer to the Administration Guide. You can also access the DB2 Product and Service Technical Library on the World Wide Web:
|