OpenEdge Data Management: DataServer for Microsoft SQL Server

RDBMS Stored Procedure Details
Handling errors
3–30
The RUN STORED–PROC statement supports the NO–ERROR option. Example 3–22 shows how to
trap errors within a procedure.
DEFINE VARIABLE ix AS INTEGER NO-UNDO.
RUN STORED-PROC send-sql-statement NO-ERROR
("select count (*) from xxx.customer where name between ’A’ and ’Z’ ").
IF ERROR-STATUS:ERROR THEN DO:
DO ix = 1 TO ERROR-STATUS:NUM-MESSAGES:
MESSAGE "error" ERROR-STATUS:GET-NUMBER(j)
ERROR-STATUS:GET-MESSAGE(j).
END.
END.
CLOSE STORED-PROC send-sql-statement.
Example 3–22: Trapping errors within a procedure
Trapping errors when using Load-Result-Into
By properly positioning the NO-ERROR in the RUN statement, error information can also be
retrieved from attempted SQL execution at the data source when using LOAD-RESULT-INTO.
Example 3–23 shows how errors are trapped after LOAD-RESULT-INTO stored procedure
execution.
DEFINE VARIABLE hTables AS HANDLE EXTENT 1 NO-UNDO.
RUN STORED-PROC send-sql-statement LOAD-RESULT-INTO hTables NO-ERROR
("Invalid SQL Statement").
IF ERROR-STATUS:ERROR THEN
MESSAGE ERROR-STATUS:GET-MESSAGE(1) VIEW-AS ALERT-BOX.
ELSE
MESSAGE "SQL call was successful." VIEW-AS ALERT-BOX.
Example 3–23: Trapping errors using LOAD-RESULT-INTO
Error messages related to using the Load-Result-Into
phrase
Note the following situations in which error conditions related to the use of LOAD-RESULT-INTO
are reported:
• The compiler issues an error if you try to specify PROC-HANDLE and LOAD-RESULT-INTO on
the same Run STORED-PROC statement.
• The compiler issues an error if you use PROC-STATUS without specifying the
LOAD-RESULT-INTO function.