Concurrent Update Intercept

For each row that you change, an update is submitted to Db2 using all columns to qualify the update (see also Method of Updating Db2 ). If the row has not changed since being retrieved, the update succeeds and processing continues normally. However, if the row has changed, or when updating a view and the row no longer matches the view criteria, Db2 returns a +100 SQL code. Detecting the error, File-AID for Db2 flags the row with ERR==> and displays the Concurrent Update Intercept window (Concurrent Update Intercept Window). The window displays once for each row in error, providing you with the ability to specify the disposition for each error individually. Before the window displays, the edit panel is scrolled to position the row in error at the top of the display.

Concurrent Update Intercept Window

End

Take no action and return to the Edit panel. This option provides you with full access to the data in the table before taking further action.

Cancel

Cancel all updates and refetch the table. A rollback is issued to cancel all changes since the last commit. The table is re-fetched and the display is positioned at row 1.

Refetch

Fetch the row in error. The row in error is re-fetched using all columns that are part of unique indexes, except columns that have changed. The row is flagged with FETCH> and the table is redisplayed. If the table is non-indexed, or the row no longer exists (for example, another user changed the index columns), the row cannot be re-fetched. In this case, an error message displays and the row is removed from the display.

Force

Force the update to proceed. The row in error is updated, using all columns in unique indexes, except those that have changed. The row is flagged with UPDATE. Your change overlays the update made by another user. If the update fails because the row no longer exists, the row is inserted and flagged with INSERT.

Re-fetch ALL

Fetch all the rows in error. Processing is the same as for re-fetch except that all rows in error are re-fetched. If you select this option, you avoid repeated window displays because File-AID for Db2 processes all rows in error identically.

Force ALL

Force all the updates to proceed. Processing is the same as for force except that all rows in error are updated or inserted. If you select this option, you avoid repeated window displays because File-AID for Db2 processes all rows in error identically.