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.
I'm not sure even where to begin on this one...We can initially run the report fine with OLAP enabled but when we click the Run button, it immediately shows the following error:
0 ERROR AT OR NEAR LINE 66 IN PROCEDURE ADHOCRQ FOCEXEC *
(FOC303) CONTROL LINE NOT RECOGNIZED IN FOCEXEC:
-BOTTOM-STYLE=OUTSET,BORDER-LEFT-STYLE=OUTSET,BORDER-RIGHT-STYLE=OUTSET,BORDER-
Shane, you say "I'm not sure even where to begin on this one" and then you say "What else do I need to do to get this report working?" Did you try anything?
The error suggests (though it may not be) that a WebFOCUS Style Sheet declaration is the problem, so I would start by commenting out all the styling, and then start re-adding them, one declaration at a time until the error reappears. That's a beginning.
Regards,
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
Thanks Francis, I'll give that a shot...Maybe I'm just not up to speed on what all has to be done for OLAP to work...Do we have to tweak our master file definition for this to work too?
TABLE FILE GGSALES
SUM BUDUNITS UNITS BUDDOLLARS DOLLARS
BY CATEGORY
ON TABLE SUBHEAD
"</1 Sales Report"
"**CONFIDENTIAL**"
"December 2002 </1"
ON TABLE SET PAGE-NUM OFF
ON TABLE SET ONLINE-FMT HTML
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLESHEET *
TYPE=REPORT, GRID=OFF, $
TYPE=TABHEADING,
JUSTIFY=CENTER,
BORDER-TOP=HEAVY,
BORDER-BOTTOM=HEAVY,
BORDER-LEFT=HEAVY,
BORDER-RIGHT=HEAVY,
BORDER-TOP-STYLE=OUTSET,
BORDER-BOTTOM-STYLE=OUTSET,
BORDER-LEFT-STYLE=OUTSET,
BORDER-RIGHT-STYLE=OUTSET,
BORDER-TOP-COLOR=RGB(200 200 220),
BORDER-BOTTOM-COLOR=RGB(200 200 220),
BORDER-LEFT-COLOR=RGB(200 200 220),
BORDER-RIGHT-COLOR=RGB(200 200 220),
SIZE=12,
BACKCOLOR=RGB(220 220 240),
STYLE=BOLD,
$
ENDSTYLE
END
-EXIT
So, I know that OUTSET (3D in HTML only) is working.
As Francis suggests, comment out (-*) each API and see what happens.
Looking through the code, don't see any missing comma's or $ sign's.
The only difference is:
ON TABLE SET STYLESHEET * vs. your ON TABLE SET STYLE *
If I take out -OLAP ON, I don't get the dimensions at the top of the page...
I got OLAP to work with the CAR file...but it refuses to work with our production files...
-OLAP ON
-* File carolap.fex
OLAP DIMENSIONS
-* DIMENSIONS FILE CAR
COUNTRY: COUNTRY, CAR, MODEL, BODYTYPE;
END
TABLE FILE CAR
SUM
DEALER_COST
RETAIL_COST
SALES
BY BODYTYPE
ON TABLE SET PAGE-NUM OFF
ON TABLE NOTOTAL
ON TABLE PCHOLD FORMAT HTML
ON TABLE SET HTMLCSS ON
ON TABLE SET OLAPPANE TOP
END
So, I suppose I'll step line by line through both programs to see what the difference is...
BY PART_NUMBER AS 'Part Number'
BY ITEM_DESCRIPTION AS 'Description'
WHERE PLANT EQ '&PLANT';
WHERE DEPARTMENT EQ '&DEPT';
WHERE WORK_CENTER EQ '&WORKCENTER';
WHERE EFFECTIVE_DATE GE DT(20070904) AND EFFECTIVE_DATE LE DT(20070904);
WHERE ( PLANT NE 'N/A' ) AND ( DEPARTMENT NE 'N/A' ) AND ( WORK_CENTER NE 'N/A' ) AND ( PART_NUMBER NE 'N/A' ) AND ( MACHINE_GROUP NE 'N/A' );
Now, here's the weird part...in the source of the resulting page, OLAP apparently translates some WHERE clauses to IFs...as in the code below:
BY PART_NUMBER AS 'Part Number'
BY ITEM_DESCRIPTION AS 'Description'
IF PLANT EQ 'FLORA'
WHERE EFFECTIVE_DATE GE DT(20070904) AND EFFECTIVE_DATE LE DT(20070904)
WHERE (PLANT NE 'N/A') AND (DEPARTMENT NE 'N/A') AND (WORK_CENTER NE 'N/A') AND (PART_NUMBER NE 'N/A') AND (MACHINE_GROUP NE 'N/A')
What I tend to do is to try and remove complexity out of the OLAP phase by
APP HOLDDATA USERTEMP
APP HOLDMETA USERTEMP
-* complex code
ON TABLE HOLD AS RESULTSET FORMAT XFOCUS
END
-RUN
APP HOLDDATA
APP HOLDMETA
-RUN
-OLAP ON
TABLE FILE RESULTSET
-* simple query
I think the reason wf has translated your wheres to ifs is that it has parsed and deparsed your query and when it deparses it has used the older IF syntax instead of the WHERE syntax.
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
Read-Only Topic
