Determining why an error occurred
You can find more information about the error detected against
a row by typing E in the prefix field for that row.
An error information panel is displayed with an explanation of why Db2® rejected the change operation.
If the SQLCODE is displayed in the prefix area, see the Db2 UDB for z/OS Messages and Codes for a detailed explanation of the error.
Some errors are the result of referential integrity (RI) constraint
violations. If the RI relationship applies to two tables, these errors
are indicated by the presence of an R
in the rightmost position
of the prefix area.
You can use the RE prefix command against rows with RI errors that apply to two tables to start another FM/Db2 Edit session. The new session is an Edit session for the other table affected by the RI error.
Related tasks
Related references