Commitment control errors

 

When you use commitment control, it is important to understand which conditions cause errors and which do not.

In general, errors occur when commitment control functions are used inconsistently, such as running an End Commitment Control (ENDCMTCTL) command when files that use the commitment definition are still open.

 

Errors during commit processing

If a communications or system failure occurs during a commit operation, resynchronization might need to be performed to ensure that the transaction managers keep the data consistent on all the systems involved in the transaction. The behavior of the resynchronization and how it affects the commit operation depends on these factors :

If the failure is catastrophic such that it can never be repaired, or it cannot be repaired in a timely manner, the system operators for other systems involved in the transaction must make a heuristic decision. The heuristic decision commits or rolls back the changes made on that system during the transaction. If the failure is repaired after such a decision, and the resynchronization detects that the decision caused data integrity problems, message CPD83D9 or CPD83E9 is sent to the QSYSOPR message queue.

 

Parent topic:

Troubleshooting transactions and commitment control

 

Related concepts


Commitment definition for two-phase commit: Not wait for outcome
States of the transaction for two-phase commitment control