Distributed unit of work connection considerations

 

When you connect in a distributed unit of work application, consider these points.

• If the unit of work will perform updates at more than one application server and commitment control will be used, all connections over which updates will be done should be made using commitment control. If the connections are done not using commitment control and later committable updates are performed, read-only connections for the unit of work are likely to result.

• Other non-SQL commit resources, such as local files, DDM files, and commitment control API resources, will affect the updatable and read-only status of a connection.

• If you connect using commitment control to an application server that does not support distributed unit of work (for example, a V4R5 system using TCP/IP), that connection is either updatable or read-only. If the connection is updatable, it is the only updatable connection. Since V5R3, Distributed Relational Database Architecture™ (DRDA^®) two-phase-commit operations have taken the following updates into consideration:

  • Updates done as a result of triggers

  • Updates done as a result of user-defined functions that are activated during a database query

 

Parent topic:

Distributed support