Handling errors during an Edit session

FM/Db2 might report errors if it attempts to implement the changes to data that you have made in an Edit session. These errors are detected by Db2® when FM/Db2 issues INSERT, UPDATE, or DELETE SQL statements. SQL errors can arise for many reasons, including violation of uniqueness, referential integrity and check data constraints defined on the Db2® object being edited. If you are unfamiliar with these concepts, see the Db2 UDB for z/OS Administration Guide.

If FM/Db2 detects an error, it marks the row that caused the error with either =ERR , =ERR R, or the SQLCODE in the prefix area. The choice of error indicator is determined by the Show SQLCODE editor option. Rows that were deleted are reinserted at the top of the current display (in TABL display format). Save operations cannot proceed until all pending errors have been corrected. If the Db2® object you are editing is subject to many constraints, or if many changes have been made to the data without verification, it might be impossible to resolve all errors. In this situation, cancel the Edit session.

Related tasks

Related references