Exception handling v14

By default, any error occurring in an SPL program stops the program from executing. You can trap errors and recover from them by using a BEGIN block with an EXCEPTION section. The syntax is an extension of the normal syntax for a BEGIN block:

[ DECLARE
    <declarations> ]
  BEGIN
    <statements>
  EXCEPTION
    WHEN <condition> [ OR <condition> ]... THEN
      <handler_statements>
  [ WHEN <condition> [ OR <condition> ]... THEN
      <handler_statements> ]...
END;

If no error occurs, this form of block executes all the statements, and then control passes to the next statement after END. If an error occurs in the statements, further processing of the statements is abandoned, and control passes to the EXCEPTION list. The list is searched for the first condition matching the error. If a match is found, the corresponding handler_statements are executed, and then control passes to the next statement after END. If no match is found, the error propagates out as though the EXCEPTION clause wasn't there. You can catch the error by an enclosing block with EXCEPTION. If there is no enclosing block, it aborts the subprogram.

The special condition named OTHERS matches every error type. Condition names aren't case sensitive.

If a new error occurs in the selected handler_statements, this EXCEPTION clause can't catch it, but it is propagated out. A surrounding EXCEPTION clause might catch it.

The following table lists the condition names that you can use.