Filter
Top Products
TP Monitor multisite update can coordinate a transaction that accesses both
DB2 and non-DB2 resource managers such as Oracle, Informix, SQLServer, etc.
Native SQL multisite update is used with DB2 servers only.
For a multisite update transaction to work, each of the databases participating
in a distributed transaction must be capable of supporting Distributed Unit of
Work. At the time of this writing, the following DB2 servers provided DUOW
support that enabled them to participate in distributed transactions:
v DB2 Common Server V2
v DB2 Universal Database V5 and V6
v DB2 for MVS/ESA V3.1 and 4.1
v DB2 for OS/390 V5.1
v DB2 Universal Database for OS/390 V6.1
v DB2/400 V3.1 or later (using SNA only at this time)
v DB2 Server for VM and VSE V5.1 and 6.1
A distributed transaction can update any mix of supported database servers.
For example, your application can update several tables in DB2 Universal
Database on Windows NT, a DB2 for OS/390 database and a DB2/400
database all within a single transaction.
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. The need for SPM is dictated by the choice of protocol (SNA vs.
TCP/IP) and use of a TP monitor. See the following table for a summary of
scenarios that require use of the SPM. The table 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.
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
98 Quick Beginnings