Which exceptions are really catchable?

Question

Hi,
In the documentation, following exception groups are listed:
u2022 Execution errors (1001)
u2022 Database access errors (1002)
u2022 Database connection errors (1003)
u2022 Flat file processing errors (1004)
u2022 File access errors (1005)
u2022 Repository access errors (1006)
u2022 SAP system errors (1007)
u2022 System resource exception (1008)
u2022 SAP BW execution errors (1009)
u2022 XML processing errors (1010)
u2022 COBOL copybook errors (1011)
u2022 Excel book errors (1012)
u2022 Data Quality transform errors (1013)
from this list, I understand that the number in parathesis represent a group of numbers in a certain range.
Yet, I am puzzled by the numbers that are thrown and catched or not by Data Services at runtime.
Example 1
In a try/catch, I have selected ALL errors to be catchable. The script in the catch editor is printing the error number and message. I have an audit rule which fails. The number of the message is NOT within the groups mentioned above, yet it is catched. What is the meaning of those numbers exactly? The error in this example is  RUN-050450 which seems to cover the audit rule failure. Why is this catch but not in the groups above? Unless those numbers mean something else?
Example 2
In a try/catch, I have selected ALL errors to be catchable. In this, there is an issue with the mail_to function. The job does log an error BUT it is not catched by the try/catch even though the ALL errors is set. Why are there some errors that the job files but are not catchable?
Thanks a lot & Best Regards
Isabelle

Answer 1

Thanks for sharing your experience. Indeed, the messages handling is not so obvious in Data Services.
2 other things I would like to point out:
- The Reference Documentation, it is mentioned under the Error Log section that If the error log is empty (that is, the button is dimmed), the job completed successfully. This doesn't seem true in fact. I have example where the job log is not empty and the job trace last statement is Job <job_name> is completed successfully. It is not clear what is the intend exactly.
- The Reference Documentation, also have a table of errors which has not relation with the catchable errors mentioned in Designer Documentation under section Categories of available exceptions. Yet, those 2 topics are related. Once again, it is not clear how the catchable exceptions are related to the error numbers.
Any hints to understand the concepts and usage is appreciated.