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

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.

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.

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!

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.

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.