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 firstname.lastname@example.org for further assistance. Reference the community FAQ to learn more about the community.
The SET MULTIPATH=SIMPLE is supposed to give you the oppurtunity to screen on independent sets of data. It seems to work with Focus db, but when trying to implement it on DB2, it fails to return short paths. We can get the desired results with SET ALL=ON, but the response time is not acceptable. Anybody has any idea? We're on WF 5.2.7 on IBM iSeries.
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004
When FOCUS/DB2 performance gets too long. My first guess is FOCUS is doing the joins instead of having DB2 do the join. When This happens FOCUS often retrieves the entire contains of the DB2 tables.
Generally the quickest way to solve the problem is the SQL pass thought and extract just the data need from each table. The answer sets becomes hold files, and you can either join the hold files or use MATCH FILE.
You might might be able to avoid the MATCH/JOIN using a DB2 Outer Join in the SQL. But, these can take a long time to run.
Another approach is to have the DB2 performance guru review the SQL query generated by FOCUS. Then you try to figure out how to change the TABLE FILE to meet their recommendations.