OH well, open another PMR...
PMR# 24058,442,000 RDI 18.104.22.168 Debugger incompatible with Free-Format
PS. I gave it several days, and I did not see any of my old PMR re-opened on the web-site for PMR. I guess I could close it if it is duplicate...
From: Ken Killian
Sent: Wednesday, March 13, 2019 6:44 PM
To: 'Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries' <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: [WDSCI-L] RDI 22.214.171.124 is NOT 100% **FREE compatible...
I have actually open several PMR on this issue, and tried to open one yesterday. But, the PMR web-site was down again! Oh well, it happens...
Too bad, IBM can't have a reliable web-site. It wanted me to re-register! Yikes, probably not a big deal to most people. But, I have very limited access to that information. So, it is a pain for me.
Previous PMR are 05324,442,000 & 2730,442,000. I was going to open another new one. But the IBM web-site for pmr was down. Oh well it happens. Then I was told NOT to open a new one, that they would re-open an old one...
Believe me, I know how to open PMRs, I do it all the time. Although, most of the time, it seems a waste of time.
Sorry, I guess these little issues drive me nuts. Especially, when they are repeatable.
Just tried it happens on my co-workers' PC too. They also fail. It is not just me...
Just telling my story, and frustration for a product, that I LOVE. (when is works.) It makes my job very enjoyable, when it works. Everybody loves a stable development environment. Or am I the only one?
Going to the PMR web-site, I don't see my old PMR re-open. I have these two number: 05324,442,000 & 28730,442,000 about the double-click issues.
I am an IBM i developer, and I expect the debugger to work to save time. Not cause me to waste more time. More often than not, I keep going back to reliable, never fail, green screen debug. I probably should just keep with that, it works! And more importantly, it is RELIABLE!! Works EVERYTIME. And it is VERY FAST too!
Oh yeah, I have two other current open PMR. Believe me, I believe in following procedures. Just don't see the results. So, since I file a lot of PMR, I have the right to complain about bugs. I do not make these issue up, they really happen.
They even happen on my home desktop with 8-CORES and Solid-State-Drive on the motherboard! So, that is a different PC. And they fail on my co-workers PC too...
Something screwy is going on, and I haven't clue how or why...
I have turned on full-time trace on debugging, for my next debug crash. But, I need to get my job DONE FIRST. And not waste time on things that should already be working! I had no idea that double-click is so hard to get to working. Or that debugging a program causes the whole IDE to crash? Really? Oh well, back to green-screen debugging on the Univac-Punch-Card-400, as my co-workers call it.
I need to reconfigure my RDI 126.96.36.199, that allowed me to take dumps, when it locks up. I guess sometimes those dumps helped the RDI developers. I have some old notes on that, where I have to change the eclipse.ini file to allow a dump. I guess I will do that too.
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Brian Parkins
Sent: Wednesday, March 13, 2019 5:31 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDI 188.8.131.52 is NOT 100% **FREE compatible...
On 13/03/2019 17:11, Ken Killian wrote:
Thanks Buck! I just wonder why it does not work for me.
I have to concur with Ken and Buck - there is a bug in RDi Debug. Just tried this simple example:
// Compile with *LISTING or *ALL debug view // In RDI *LISTING view, double-click each variable identifier to select and place in MONITOR View // Case A: Selected // Case B: not selected
dcl-s Var_a char(3); // (A)
dcl-s Var_b char(3); // (B)
dcl-s Var_c char(3); // (A)
Var_a = 'ABC'; // (A)
Var_b = 'DEF'; // (B)
Var_c = 'GHI'; // (A)
*InLR = *On;
I have not spotted this before because I usually debug from the *SOURCE view. I am used to a right-click on the variable, then MONITOR EXPRESSION from the context menu. (Yup - long-winded, I know. But works in all cases)
A left double-click in the *LISTING view has mixed results, depending on the position of the source line. (I think the light/dark blue colourisation is a red-herring.) Another thing: the hover help does not work for VAR_B either - could this be related?
So, the problem is reproducible - PMR time, Ken!!