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     Warning EX and EXEC work differently in MRE

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Warning EX and EXEC work differently in MRE
 Login/Join
 
hammo1j
Master
posted
http://documentation.informationbuilders.com/masterinde...39.htm#d05stp1027711

In the above documentation for use of EXEC command to execute a .FEX it states

quote:

Syntax: How to Pass Keyword Parameters
EX[EC] procedurename=value[,...]
EX SLRPT AREA=S,CITY=STAMFORD,VERB=COUNT,
FIELDS=UNIT_SOLD,CODE1=B10,CODE2=B20



This suggests that EX and EXEC are one and the same thing. However examining the effect under MRE I have discovered

EX FEXNAME works like

-INCLUDE FEXNAME

In that it tries to resolve the reference to FEXNAME with the MRE domain and then it will pass both files (the caller and executed fex) to the server for execution.


EXEC FEXNAME is analogous to

-MRENOEDIT BEGIN
-INCLUDE FEXNAME
-MRENOEDIT END

In that FEXNAME is resolved on the SERVER and must exist within the application path.

IBI docs team it would be worthwhile updating the documentation as this is a reasonably important distinction and can be very confusing!


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, 2006Report This Post
Susan Trommer
Member
posted Hide Post
Thank you for catching and letting us know. I have informed the WebFOCUS documentation services manager so the correction will be made.
This information is documented in the Managed Reporting Developer Guides. In Rel 761 manual it is in Chapter 2 on pg. 77. Actual doc is:

–INCLUDE and EX statements coded in a procedure are processed by the WebFOCUS Client,
which looks for the procedure in the Managed Reporting repository. Procedures that are
referenced with an EXEC statement are not processed by the WebFOCUS Client, they are
only passed to the WebFOCUS Reporting Server for processing therefore these procedures
are not looked for in the Managed Reporting repository.
Thanks again...


Susan Trommer
Information Builders
 
Posts: 28 | Registered: May 22, 2003Report This Post
Rob Bowen
Member
posted Hide Post
I'ts been like this since I first started working with WebFOCUS 3.5. I seem to recall I first found out about the EXEC from the manual back then (before I knew about -MRNOEDIT).


WebFOCUS 8.1.04; SQL Server 2012; Windows 7; Windows Server 2012 R2;
 
Posts: 26 | Registered: November 21, 2005Report This Post
hammo1j
Master
posted Hide Post
Thanks very much, Susan, for showing you care about us users!


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, 2006Report This Post
JoJo
Member
posted Hide Post
The Developing Reporting Applications manual was updated (in two Syntax topics where EX[EC]
is used) with the following note:
Note: When EXEC is used in Managed Reporting, it is important to note that there is a difference between EX and EXEC. EX statements coded in a procedure are processed by the WebFOCUS Client, which looks for the procedure in the Managed Reporting repository. Procedures that are referenced with an EXEC statement are not processed by the WebFOCUS Client, they are only passed to the WebFOCUS Reporting Server for processing, and these procedures are not looked for in the Managed Reporting repository.

We also added a Note to the other
WebFOCUS manual locations where EX[EC] is documented.

Thanks for the feedback.
 
Posts: 1 | Registered: November 18, 2005Report This Post
susannah
Expert
posted Hide Post
Thank you JoJo
but what is needed, as always, is an EXAMPLE of the coding differences, in use. The impact.
As John has given us. (Thanks John.)
Otherwise the distinction just melds into the gibberish.
Whats significant to the coder may not be where they execute, but that one is self contained and one is not, having impact on use of statement labels, &vars, etc, between host fex and guest fex.



In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report 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     Warning EX and EXEC work differently in MRE

Copyright © 1996-2020 Information Builders