![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The COMMIT statement applies all changes made to TDS and external data since the last synchronization point. You do not need to explicitly issue a COMMIT at the end of a transaction. Data is implicitly committed for you at the end of the transaction.
• You can use the COMMIT statement before the commit limit is reached or when the exception ON COMMITLIMIT is signaled.
• The COMMIT statement does not release locks. The locks are released on the affected table at transaction end.
• When issuing a COMMIT, you can get an unusual and untrappable SYNC error resulting from the COMMIT updating too many page buffers in the Data Object Broker. The number of page buffers is determined by the WORKINGSET Data Object Broker parameter.
To avoid SYNC errors against updates to a parameterized table, issue a COMMIT at the end of the updates to each instance of the table.
Signaled if the maximum number of updates (INSERTs, REPLACEs, or DELETEs) between synchronization points is reached
1.
2. FORALL $EMPLOYEES:
FORALL EMPLOYEES($EMPLOYEES.REGION):
EMPLOYEES.SALARY = EMPLOYEES.SALARY + 100;
REPLACE EMPLOYEES($EMPLOYEES.REGION);
END;
COMMIT;
END;
3.
• In example 1, the COMMIT statement commits the insertion to the EMPLOYEES table so that the inserted occurrence can be retrieved in the FORALL.
• In example 2, a commit is made at the end of the updates to each instance of the EMPLOYEES table.TIBCO Object Service Broker Parameters about the Data Object Broker parameters.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |