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 firstname.lastname@example.org for further assistance. Reference the community FAQ to learn more about the community.
I already have a -INLCUDE file to check for errors and no records return but I wanted to see if I can what line (which you said not possible) and display the current hold file the error occurred. I have this INCLUDE file after each HOLD file.
Do you have an example of error handling you can show me maybe you worked on before?
Right now we dont have error handling and I am trying to implement it since we are moving 3/4 of our reports to go against Netezza DB.
The documentation for EMGSRV is in "WebFOCUS New Features 8.0.08" (80snf.pdf).
Capturing Event Routing for Specific FOCUS Error Conditions
You can now use the EMGSRV profile command to capture event routing for specific FOCUS error conditions. The EDAPRINT/ON value enables you to use existing server event routing facilities to create custom filters that trigger email alerts and/or procedure execution for enduser events that would not normally be routed to the edaprint log.
Hmmm... The "FILE" option is not documented there.
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server