Greg,
I have a work-around to make RDI 100% ROCK SOLID! And has saved me some aggravation too!
I turn off the parsing. No colors, no code-assist, no out-line. <Big Frown>
But, most importantly of all... NO LOCK-UPS!!!
Just something, I am doing to save my sanity.
I set break points, and RDI debug skips over it. Oh well, back to reliable Green-screen debug, sadly. SEU & STRDBG on GREEN Screen is 100% Reliable! <yeah!> NEVER FAILS, not even once!
PS. Don't have the time to restart RDI, nor create a new workspace. So, turning off parsing has been great!
-Ken Killian-
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> On Behalf Of Greg Wilburn
Sent: Thursday, August 16, 2018 3:38 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Officially the weirdest thing I've seen in RDi
I'm working program. I had it in debug by way of setting a service entry point. Stepping through the pgm, I received a program error inside a monitor statement (not sure if that matters).
I made some changes to the program (that was on my screen in edit mode), saved & compiled it, refreshed my SEP...
When I ran the program again, the code had REVERTED to what it was BEFORE the changes. I could literally do CTRL-Z (undo) and get my changes back. Repeated the above process, and it happened again.
I have reproduced this 4 times now.
I will close RDi and restart... but this is beyond ridiculous.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
midrange.com
