This statement exits the
CATCH handling of a
and resumes processing after the statement that raised the exception. This statement can only be executed
CATCH block of a
TRY control structure for which the addition BEFORE
UNWIND is declared. When exception handling is exited using
RESUME, the context of the exception is not deleted and any
CLEANUP blocks are not executed.
The following are prerequisites for resuming processing:
The exception was raised as a resumable exception by the addition
RESUMABLEof the statement RAISE EXCEPTION or by the addition
THROWin a conditional expression.
The exception was declared with the addition
RAISINGin the interface of all procedures from which it was propagated (if it is not an exception derived from CX_NO_CHECK).
If these points do not apply, an exception of the class CX_SY_ILLEGAL_HANDLER is raised. To check whether
the prerequisites are met, the instance attribute IS_RESUMABLE with type
of the current exception object can be checked. The value of the attribute is set using the addition
INTO when the statements
are executed and when an exception object is reused using the statement
- If the resumable exception was not raised by the variant RAISE RESUMABLE EXCEPTION oref, the handler can send information to the raiser of the event by assigning values to appropriate attributes of the exception object.
- Resuming processing after an exception is particularly useful if the exception was raised when a special method was called, such as a constructor or a functional method in an operand position.
CATCHblock is not exited using
RESUMEwhen handling a resumable exception, the program does not continue in the context of the statement that raised the exception (as described in System Response After a Class-Based Exception). This context is deleted when the
CATCHblock is exited, at the latest.
Cause: Exception cannot be resumed. The ID of the exception text is NOT_RESUMABLE