‎2008 Apr 07 6:10 AM
Hello experts,
My programme executes a dynamic open sql and the requirement is, my programme should never result in an ABAP short dump.
With ABAP release 610, I can catch class based exceptions like cx_sy_dynamic_osql_error, but under 46C, I can only use CATCH SYSTEM-EXCEPTIONS, but no sql exceptions can be found in the runtime error list, that means no sql exceptions are perceived as catchable runtime errors.
Therefore, could you advise how I should handle the runtime exceptions and not cause the ABAP short dump, please?
Thanks and best regards,
James
‎2008 Apr 07 2:43 PM
http://help.sap.com/saphelp_nw04/helpdata/en/a9/b8eef8fe9411d4b2ee0050dadfb92b/content.htm
will TRY and the CATCH statement be of any use ?
‎2008 Apr 08 2:30 AM
Hi there,
Class based exceptions are introduced starting from ABAP 610, therefore under 46C, I'm not allowed to use that.
Thanks and best regards,
James
‎2008 Apr 08 2:57 AM
Hi,
Don't think if you can catch those exception in 46C.
Regards,
Atish
‎2008 Apr 08 3:01 AM
Hi there,
No, TRY is even not a keyword under ABAP 46C.
Best regards,
James