Re: lexEdit

Hi Vern,

I assume you've seen the PDF(s) for installing - it is pretty sparse for documentation. Still, it's better than the sbreak documentation (NONE) for STRDBG debugging.

I didn't find SEP in the docs or help file... sigh. Not much info. I noticed that the install (PDF) doesn't even tell you about jhall.jar, which is required for the help to work :) "sparse" is an understatement.

The way to get a SEP breakpoint is to set just a breakpoint, clicking in left side of source. Then right click on the breakpoint and change its properties - very cool!

Ahhh... I see it now. Thanks a lot!

It appears to work similarly to the green-screen version. You have to start debug on one job, set the SEP breakpoint, and then switch the debugging to the job that actually runs the program. Cumbersome, but it works. I'm really glad you showed me!

The SEP in WDSC is more elegant. The other nice thing about the WDSC one is that it colorizes your code for you.

But, aside from those two things, I like the System debugger better. Plus, you get entitlement with JT400 (which comes with IBM i) as opposed to the requirement to buy ADTS (or RDi in 6.1). It runs a LOT faster. It's cross-platform. It's easier to use... System Debugger is a great tool, too bad it's such a "secret".

Have you found how you can bring up the graphical debugger (the name Kim ?? used at COMMON for this) when you execute STRDBG? Also very cool!

The old docs (V5R2, maybe? plus the included help file) refer to it as the iSeries System Debugger. The V5R4 & 6.1 info center refers to it as the System i5 Debugger.

Also, FYI, this debugger is installed with iNav... at least in my V5R4 version of iNav, if I go into Run SQL Scripts and click Run -> Debugger, it will open the System Debugger. It doesn't start the debug manager, though, just the debugger itself, so you can't launch via STRDBG if you use the iNav interface. But, I think it's interesting :)

Anyway thanks for the SEP info... I wonder if I can still change my article...