I don't use the dual session - it seems a little redundant. I have it setup to use the disk option for read/write which requires that I have the host session logged into the correct account in order to compile/catalog the program.
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 -- 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: Thursday, February 05, 2004 9:35 AM To: U2 Users Discussion List Subject: Re: UniDebugger in SB+ <SNIP> Colin- I'm not clear what exactly Dual session is about. I can click Compile, Catalog, or Run, and they work fine. However, the whole point of UniDebugger (from my perspective) is that it gives VB-like control over running code. I made some progress by changing the login script to only get to the unix shell. However, there is still some kind of hiccup where I click Step Into, then I have to click on the Dual Session and press Enter to make things move forward. Is there something I need to set differently? TIA, David Beahm -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
