Effects of calling SQLTransact() in a DB2 UDB CLI application

 

Here are some effects of calling SQLTransact() in a DB2^® UDB call level interface (CLI) application. When a transaction ends:

• All statements must be prepared before they can be used again.

• Cursor names, bound parameters, and column bindings are maintained from one transaction to the next.

• All open cursors are closed.

 

Parent topic:

Committing or rolling back in a DB2 UDB CLI application

 

Related reference

SQLTransact - Commit or roll back transaction