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 have e problem with a reporting procedure which is several thousand lines of code. The server crashes with "Unknown error occurred. Agent on reporting server EDASERVE may have crashed. Please investigate reporting server log.".
The problem is in the simple block:
TABLE FILE DB2_TPAESLING PRINT CODPAESE CODILING NOMPAESE BY CODPAESE NOPRINT BY CODILING NOPRINT ON TABLE HOLD AS DB2_TPAESLING_FIL END -RUN
I think the problem is that there are too many HOLD files (over 300) in the procedure. When I hold with a name that already exists there is no problem. Is there any limit to the number of HOLD files in one procedure? Has anyone had the same problem?
Thank you!This message has been edited. Last edited by: Kerry,
It could be a space problem and not the number of HOLD files. If you HOLD with a name that already exists, the file is replaced and space for two files is not used, but if you use different names, then space for each HOLD file is used.
Unless you're using a FILEDEF or APP HOLD command to redirect where the HOLD files are created, they're created in the WebFOCUS server temp area: C:\ibi\srv76\wfs\edatemp\ - in one of the WF agent folders ts000001, ts000002, etc.
Ensure there is adequate disk space on the server. You're accessing a DB2 database which suggests a mainframe system with huge tables.
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
The only time I have ever had that problem is when space was an issue. I have several batch procedures that use lots of hold files (never took the time to count how many).
I would also suggest that you CLEAR JOINS, DEFINE and FILEDEFs and delete files when they are no longer needed. You will save yourself a lot of headaches, especially if you are reusing names. For example:
DEFINE FILE HOLD CLEAR
END
-*
JOIN CLEAR *
-*
FILEDEF HOLD CLEAR
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
I have a very particular procedure for a client that uses multiple loops and compounds many reports into a single document and the expanded code is around 70,000 lines.
File systems have limits on the number of open files that they allow. In procedures that require very large numbers of temporary files, either close them, or delete them and reuse the name. The delete is important because if you do not and the particular step returns 0 records you will have major problems.
You should open a call with CSS to see if there is a limit.
Aside from that, I've had your error more times than I care to remember. Every time I got that error it was with procedures that were thousands of lines long. The reporting server would just seem to get lost on big requests, and became unable to display the appropriate error message. 9 times out of 10 that error turned out to be an unresolved ampher variable.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
Perhaps there aren't enough -RUN statements in the procedure with thousands of lines. I always put a -RUN statement after every FILEDEF, JOIN and END statement, to ensure the WebFOCUS code gets executed immediately and not after the whole program is parsed.
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 would agree with dhagen, open a case with support, they should be able to tell you why the agent crashed. could be file(s), could be a memory limit, could be for any number of reasons.
You have been given excellent advice from Dhagen, Francis, JG, jg, j.g. and Fortune Cookie. Might I add in my two cents so here goes: 1) Must you keep "ALL" the previous hold files around? Or can you do some cleanup before the point of failure? 2) Do youpossibly have 2 hold files with the same name? Meaning. One you let go to the default area, and one you have filedef'd to keep around in your own location? Could there be a conflict? (3) If you -EXIT prior to this snippet of code where the crash transpires - does the job exit cleanly? Hope this gives u some food for thought.
(4) If you put a limit on the very last request where this crash occurs - do you get the same result? If not, data issue?