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 was told recently that I can create procedures such as long, complex Defines in a separate procedure, and then call that procedure by putting EX Subroutine Name. However, it does not seem to be recognizing the subroutines. Can this be done?
I believe with a complex define as you want, you need to do a '-include' in your code
a.fex define..... .. end
b.fex -include a table... ... end Or if you need concrete a.fex is DEFINE FILE CAR MODELA/A20 = MODEL; END
b.FEX -include a TABLE FILE CAR PRINT MODEL MODELA END What you are including has to be in the application path or library concatenation depending on if you are mainframe versus web for storing fex.
Posts: 1317 | Location: Council Bluffs, IA | Registered: May 24, 2004
Thanks for the response. I've found that both -Include and EX work, but only for one subroutine. I can call one subroutine, the first one, but it ignores the others.
The thing is that they are all Defines, and because they are such long, complex Defines, and the fact that I want to use them in other reports, it seemed better to save them separately. One of the problems seems to be that the only way I could get even one subroutine call to work is that I had to put the Define File Filename...procedure...End in each separate subroutine. Is there a way to call multiple subroutines? That part didn't work for me with either -Include or EX.
Two approaches: - - - (a) Omit the DEFINE and END lines from the includes, and keep them in the reporting focexec:
DEFINE FILE XXX -INCLUDE mydefs1 -INCLUDE mydefs2 -INCLUDE mydefs3 END
(b) Use the ADD option: In each of your Define focexecs put: -DEFAULT &OPTION=' ' DEFINE FILE xxx &OPTION ... END And in your report fex: EX mydef1 EX mydef2 OPTION=ADD EX mydef3 OPTION=ADD (DEFINE with no option, or with the CLEAR option, cancels any prior Defines for that filename (which was your problem), while ADD appends to the existing list.) - - -
Either way, the net effect achieved is that the sets of defines are activated, in the desired order.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005