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.
-------------------------------------------------------- UPDATE: SOLUTION AT END OF THREAD (February 11, 2005 11:24 AM) -------------------------------------------------------- Has anyone heard of this one? Fexes run from file utilities, but won't run deferred with the following message: 0 ERROR AT OR NEAR LINE 6 IN PROCEDURE THISFEX FOCEXEC * (FOC36249) RECURSIVE -INCLUDE OVERFLOW DETECTED No processing messages are displayed before this message when the deferred job terminates. It seems to happen even with the simplest fexes. Thanks in advance. JSouth
(FOC36249) RECURSIVE -INCLUDE OVERFLOW DETECTED The -INCLUDE dialogue manager directive may not include the same file recursively more than a limited number of times (either directly or indirectly).
Let me speculate:
I believe this msg really means that the depth of nesting of -INCLUDE statements has been exceeded, regardless of whether recursiveness is involved or not.
The nesting level limit used to be 4 (with recursive -includes supported, provided they are self-limiting), but has been raised in recent Focus and WF releases (7.x, 5.x) to an unspecified but much higher number.
With the (unspecified) present high limit, the most likely source of violation of the high limit would be recursiveness gone wild, hence they renumbered and reworded the message.
So: Perhaps deferred processing (read: RCaster) has not caught up, and still has 4 levels as the limit (among other unimplemented Focus features).
That would explain the difference in behavior, and the close-but-not-quite-appropriate nature of the error message.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
Thanks for replying Jack. You'd think it would have something to do with includes, but here is the simple fex I've been working with to try to figure this out. -TYPE "NORTHNONE WAS HERE" -RUN This two-line fex is called 'TYPOUT' Here is Custom Report setup. -* Edit Tool -MRNOEDIT BEGIN -INCLUDE TYPOUT -MRNOEDIT END -RUN
The deferred report was the same name as the fex it was including, hence the recursive error. Renamed the fex to another name and all was well. Hope this helps someone else, because it was a bear to figure out.