The COMMIT WORK statement is the commit operation. The unit of recovery in which the statement is executed is terminated and a new unit of recovery is initiated. All changes made by CREATE, COMMENT ON, DROP, INSERT, UPDATE and DELETE statements executed during the unit of recovery are committed. A COMMIT WORK releases all locks not acquired by a LOCK TABLE statement. See LOCK TABLE for an explanation of the duration of explicitly acquired locks.
This CA Datacom/DB extension has the same effect as COMMIT WORK.
A unit of work is made up of one or more units of recovery. In a batch environment, a unit of work corresponds to the execution of an application program. Within that program, there may be many units of recovery as COMMIT or ROLLBACK statements are executed.
A unit of recovery is a sequence of operations within a unit of work. A unit of recovery is initiated by:
A unit of recovery is terminated by:
A commit or rollback operation affects only the results of SQL statements executed within a single unit of recovery.
Uncommitted database changes made in a unit of recovery may or may not be perceived by other units of work depending on the isolation level selected.
Uncommitted database changes made in a unit of recovery can be backed out by CA Datacom/DB.
Committed database changes can be perceived by other units of recovery and cannot be backed out by CA Datacom/DB.
CA Datacom/DB database changes are also committed when a unit of recovery terminates normally.
|
Copyright © 2014 CA.
All rights reserved.
|
|