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.
SO we have a application where developers pushed lots of fexes to prod with the dreading line ECHO=ALL; I'm wondering is there a global setting to turn it off? Unfortunately its a line in every fex inside each reportcaster job (over 100 or so). Definitely a bad idea to have that in prod but, I figured I'll ask here if any of you guys handled it differently?
Thanks in advance.This message has been edited. Last edited by: vaayu,
If you set the ECHO to NONE as a pre-process, that will prevent procedure code from being displayed (echoed). Once the value of &ECHO has been set to NONE, it cannot be changed during the session or connection.
Hallway
Prod: 8202M1
Test: 8202M4
Repository:
OS:
Outputs:
Posts: 608 | Location: Salt Lake City, UT, USA | Registered: November 18, 2015
Thank you Hallway, that seemed to have worked for what we're doing. Appreciate your help!!
quote:
Originally posted by Hallway: Check out theses docs
If you set the ECHO to NONE as a pre-process, that will prevent procedure code from being displayed (echoed). Once the value of &ECHO has been set to NONE, it cannot be changed during the session or connection.
Originally posted by Waz: Wow, need to read the documentation more often.....
I actually found the ECHO setting by helper fex that I have that reports all of the available SETs and their current/available values.
TABLE FILE sysset
PRINT
VALUE AS 'Available,Values'
SETMAXLEN AS 'Max,Length/,Value'
SETFPROMPT AS 'From,PROMPT'
SETFTAB AS 'From,TABLE'
SETFPARMS AS 'From,PARAMS'
VALDESC
IS_DEFAULT
BY SETNAME
BY SETDESC
BY SERVDESC
BY SETVALTYPE
BY CURR_VALUE
WHERE SETNAME EQ &SETNAME.(OR(FIND SETNAME IN sysset |FORMAT=A64)).Select SET value.;
ON TABLE SET PAGE-NUM OFF
ON TABLE SET STYLE *
INCLUDE=IBFS:/FILE/IBI_HTML_DIR/ibi_themes/flat.sty,$
TYPE=REPORT, LINES-PER-PAGE=UNLIMITED, TITLETEXT='WebFOCUS Sets', $
ENDSTYLE
END