Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 The Action Statements : COMMIT Statement

COMMIT Statement
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.
Usage Notes
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.
Exceptions
 
Signaled if the maximum number of updates (INSERTs, REPLACEs, or DELETEs) between synchronization points is reached
Examples
1.
INSERT EMPLOYEES WHERE REGION = 'MIDWEST';
COMMIT;
FORALL EMPLOYEES WHERE REGION = 'MIDWEST':
2.
FORALL $EMPLOYEES:
   FORALL EMPLOYEES($EMPLOYEES.REGION):
   EMPLOYEES.SALARY = EMPLOYEES.SALARY + 100;
   REPLACE EMPLOYEES($EMPLOYEES.REGION);
   END;
   COMMIT;
END;
3.
INSERT EMPLOYEES('MIDWEST');
____________________________________
ON COMMITLIMIT:
COMMIT;
About the Examples
In example 1, the COMMIT statement commits the insertion to the EMPLOYEES table so that the inserted occurrence can be retrieved in the FORALL.
See Also
TIBCO Object Service Broker Parameters about the Data Object Broker parameters.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved