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.
Does anyone know of a reason why anyone would want to have a procedure "EX" another procedure (as opposed to just using an "INCLUDE")? We have a common place where we keep our global and local variables, however, it looks like we only use the "EX" command when calling a stored procedure (where in this case we feed the procedure parms). We're looking to upgrade from 5.3.3 to 7.1.6, and one thing we've noticed is that global variables pop up under the advanced tab in ReportCaster in 7.1.6, whereas it didn't in 5.3.3, so I'm thinking we really don't have a need for global variables. I am fairly new with WebFOCUS, so if someone could give me some insight on this, I would greatly appreciate it. Thanks!
------------------------------------------------------ WebFocus 7.1.6 Web Server: resides on MS IIS with Tomcat plug-ins on Windows 2003 SPI SQL database: Informix Client-SDK Version 2.70 IE version 6.0
henry the principal reason is the concept of 'self -containment'; -INCLUDE isn't self contained. A -INCLUDE is code brought in to the fex before it begins to run. So, for example, in a batch job where the same fex might be run multiple times with different sets of parms, any GOTO statements or statement labels would be repeated, and unresolved infinite looping would occur. As far as the self-contained bit goes, theres a gigantic difference between EX and EXEC and it all depends on the version you're on.; The && variables in Caster v7, now being requested, are a huge nuisance, i agree with you, there is a work around to get caster to not require values for those parms. But it gives you no confidence that caster will in fact pay attn to the parm values you actually DO need to provide.
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
The main difference between EX and -INCLUDE is that you are given a new private space to code your amper variables - you cannot read or modify the variables of the calling procedure. (Like fortran subroutines for anyone who remembers). It is a stack like representation in that once you exit the EX'ed proc the previous amper environment is re-established for the original proc.
The global variables are shared at all levels of EX nesting.
susannah
I have a feeling that there is not a problem with label duplication within a fex that -INCLUDES another fex with the same label because I think wf internally prefixes the label with the include name to avoid what would be a very common problem.
John
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
I actually opened up a case prior to posting in the forums (30032538). I described the same concerns you had mentioned susannah. That answered my question, thanks!
------------------------------------------------------ WebFocus 7.1.6 Web Server: resides on MS IIS with Tomcat plug-ins on Windows 2003 SPI SQL database: Informix Client-SDK Version 2.70 IE version 6.0