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     OLAP sorting causes (FOC262) UNBALANCED PARENTHESES

Read-Only Read-Only Topic
Go
Search
Notify
Tools
OLAP sorting causes (FOC262) UNBALANCED PARENTHESES
 Login/Join
 
Jason K.
Master
posted
We have a report that we have enabled olap *tabbed* on. When a user goes to sort it or unhide a column (do anything at all in OLAP actually) they get an error of

0 ERROR AT OR NEAR LINE 198 IN PROCEDURE ADHOCRQ FOCEXEC *
(FOC262) UNBALANCED PARENTHESES
(FOC009) INCOMPLETE REQUEST STATEMENT
BYPASSING TO END OF COMMAND

there's nothing special about line 198. It's just a BY encased in some DM code.

Additionally, we have
-SET TRACEON=ALL;
-SET TRACEUSER=ON;
-SET &ECHO=ALL;
-SET &ECHO=ON;
at the top of this fex, but it doesn't echo the code like usual. We're guessing that this has something to do with OLAP.

Thanks!


Prod: Single Windows 2008 Server running Webfocus 7.7.03 Reporting server Web server IIS6/Tomcat, AS400 DB2 database.
 
Posts: 611 | Registered: January 04, 2007Report This Post
Alan B
Virtuoso
posted Hide Post
Jason

The times I came across this error was with a COMPUTE in the OLAP code.

Is this the case?


Alan.
WF 7.705/8.007
 
Posts: 1451 | Location: Portugal | Registered: February 07, 2007Report This Post
Jason K.
Master
posted Hide Post
Alan, YES!

actually here's of the fact (SUM) fields, we have 17 of the 20 that are COMPUTES.

Is there any way to have the computes without this error?

This message has been edited. Last edited by: Jason K.,


Prod: Single Windows 2008 Server running Webfocus 7.7.03 Reporting server Web server IIS6/Tomcat, AS400 DB2 database.
 
Posts: 611 | Registered: January 04, 2007Report This Post
Alan B
Virtuoso
posted Hide Post
This is one of a few known(!) issue with OLAP COMPUTES, that may be the issue.

If the final parenthesis is just prior to the semi colon, it is removed by the OLAP parser.

So COMPUTE X/F4 = 100*(3+4); would fail, but
COMPUTE X/F4 = (100*(3+4))*1; should work.

The other main issues are a -ve sign causing issues (though not all the time) in a logic based COMPUTE, and that a COMPUTE can only use EQ or NE in a logic expression. Both of these have WARs also.

On a positive note we have had over 500 complex COMPUTES in an OLAP without error with the WARs in place. (The 'we' includes John Gray, Jim Fraser and Manuel Gonzales who all contributed to getting this to work).


Alan.
WF 7.705/8.007
 
Posts: 1451 | Location: Portugal | Registered: February 07, 2007Report This Post
Jason K.
Master
posted Hide Post
I did not know that.
thanks!


Prod: Single Windows 2008 Server running Webfocus 7.7.03 Reporting server Web server IIS6/Tomcat, AS400 DB2 database.
 
Posts: 611 | Registered: January 04, 2007Report 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     OLAP sorting causes (FOC262) UNBALANCED PARENTHESES

Copyright © 1996-2020 Information Builders