RC/Edit Error Processing

When changes are saved (END, SET or SAVE commands), those changes are then committed to DB2. However, there is the possibility of an error, even though RC/Edit performs security and type checking during entry.
carcudb2
When changes are saved (END, SET or SAVE commands), those changes are then committed to DB2. However, there is the possibility of an error, even though RC/Edit performs security and type checking during entry.
Some possible errors include:
  • Duplicate key for a unique index on an insert or update
  • A security violation, occurring when someone removes user authority while the user is editing the data
  • Table contention in the Searched Update Method, occurring when issuing the SET or SAVE command at the same time as another user is committing data. Wait a minute and then try again, and the deadlock should be over.
When an error occurs, the Error screen appears. The row in error appears along with a corresponding error message. The user has four options: Ignore the row, Retry the request, Cancel the edit session, or View the full message text for the error. Update the row by moving the cursor to the appropriate fields. Only the primary edit commands TYPE or EXPLODE can be entered. For information about the fields, press F1 (Help).