Error Handling (Magic xpa 3.x)

Magic xpa provides two ways to handle errors. The predefined task error strategy lets you either:

Abort – Magic xpa rolls back the current transaction, whether physical or deferred, removes the current data view, and aborts the task where the error occurs.

Recover – Magic xpa keeps the current data view, stays on the current task, and lets the end user recover from the error.

Sophisticated error handling lets you write actual Magic xpa code for the errors, using error handlers. Magic xpa provides a list of known and expected errors that can be intercepted, and lets you handle other errors specific to your DBMS error code. This level also provides you with a list of new engine directives to control the behavior of the Magic xpa engine after implementing the error handler.