Steve,
Thanks, I need to know the right type of information to grab to open a PMR.
<Sidebar> I have always had my "Show Heap Status" since a TERRIBLE release of RDI, version 8.5? I think. Which would just randomly close down. No pop-up and no warning. Just close down! Rightfully I really lost it on that issue MANY years ago. But, IBM fixed it! That was the worst RDI release ever! It had a Grand Canyon size Memory Leak. Ancient History! RDi keeps getting better!
But, I need to CHECK "show Heap Status" more often. My responses time on RDI 9.6.0.5 was outstanding; lighten FAST, no lock-ups and thoroughly impress. So I forgot to check the heap status.
I was using the Turnover Plugin, as I always do. I highly doubt that Turnover-plugin blocked the function of the save-button. But, I was also using the RPG-UNIT and using the debug perspective also. So possibly all those together caused a memory-leak. Wow! That could be very difficult to find the cause. Hindsight is always 20/20.
And I was editing an "RPGLEC" and it gave me false "syntax Error" on this statement:
"/endif // C001" --> " RNF0275: Field required to be blank is not blank; defaults to blank." Yet, I had no issues using the copy-book, just saving my changes.
I am 100% clueless if was relate to this "false" syntax error or not. Since the day's (1960's) of punch-cards, we are Required to mark Change/Added code lines. Hold over from punch-cards of the 1960's. Way before my time.
I only know checking the error log at the time, I saw that " ILE RPG ParseController: parse failed". And figure that possibly, somehow, it was related to Save-button not working. Don't know, I am merely guess here. I am only an RDI user.
So, I cannot just rely on just sending the Error-Log for a PMR. More information is helpful for debugging rare sporadic RDI issues. This will be my new steps.
1.) Stop, breath and count to 10. :)
2.) Get a screen capture of the Heap on the status bar:
https://imgur.com/a/KkwPQ2N
3.) Screen shot of the "Plug-in Selection spy". Alt+Shift+F1
https://imgur.com/a/fNXNzVu
4.) Screen shot of entire RDI.
5.) Save off my current snap shot of the error-log to submit to PMR.
(Error Log: ".log" file)
6.) Restart RDI to continue with my job work. My primary mission.
Anything else I should capture that might be helpful? Before reporting to IBM PMR and/or Private email to Armand. Armand has been a tremendous help, kudos.
PS. I just hoping to squash this rare bug where the save-button does not work. Caught me at a bad time, with deadline pressures, and being asked "Is it done yet? You said it would be done"
It has been well over a year, since I have ran into a non-functioning save-button.
Thanks for your calming words.
I have been thoroughly impress with Help-systems ever since the early 1990's. Your company's products/technological knowledge have never ceases to amaze me. Love the RPG toolbox Plugin for RDI! Been using it since the mid 1990's. So glad that Help-System is helping on quality control on RDI!
-Ken Killian-
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve Ferrell via WDSCI-L
Sent: Wednesday, January 23, 2019 3:44 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Steve Ferrell <Steve.Ferrell@xxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Could not save my source changes!
Hi Ken,
That tells me that something in your debug sessions are causing a heap memory issue.
We are running memory profilers to see if we can locate a Debug Memory leak, but we haven't been able to recreate one yet. There must be something unique to your environment or process(es).
Please help us find this memory leak by turning on your heap memory view and when you see a spike in memory usage, make a note what actions you took, or screen shots (ie SEP in a split window/Ran 3rd party junit, etc.). This type of information on a PMR (or emailed to Armand directly) will help us locate and eliminate the memory issue.
Also, once the heap is near max, restart BEFORE a memory crash and these odd behaviors will not happen.
Your past PMRs have helped make RDi better, and for that we thank you!
Steve Ferrell
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Ken Killian
Sent: Wednesday, January 23, 2019 2:03 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Could not save my source changes!
Surprise, restarting RDI allows the save icon to work again.
-Ken Killian-
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Ken Killian
Sent: Wednesday, January 23, 2019 2:53 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [WDSCI-L] Could not save my source changes!
Hi,
Tried to click on my save icon to save my source. And it would not save my source in RDi 9.5.06.
In the Error Log I notice this:
ILE RPG ParseController: parse failed
Should a "parsing error" ever stop me from saving my source?
Screen shot of plug-in Selection spy, if that happens to be helpful...
https://imgur.com/a/fNXNzVu
Oh well it happens, time to restart RDI again. And retrace my work flow. This is supposed to increase my productivity?
If it makes a difference, it was on a "copy-book" type: "RPGLEC". The parser is giving false errors on comment lines?
<break-Time!>
-Ken Killian-
midrange.com
