Host and System i™ database servers require DB2 Connect™ to participate in a distributed transaction originating from Linux™, Windows®, UNIX®, and web applications. In addition, many of the multisite update scenarios that involve host and System i database servers require that the sync point 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 (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 if DB2 Connect is required for any access to the host or System i from Intel® or UNIX machines. For multisite updates, the SPM component of DB2 Connect is required if you are using a TP monitor.
| Transaction Processor Monitor Used? | Sync Point Manager Needed? | Product Required (Choose One) | Host and System i Database Supported |
|---|---|---|---|
| Yes | Yes |
DB2 Connect server product DB2 Enterprise Server Edition with DB2 Connect license applied |
DB2 Universal Database (UDB) for OS/390® and z/OS® V7 DB2 UDB for z/OS V8 or later |
| No | No |
DB2 Connect Personal Edition DB2 Connect server product DB2 Enterprise Server Edition with DB2 Connect license applied |
DB2 UDB for OS/390 and z/OS V7 DB2 UDB for z/OS V8 or later |
Note: A distributed transaction can update any mix of supported database servers. For example, your application can update several tables in a DB2 database on Windows, a DB2 for OS/390 database and a DB2 for i5/OS database all within a single transaction.
Parent topic: Multisite Updates