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.
There are no restrictions on the source file. The lookup file can be any non-FOCUS data source that is supported as the cross referenced file in a cluster join. The lookup fields used to find the matching record are subject to the rules regarding cross-referenced join fields for the lookup data source. A fixed format sequential file can be the lookup file if it is sorted in the same order as the source file.
- Documentation.
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
Just to clarify ... The file you are defining is the HOLD file. The table you are using for the DB_LOOKUP can be a SQL Server table.
TABLE FILE PASSED_BINNED
SUM
PASSED
TAGS
PASSED_TAGS
DETECTED_TAGS
PPT_TAGS_REMAINING
BY SPECIES_RELEASE
BY RELEASE
BY REL_RELEASEDATETIME AS 'RELEASEDATETIME'
BY YEAR
BY SYSTEM
BY LD_TYPE
BY UNIT
BY JULDAY
BY HOUR
BY QUARTER_HOUR
BY HOURS
ON TABLE HOLD AS ALMOST_THERE
END
-RUN
DEFINE FILE ALMOST_THERE
FLOW/D14.6 MISSING ON = DB_LOOKUP(OPS_HOLD_ALL,YEAR,OPS_YEAR,SYSTEM,OPS_SYSTEM,LD_TYPE,OPS_TYPE,UNIT,OPS_UNIT,JULDAY,OPS_JULDAY,HOUR,OPS_HOUR,QUARTER_HOUR,OPS_QUARTER_HOUR,OPS_VALUE );
...
The closer you can match the sort order (or index) of the two tables, the better. OPS_HOLD_ALL is a SQL Server table with dam flows taken every fifteen minutes for six years and FLOWs are returned with no noticeable lag.
Posts: 60 | Location: Ellensburg Washington | Registered: May 22, 2009