Validating and saving changes with a File Manager/Db2 editor session
In Edit only, you can make changes to the data and save those changes to Db2®.
An Edit session of a Db2® object has important differences when compared to an Edit session of a data set. These differences need to be understood to make the most effective use of a File Manager/Db2 Edit session.
Db2® data is accessed by calls
to Db2®. Some important Db2® concepts are discussed here
because an understanding of these concepts is central to understanding
how the FM/Db2 editor operates:
- Db2® unit of work
- A Db2® unit of work commences when a process initially connects to, or accesses data from, Db2®. The unit of work continues until the process ends the connection or issues an explicit Db2® COMMIT or ROLLBACK statement. Between the start and end of the unit of work, the process may make many calls to Db2® to read (fetch) change (update), insert, or delete rows.
- Db2® COMMIT
- This is a Db2® command that is used to signal the end of the current unit of work. A Db2® commit occurs automatically when a process ends; however, a Db2® commit may also be issued to finalize any pending changes to Db2® data. Issuing a Db2® commit is an irrevocable step. After the commit, it is not possible to reverse (back out) any changes made since the start of the unit of work.
- Db2® ROLLBACK
- This is a Db2® command that is used to signal that all pending changes for the current unit of work are to be reversed (backed out). After the rollback is processed, the Db2® data is in the same state that it was in at the start of the unit of work, or at the last commit point.
For more information about Db2® units of work, commit, and rollback, see "Db2® Concepts (Application Processes, concurrency and recovery)" in the SQL Reference manual, for the appropriate version of Db2®.