I found a posting, that Francis posted an example of capturing the error number and getting the error message, which works great, but is there any way to capture the rest of the information that is normally displayed if there isn't a catch?

Mainly, we would like to see the line Number that the error occurred on.

This message has been edited. Last edited by: <Kathryn Henning>,

We would all love to see the line number - in 2015 there is no method I know of to capture the line number of the error.

Does the TRACE method get the error message with the line number ?

Can automate/capture that, so I can put it in a log?

I'm attempting to create a generic error catch fex, that I can use through out custom fex files. We have a lot of Web Services for example that are called and if they are down, errors are thrown on the screen. We can create generic error pages, but I'm trying to take this to the next level and log where the errors are coming from, what line, etc. You know, like every other language on the planet. Even if there's not a conventional means of doing so, I'm going to make it work, but attempting to make this as simple as I can for those who have to implement it, including myself.

So far this is what I have to put behind each thing I want to trap.

-SET &ERRNUM = &FOCERRNUM;
-*From the reporting server, you have to use the short folder name.
EX err/err_check PROC='&FOCFEXNAME.EVAL', DESC='JUST READ CAR TABLE', ERRNUM=&ERRNUM, USERINFO=&IBIMR_user
-*From the client Content, you must specify the full path.
-*EX IBFS:/EDA/EDASERVE/err/err_check PROC='&FOCFEXNAME.EVAL', DESC='JUST READ CAR TABLE', ERRNUM=&ERRNUM, USERINFO=&IBIMR_user