PRINT "@TTY = ":@TTY FOO = 1 DEBUG PRINT "ALL DONE"
I save it (using the UniObjects option) and select Tools | Compile. I fill in my password and the login script runs:
- unix username/password login - exit script menu to unix prompt - stop dual session - start UniData login script - SB username/password login, select Wyse60 terminal type, etc. - drop to : prompt per your suggestion
The terminal window shows everything working fine. Pressing F8 once works perfectly -- the yellow arrow points to the first line, the terminal window shows the SETDEBUGLINE and RUN commnads. Pressing F8 again, the output from the first print statement shows but the yellow arrow in the editor disappears. Continuing to press F8 does nothing, however if I switch to Show Dual Session, press Enter, switch back, press F8, switch to Dual Session again, and press Enter again, something unclogs and the debugger commands that hadn't executed before suddenly run ($ and a \FOO for my watch) and the yellow arrow reappears.
If I leave the Dual Session up, things continue to work (F8 moves the yellow arrow, etc.). When I press F5 to let the program run (after stepping thru the DEBUG statement) the dual session shows up at line 1 again in debug mode. I can manually type E to finish running the program, but I don't know why it ran again. I can flip back to the regular session and see what was output.
Doesn't sound right to me. Is there something I need to do in Dynamic Connect's settings?
Thanks, David Beahm
[EMAIL PROTECTED] wrote:
I don't use the dual session - it seems a little redundant.
To do this I change the view to host (so I can see the screen) and hit connect. That gives me the login prompt and I login (don't use a GUI terminal type) and from the menu I enter '0' to get to the UniData TCL prompt (:).
If you run <F5> the program it will only go into the debugger if you have a debug statement in the code. You can do an <F8> to 'step into' the code. Each <F8> will execute a line. This will update the "edit" window. If you change the view to 'debug' there is a watch window that you can add variables to using the 'quick watch' button - which will also allow you to view the values of variables.
There are a couple different "step" buttons to 'run to cursor', 'step over' etc. It seems to work reasonably well (but then I haven't used the VB one much).
What exactly were you unable to do?
hth
-- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
