Connect and commitment control restrictions

 

There are restrictions on when you can establish the connection using commitment control. The restrictions also apply if you attempt to run statements using commitment control, but you specified COMMIT(*NONE) on the connection.

If a two-phase undetermined or updatable resource is registered or a one-phase updatable resource is registered, another one-phase updatable resource cannot not be registered.

Furthermore, when protected connections are inactive and the DDMCNV job attribute is *KEEP, these unused DDM connections will also cause the CONNECT statements in programs compiled with RUW connection management to fail.

If running with RUW connection management and using the job-level commitment definition, then there are some restrictions.

• If the job-level commitment definition is used by more than one activation group, all RUW connections must be to the local relational database.

• If the connection is remote, only one activation group may use the job-level commitment definition for RUW connections.

 

Parent topic:

Distributed support