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 different outputs when running the file below:
TABLE FILE F3112 SUM FST.WLSTRT/MDYY LST.WLDRQJ/MDYY COMPUTE DAYS_LEFT/D12.2 = LST.WLDRQJ - FST.WLSTRT; BY WLDOCO WHERE (F3112.F3112.WLMMCU EQ ' 4333') AND (F3112.F3112.WLDOCO EQ 550595) AND (F3112.F3112.WLOPSC_CODE NE 'T') AND (F3112.F3112.WLOPST_CODE NE '20');
Output is correct: Order FST Start Date LST Request Date DAYS_LEFT 550595 10/11/2016 12/01/2016 51.00
Removed (F3112.F3112.WLDOCO EQ 550595)from the above file.
Output is not correct:
Order FST Start Date LST Request Date DAYS_LEFT 550595 10/11/2016 11/29/2016 49.00
The output of the LST Request Date is not correct when removing and running all of WLDOCO. It should be 12/01/2016.
Any input is appreciated as to why the output is not the same when removing the WLDOCO.This message has been edited. Last edited by: <Kathryn Henning>,
When you specify a single value for WLDOCO the records don't need to be sorted once retrieved into the WF internal matrix. Without the filter on WLDOCO the records do need to be sorted after retrieval. By happenstance the records for 550595 are not sorted in the same order in both cases. So the LST operator selects a different last record in each case. Would using the MIN operator instead of FST, and MAX instead of LST give you the correct data?
The other advantage to MIN and MAX is they can be passed to SQL (if a relational DB is your data source). SQL doesn't have FST and LST, so WF cannot pass those operators and must therefore retrieve all records in order to make that determination in the summary output. With MIN and MAX SQL can perform the summary/aggregation, which will improve query performance significantly as the number of records being retrieved increases.This message has been edited. Last edited by: Dan Satchell,
WebFOCUS 7.7.05
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
TABLE FILE F3112 SUM MIN.WLSTRT/MDYY MAX.WLDRQJ/MDYY COMPUTE DAYS_LEFT/D12.2 = MAX.WLDRQJ - MIN.WLSTRT; BY WLDOCO WHERE (F3112.F3112.WLMMCU EQ ' 4333') AND (F3112.F3112.WLDOCO EQ 550595) AND (F3112.F3112.WLOPSC_CODE NE 'T') AND (F3112.F3112.WLOPST_CODE NE '20');
Output is not correct:
Order MIN Start Date Max Request Date DAYS_LEFT 550595 10/5/1901 10/5/1901 0.00
Should be:
Order MIN Start Date Max Request Date DAYS_LEFT 550595 10/11/2016 12/01/2016 51.00
Are WLSTRT and WLDRQJ DEFINEd fields? Are the real fields date-time values?
What do you get when you run this:
TABLE FILE F3112
SUM
FST.WLSTRT/MDYY
MIN.WLSTRT/MDYY
LST.WLDRQJ/MDYY
MAX.WLDRQJ/MDYY
COMPUTE DAYS_LEFT1/D12.2 = LST.WLDRQJ - FST.WLSTRT;
COMPUTE DAYS_LEFT2/D12.2 = MAX.WLDRQJ - MIN.WLSTRT;
BY WLDOCO
WHERE (F3112.F3112.WLMMCU EQ ' 4333')
AND (F3112.F3112.WLDOCO EQ 550595)
AND (F3112.F3112.WLOPSC_CODE NE 'T')
AND (F3112.F3112.WLOPST_CODE NE '20');
WebFOCUS 7.7.05
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
It seems to me that your file has multiple fields named WLDRQJ in it. Removing the WHERE-clause changes the order in which those fields are found and you're reading a different field than you were with the WHERE-clause.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :