Local and remote committable resources

 

A committable resource can be either a local resource or a remote resource.

 

Local committable resource

A local committable resource is on the same system as the application. Each journal associated with resources under commitment control can be thought of as a local location. All the resources that are registered without a journal (optionally for both DDL resources and API resources) can be thought of as a separate local location.

If a committable resource is on an independent disk pool and the commitment definition is on a different disk pool, the resource is not considered local.

 

Remote committable resources

A remote committable resource is on a different system from the application. A remote location exists for each unique conversation to a remote system. A commitment definition might have one or more remote locations on one or more remote systems.

When you place a local resource under commitment control for the system disk pool, or any independent disk pools, use Distributed Relational Database Architecture™ (DRDA^®) to access resources under commitment control in any other independent disk pools. The following table shows the types of committable resources and their locations.

Resource type	Location
API	Local
DDL	Local
DDM	Remote
DRDA	Local or remote
FILE	Local
LU62	Remote
TCP	Remote

 

Parent topic:

How commitment control works with objects

 

Related concepts

Commitment control and independent disk pools