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 could not reproduce your problem in WF 8.2.06. The global variables are both killed by the -INCLUDE program and does not show up in the calling program anymore.
I just used your example as posted so your code must have an additional -SET for &&LIMIT somewhere else.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005
-*-* Fex 11111.fex
-TYPE -*******************************************
-TYPE -** first fex
-TYPE -*******************************************
-SET &&VPDATNAI='OUI';
-SET &&LIMIT=1;
-TYPE Sent values to second fex
-TYPE VPDATNAI: &&VPDATNAI<--
-TYPE LIMIT: &&LIMIT<--
-TYPE -*******************************************
-TYPE -** second fex call
-TYPE -*******************************************
-INCLUDE IBFS:/WFC/Repository/IT/22222.fex
-TYPE Received values from second fex
-TYPE VPDATNAI: &&VPDATNAI<--
-TYPE LIMIT: &&LIMIT<--
-TYPE -*******************************************
-TYPE -** end first fex
-TYPE -*******************************************
-*-* Fex 22222.fex
-TYPE -*******************************************
-TYPE -** second fex
-TYPE -*******************************************
-TYPE Received values from first fex
-TYPE VPDATNAI: &&VPDATNAI<--
-TYPE LIMIT: &&LIMIT<--
-SET &&VPDATNAI='';
-SET &&LIMIT='';
-TYPE Sent values back to first fex
-TYPE VPDATNAI: &&VPDATNAI<--
-TYPE LIMIT: &&LIMIT<--
-TYPE -*******************************************
-TYPE -** end second fex
-TYPE -*******************************************
My result is the following
-*******************************************
-** first fex
-*******************************************
Sent values to second fex
VPDATNAI: OUI<--
LIMIT: 1<--
-*******************************************
-** second fex call
-*******************************************
-*******************************************
-** second fex
-*******************************************
Received values from first fex
VPDATNAI: OUI<--
LIMIT: 1<--
Sent values back to first fex
VPDATNAI: <--
LIMIT: <--
-*******************************************
-** end second fex
-*******************************************
Received values from second fex
VPDATNAI: <--
LIMIT: <--
-*******************************************
-** end first fex
-*******************************************
Also, please update your signature to let us know which version of WF you are running
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
Thks a lot for your help In fact the pb is that i use an -EXIT in the 2nd FEX, and so the global variables are not killed as i would. So i m going to try to modify my fex to fix this pb.