As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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>,
- FOCUS Man, just FOCUS! ----------------------------- Product: WebFOCUS Version: 8.1.04 Server: Windows 2008 Server
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
- FOCUS Man, just FOCUS! ----------------------------- Product: WebFOCUS Version: 8.1.04 Server: Windows 2008 Server