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.
In an FML report, a RECAP is not calculated correctly when a datavalue is null in v7.6.5 - an incorrect number is displayed. This worked correctly in v5.3.4
SET COMPMISS = OFF seems to have saved the day.
I would like to know if anyone else had to code the COMPMISS setting, and is it safe to have this setting turned OFF for all reports.This message has been edited. Last edited by: Kerry,
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
This has to do with a behaviour change. In the past (v5.3.4) it appears that MISSING=ON was not added to the HOLD file Masters. Now in v7.6.5 it IS passed and this missing data causes incorrect calculations in FML RECAPs.
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
Where needed, you could always specify ON TABLE SET HOLDMISS OFF in the request that creates the hold file. That would bring back the old 534 behaviour in not saving missing values to the hold file. Or, of course as you already found out, the COMPMISS in the request with the recaps.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
In the past, when a new option was added, the default setting would be to NOT alter the behaviour, this setting by default alters WebFOCUS behaviour and results in incorrect report results. I'd understand if the report triggered an error, but actually producing incorrect results - that's just wrong.
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