Tom,

I think that the best way to handle the specialization of
errors under "arithmetic exception" is with secondary codes -
that's why they exist. We would still raise the same primary
code, but add secondary codes indication whether the actual
error was string truncation (and possibly passing the string)
etc.


Regards,


Ann