topic Re: Nested Exception Handling in Application Development and Automation Discussions

Nested Exception Handling

Former Member — Mon, 17 Nov 2014 11:18:55 GMT

Dear All,

REPORT 1

calls a class CLASS 1 -> METHOD1

TRY.

CLASS 1 -> METHOD1 calls a Funnction Module FM1

CATCH.

ENDTRY.

*****************************************************************************

FM1 calls CLASS 1 -> METHOD2

CLASS 1 -> METHOD2 calls

if X1

CLASS 1 -> METHOD3

Raises Exception class CX1

elseif X2

if XX1

CLASS 1 -> METHOD4

Raises Exception class CX1

else XX2

CLASS 1 -> METHOD5

Raises Exception class CX1

endif.

How can I revert back to the report program REPORT1 with the raised exception.

I have tried the CLEANUP statement, it cleans up the exception if not caught in the TRY-CATCH-ENDTRY block.

Should the exception be caught in every caller program and propagated outside the call.

Re: Nested Exception Handling

SuhaSaha — Mon, 17 Nov 2014 11:36:55 GMT


Should the exception be caught in every caller program and propagated outside the call.

If you want to propagate an exception, why do you want to catch it?

In order to propagate the exception to the original report then define it in the procedure's (method, FM, subroutine) signature. I don't think that CLEANUP would serve the purpose.

BR,

Suhas

Re: Nested Exception Handling

Former Member — Mon, 17 Nov 2014 11:41:02 GMT

I have defined that in the signature of all the caller program,

but gives a short dump after being raised.

Re: Nested Exception Handling

SuhaSaha — Mon, 17 Nov 2014 11:46:09 GMT


Soumen Das wrote:

I have defined that in the signature of all the caller program,

but gives a short dump after being raised.

Short dump => the exception was not handled in the caller / incorrect exception was handled. Without additional details it's not possible to analyse your problem.

Re: Nested Exception Handling

former_member202818 — Mon, 17 Nov 2014 11:47:06 GMT

Hi Das,

Are you calling one program from another?