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.
If that day comes many reporting environments will no doubtedly stop working and not only because of &ECHO but because of the fact that Dialog Manager treats "almost" anything as an alphanumeric value (even if not quoted) unless it looks like a number or is a reserved word.
Though I prefer using:
-IF &COUNTRY EQ 'ENGLAND' THEN ....
It's perfectly valid to say:
-IF &COUNTRY EQ ENGLAND THEN ....
I might have fallen on the latter a few times so hopefully that day won't come ...
I think we would need someone from the programming division to answer this, as at what stage in the interpreting of the code does the test for the contents of the &ECHO variable start. I would have thought that it would be after the eval of the string to assign the variable, but I guess we will probably never know.
&ECHO has been around forever, but if IBI had it to do over again, I would hope ECHO would join the ranks of the SET commands. SET is used to modify the environment and -SET is used to establish values for Dialogue Manager variables. SET specifies options, -SET specifies values. ECHO should be one of the former, not one of the latter. IBI had more time to consider the relatively new DMPRECISION command, which modifies the precision of Dialogue Manager numeric values. DMPRECISION is SET, not -SET. The proper syntax for ECHO should be SET ECHO = {ON/OFF/ALL/NONE}.This message has been edited. Last edited by: Dan Satchell,
WebFOCUS 7.7.05
Posts: 1213 | Location: Seattle, Washington - USA | Registered: October 22, 2007
SET is used to modify the environment and -SET is used to establish values for Dialogue Manager variables. SET specifies options, -SET specifies values. ECHO should be one of the former, not one of the latter.
Well, maybe. However, -SET &ECHO = {whatever} displays the code and is needed to evaluate the flow of the code (in View Source, etc). So, it it really environmental in nature, or DM?
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005