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.
New TIBCO Community Coming Soon
In early summer, TIBCO plans to launch a new community—with a new user experience, enhanced search, and expanded capabilities for member engagement with answers and discussions! In advance of that, the current myibi community will be retired on April 30. We will continue to provide updates here on both the retirement of myibi and the new community launch.
What You Need to Know about Our New Community
We value the wealth of knowledge and engagement shared by community members and hope the new community will continue cultivating networking, knowledge sharing, and discussion.
During the transition period, from April 20th until the new community is launched this summer, myibi users should access the TIBCO WebFOCUS page to engage.
Is there any new documentation or tips/tricks on Error Handling? I searched but didnt see anything new.
I know how to display the error when it occurs but I also want to display the line number or let me know the TABLE FILE or HOLD FILE the error occured in.
Is this possible?
Thanks, prodriguThis message has been edited. Last edited by: <Kathryn Henning>,
I would suggest a workaround of setting a string at each error test detailing what is needed, e.g. line number and master or a description of what was being done at that step.
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).
quote:
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.
Francis
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
I got it to work with the below code. All I needed to do it SET TEMPERASE=OFF.
SET TEMPERASE=OFF
-SET &TEMPPATH=TEMPPATH(80,'A80');
-TYPE &TEMPPATH
FILEDEF EMGFILE DISK EMGFILE.DAT
-RUN
SET EMGSRV=FILE
TABLE FILE CAR
PRINC CAR
END
-RUN
Hi Prodrigu, Instead of setting TEMPERASE=OFF, just FILEDEF the output file to a specific loaction. ie. FILEDEF EMGFILE DISK C:\ibi\apps\data\EMGFILE.DAT Regards, Ian
_______________________ *** WebFOCUS 8.1.05M ***
Posts: 196 | Location: London, UK | Registered: December 06, 2005