Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED]Where-based Join from non-focus to focus

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED]Where-based Join from non-focus to focus
 Login/Join
 
Gold member
posted
I have a report which I developed in our Dev environment running 8104 and tried to move it over to Production environment which is currently on 8009 and it does not run. It is giving me an error of "(FOC36316) WHERE-BASED JOIN FROM NON-FOCUS TO FOCUS NOT SUPPORTED."

The report runs perfectly fine in Dev. Was there support added after 8009 to allow this Join to function properly or is there some setting that might not be set right in Production? Has anyone else ran into this before? I've verified that the data source it is trying to link to is available in Prod as well.

Here's the bit of code that it seems to be hung up on, which is indeed joining from a SQL table to a FOCUS.
JOIN
 LEFT_OUTER FILE vwloanservcustomertask
 AT VWLOANSERVCUSTOMERTASK.VWLOANSERVCUSTOMERTASK.TASKNUMBER TO MULTIPLE
 FILE foclossdraftbranchcodes AT FOCLOSSDRAFTBRANCHCODES.SEG01.CIT TAG J4 AS J4
 WHERE ( VWLOANSERVCUSTOMERTASK.VWLOANSERVCUSTOMERTASK.TASKNUMBER EQ J4.SEG01.CIT ) AND ( VWLOANSERVCUSTOMERTASK.VWLOANSERVCUSTOMERTASK.SERVICINGBRANCH EQ J4.SEG01.SERVBRANCH );
 END


Thanks

This message has been edited. Last edited by: capples,


WF 8.2.0.3
Windows 10 64bit
HTML, AHTML, PDF, Excel
 
Posts: 83 | Registered: April 13, 2015Report This Post
Guru
posted Hide Post
could you verify if by accident there is a non-FOCUS file on production in some app directory or foccache called vwloanservcustomertask?


Test: WF 8.2
Prod: WF 8.2
DB: Progress, REST, IBM UniVerse/UniData, SQLServer, MySQL, PostgreSQL, Oracle, Greenplum, Athena.
 
Posts: 454 | Location: Europe | Registered: February 05, 2007Report This Post
Virtuoso
posted Hide Post
quote:
FOC36316

Apparently such a join was not yet supported in your earlier 8.x release.

Solution is to defer the join: omit the JOIN in the table request against the database table (vwloanservcustomertask), HOLD the result in Format Focus (or Xfocus), and then join the held Focus file to foclossdraftbranchcodes.foc.

Note that, by the nature of the data sources, the join you coded would not be passed through to the database server, so postponing the Join to the reporting step makes little difference in execution efficiency.
 
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED]Where-based Join from non-focus to focus

Copyright © 1996-2020 Information Builders