isCOBOL ESQL is built upon JDBC, and the JDBC specification says that connections should (by default) be in 'autocommit' mode.
That means that every time a modification is made (whether it be INSERT, UPDATE or DELETE), the database is commited automatically.
That scenario is often what is required in plain Java, or COBOL applications.

However, there are some cases where it makes more sense for autocommit mode to be off, such as inside transaction processing environments or programs generated by Pro*COBOL or the DB2 preprocessor which doesn't work in autocommit mode by default.
You also may want to manage the number of commits in a large sequence of INSERT statements by limiting commits to every 1000 or so operations to improve performance.

To turn off autocommit, set this property:

   iscobol.jdbc.autocommit=false

1. How do I set up isCOBOL ESQL Generator for use with Microsoft SQL Server?
2. How do I use isCOBOL ESQL with Microsoft SQL Server?
3. How do I migrate a Vision file to an Oracle database table?
4. Where is the Veryant ESQL generator? What files do I download?
5. How do I connect to a MS SQL 2005 Named Instance?
6. How does isCOBOL limit the size of database query working set for the START statement?
7. How is READ NEXT implemented in isCOBOL ESQL Generator (EasyDB)?
8. How do I get isCOBOL to create a database table when iscobol.file_suffix is set?
9. How is it possible to insert a NULL into an ORACLE TABLE when host variable has been initialized?