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.
The first issue you may have debug (ie. -SET &ECHO=ALL or tracing can be on...etc) on so you may hit the limit in your test box. It may be that the limit is set lower compared to your PROD box. The default is set to 20000 lines for IBIF_max_messages. If you want it to be unlimited, set it to zero.
The second issue is more vague, it could be something like missing double quotes in code, join statements not cleared, ...etc (at least those were the ones that I've encountered, of course there are definitely more).
Lalita, even though the programs and masters are the same, it doesn't mean that the data is. You may be pointing to dev, trial, and prod versions of data. IBIF_max_messages oftentimes means that the focexec is having trouble handling the data that comes in and throws an error for each record that fails until it reaches the threshold and fails. The easiest way to diagnose this problem is to put a recordlimit in the program, very small, so that you don't crash and can see the error. Once you know what the error is, you can attempt to fix it.
That is how I would start to diagnose the problem. Please post your results of this exercise.
You can't fix the problem until you know what it is. Have you tried running a trace, server-side? You might have to go through a lot of text before you find the error message but once you find it, you'll know what you have to fix. Give it a shot.
Not sure if this might be the issue with your case, but quite a few times I had encountered Max messages error because of having multilple Label names for a GOTO stmt. WF parser would look for a single Label for a GOTO but if you have multiple Labels then this error would pop up. Just check on it.
thanks Sashanka
WF 7.7.03/Windows/HTML,PDF,EXL POC/local Dev Studio 7.7.03 & 7.6.11
IBIF_max_messages is defined in the WebFOCUS Client Console under Configuration/Client Settings/General, near the bottom. You must be an admin to change this.
For this particular issue, I wouldn't raise it. I'd lower it so that the termination happened much more quickly and turn on client and server traces. You cannot solve this problem until you know what the error is, especially if you've ruled out the other suggested causes in this thread. My experience is that these are often data problems.