Types of committable resources

Types of committable resources

This table lists the different types of committable resources, including FILE, Data Definition Language (DDL), distributed data management (DDM), logical unit (LU) 6.2, Distributed Relational Database Architecture™ (DRDA^®), API, and TCP.
The table shows the following items:

The types of committable resources.

How they are placed under commitment control.

How they are removed from commitment control.

Restrictions that apply to the resource type.

Resource type How to place it under commitment control How to remove it from commitment control What kinds of changes are committable Restrictions

FILE- local database files Opening under commitment control¹ Closing the file, if no changes are pending.
If changes are pending when the file is closed, after performing the next commit or rollback operation.
Record-level changes No more than 500 000 000 records can be locked for a single transaction².
DDL- object-level changes to local SQL tables and SQL collections. Running SQL under commitment control Performing a commit or rollback operation after the object-level change. Object-level changes, such as:

Create SQL package

Create SQL table

Drop SQL table
Only object-level changes made using SQL are under commitment control.
DDM- remote distributed data management (DDM) file Opening under commitment control. Commitment control support for DDM has more information about commitment control and distributed data management. Closing the file, if no changes are pending.
If changes are pending when the file is closed, after performing the next commit or rollback operation.
Record-level changes
LU 6.2- protected conversation Starting the conversation³ Ending the conversation
DRDA- distributed relational database Using SQL CONNECT statement Ending the connection
API- local API commitment resource Add Commitment Resource (QTNADDCR) API Remove Commitment Resource (QTNRMVCR) API The user program determines this. Journal entries might be written by the user program using the Send Journal Entry (QJOSJRNE) API to assist with tracking these changes. The application must provide an exit program to be called during commit, rollback, or resynchronization operations.
TCP-TCP/IP connection Using SQL CONNECT statement to an RDB defined to use TCP/IP connections, or opening a DDM file defined with a TCP/IP location Ending the SQL connection, or closing the DDM file if no changes are pending. If the DDM file is closed with changes pending, the connection is closed after performing the next commit or rollback operation.
Notes:

¹ For details on how to place a database file under commitment control, see the appropriate language reference manual. Related information for commitment control links to language manuals that you can use.

² You can use a QAQQINI file to reduce the limit of 500 000 000. See Managing transaction size for instructions.

³ When a DDM connection is started, the DDM file specifies PTCCNV(*YES), and the DDM file is defined with an SNA remote location; an LU 6.2 resource is added with the DDM resource.
When a DRDA connection is started, an LU 6.2 resource is added with the DRDA resource if both of the following conditions are true:

The program is using the distributed unit of work connection protocols.

The connection is to a rational database (RDB) that is defined with an SNA remote location. For more information about starting protected conversions, see APPC Programming
.

Parent topic:
How commitment control works with objects

Related concepts

Commitment control support for DDM
Updates to the notify object

Related reference

Add Commitment Resource (QTNADDCR) API
Remove Commitment Resource (QTNRMVCR) API
Send Journal Entry (QJOSJRNE) API

Resource type	How to place it under commitment control	How to remove it from commitment control	What kinds of changes are committable	Restrictions
FILE- local database files	Opening under commitment control¹	Closing the file, if no changes are pending. If changes are pending when the file is closed, after performing the next commit or rollback operation.	Record-level changes	No more than 500 000 000 records can be locked for a single transaction².
DDL- object-level changes to local SQL tables and SQL collections.	Running SQL under commitment control	Performing a commit or rollback operation after the object-level change.	Object-level changes, such as: Create SQL package Create SQL table Drop SQL table	Only object-level changes made using SQL are under commitment control.
DDM- remote distributed data management (DDM) file	Opening under commitment control. Commitment control support for DDM has more information about commitment control and distributed data management.	Closing the file, if no changes are pending. If changes are pending when the file is closed, after performing the next commit or rollback operation.	Record-level changes
LU 6.2- protected conversation	Starting the conversation³	Ending the conversation
DRDA- distributed relational database	Using SQL CONNECT statement	Ending the connection
API- local API commitment resource	Add Commitment Resource (QTNADDCR) API	Remove Commitment Resource (QTNRMVCR) API	The user program determines this. Journal entries might be written by the user program using the Send Journal Entry (QJOSJRNE) API to assist with tracking these changes.	The application must provide an exit program to be called during commit, rollback, or resynchronization operations.
TCP-TCP/IP connection	Using SQL CONNECT statement to an RDB defined to use TCP/IP connections, or opening a DDM file defined with a TCP/IP location	Ending the SQL connection, or closing the DDM file if no changes are pending. If the DDM file is closed with changes pending, the connection is closed after performing the next commit or rollback operation.
Notes: ¹ For details on how to place a database file under commitment control, see the appropriate language reference manual. Related information for commitment control links to language manuals that you can use. ² You can use a QAQQINI file to reduce the limit of 500 000 000. See Managing transaction size for instructions. ³ When a DDM connection is started, the DDM file specifies PTCCNV(*YES), and the DDM file is defined with an SNA remote location; an LU 6.2 resource is added with the DDM resource. When a DRDA connection is started, an LU 6.2 resource is added with the DRDA resource if both of the following conditions are true: The program is using the distributed unit of work connection protocols. The connection is to a rational database (RDB) that is defined with an SNA remote location. For more information about starting protected conversions, see APPC Programming .