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.
Sounds like flat files, with only one NY record in the second (joined-to) file.
If it's a join to a FIX file, the result is correct for a one-to-many JOIN
In a one-to-many join to a flat file, if there were several matching records in the second file they would all be coupled to the first NY record in the first file, and for subsequent NY records in the first file the cupboard would be bare (since the process does not backspace the second file).
Procedurally, Focus reads forward in the second file, after the first match, until it encounters a non-NY keyed record. It then sits on that record waiting for a record in the first file that matches it.
So any additional NY records in the first file would show no match, whether the second file contains zero, one, or several records keyed to NY.
Bottom line: Remove "ALL" from the JOIN.
- Jack Gross WF through 8.1.05
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005