@SQLCODE System Field

This integer System Field contains a value that indicates what happened when the preceding SQL statement executed. The values returned in @SQLCODE are shown in Table 19.

VALUE IN @SQLCODE	MEANING
0	The operation was successful.
100	One of the following: A FETCH for which there was no next row. A SELECT or INSERT ... SELECT for which no rows were found. A “searched” UPDATE for which there were no rows to update. A “searched” DELETE for which there were no rows to delete.
Negative	Unsuccessful execution (table not changed).

Figure 19 Values Returned in @SQLCODE

Error Messages

If the ACCENT R ERROR MESSAGES option is enabled, a message is displayed if there are any SQL syntax errors or other runtime errors when the Process Module is executed. Since the SQL statements are dynamic (that is, they can be built within the Process Module), it is possible to have syntax errors at runtime. The text of error messages is located in the system function @ERROR_ MESSAGE. In order to get the error message, you must first store 0 to @ERROR_ NUMBER to trap the error conditions and test for non-zero to indicate an error condition. You may then test @ERROR_MESSAGE for the error which occurred. A complete list of these error messages can be found in the Oracle RDBMS Error Messages and Codes Manual.

Error messages may be enabled with the ICL command ENABLE ERROR MESSAGES and disabled with DISABLE ERROR MESSAGES.

Command Area Trace

If COMMAND AREA TRACE is enabled, each SQL statement that is passed to the server will be displayed as it is executed. The statement will be prefixed by the string "Oracle>>". COMMAND AREA TRACE can be enabled by typing ENABLE COMMAND AREA TRACE and disabled with DISABLE COMMAND AREA TRACE.

Multiple cursors

A cursor is a work area used by ACCENT R and Oracle to contain the results of SQL SELECT and FETCH statements. ACCENT R allows you to be executing row selection on up to 20 SQL tables concurrently.