It looks like it is getting a little confused. I've never had to use the dual session option. Pressing <F8> steps through the code just fine for me.
After you get the "host" window logged in can you choose compile and have the compile message show? I find it easiest to switch to "host" view (<alt>+v 3) so you can read all of the messages. I'm not sure if there is any difference when using uniobjects (as I couldn't get it to work as easily as disk). Perhaps the uniobjects connection is causing the issues with dual session. Can you use ftp? I'm running UniDebugger 1.2.3 hth -- Colin Alfke Calgary, Alberta Canada "Just because something isn't broken doesn't mean that you can't fix it" Stu Pickles -----Original Message----- From: David Beahm [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 1:57 PM To: U2 Users Discussion List Subject: Re: UniDebugger in SB+ I am having trouble using the step functions. In my scenario, I have a program open for editing: 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 -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
