Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Debugging paradigm/techiniques

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Debugging paradigm/techiniques
 Login/Join
 
<abroit>
posted
I am returning to Focus...ok, WebFocus...now.

Previously, you could set ECHO=ON and use dialogue manager variables to debug.

What is the new paradigm?

How do you debug and follow the course of execution?

TIA
 
Report This Post
dhagen
Virtuoso
posted Hide Post
The same thing still applies in WebFOCUS. You can use -SET &ECHO=ON|ALL|OFF; to control the presentation of the "Focus" code. The code will be sent to the browser. If a report is delivered in HTML format, then do a "View/Source" to see the echo'd code. This will not work if the final report is pdf or excel.
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report This Post
susannah
Expert
posted Hide Post
ab, another technique you can use in web is
CMD NET SEND yourdesktopname SOME TEXT MESSAGE
this will send a message in an alert box to your desktop, useful during the middle of a long fex, to give you progress reports.
CMD NET SEND mymachinename You've read &LINES
for example.
Your Echo file isn't available to you until the fex finishes, then you have the entire thing available with a right-click-view-source.
CMD NET SEND..works in a windows server env if your it folks have messaging enabled, i don't know about any other.
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Carol Dobson
Guru
posted Hide Post
After adding the

-SET &ECHO=ALL;

I replace my uutput statment
ON TABLE SET ONLINE-FMT PDF or whatever

to

ON TABLE HOLD

Then the whole trace is available to you.
Makes debugging easy!
 
Posts: 428 | Location: Springfield, MA | Registered: May 07, 2003Report This Post
N.Selph
Guru
posted Hide Post
I've never run into the CMD NET SEND syntax before? In what environment/machine does it run? When I try it I get:
/sbin/sh: NET: not found.
 
Posts: 391 | Location: California | Registered: April 14, 2003Report This Post
susannah
Expert
posted Hide Post
CMD is an updated version of the DOS command
We have a win2k server in a windows xp environment on a cisco network.and this syntax has run from win436 upwards.
In some env, DOS NET SEND machinename message
works.
It requires messaging be set on. ask your network guys. i'm out of my depth there.
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Debugging paradigm/techiniques

Copyright © 1996-2020 Information Builders