The commit protocol of a committable resource

 

Commit protocol is the capability a resource has to participate in one-phase or two-phase commit processing. Local resources, except API committable resources, are always two-phase resources.

If a committable resource resides on an independent disk pool and the commitment definition resides on a different disk pool, the resource is not considered as a local resource or a two-phase resource.

A two-phase resource is also called a protected resource. Remote resources and API committable resources must be registered as one-phase resources or two-phase resources when they are placed under commitment control. The following table shows what types of committable resources can coexist in a commitment definition with a one-phase resource.

Resource type	Can coexist with
One-phase API resource	Other local resources. No remote resources.
One-phase remote resource	Other one-phase resources at the same location. No local resources.

 

Parent topic:

How commitment control works with objects

 

Related concepts

Commitment control and independent disk pools