Re: Source code changes un-recoverable after a crash -- WDSCI-L

Jon,

Good point! That has worked for me before.

I believe we tried the "Save as..." once. And it gave us the option to save it to PC file, not another member on the IBM i. Which I discovered usually happens when something gets hosed up...

We just copied his PC-FILE in the work-space to his desktop. And then since the save source did not work, we re-applied the changes from that PC-Text file.

-Ken Killian-

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Tuesday, February 14, 2017 12:58 PM
To: Wdsci-L <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Source code changes un-recoverable after a crash

"so all his changes were lost. "

Perhaps not. The workspace is constantly being saved on the PC. The actual interval being determined by the save interval which by default is 5 minutes.

In case like this in the past I have been able to recover the updated source BUT you have to be aware of the possibility _before_ opening the source from the host again. I don't know why RDi does not always "notice" that an updated local copy exists (but it hasn't happen to me in a very long time now) and prompt you. But in cases where you know that there is something bad going on it can be worthwhile to dig into the workspace and take a copy of the locally saved source file. Then you can use that as the source for updating once you re-open.

Also, I have found that sometimes Save As will work in cases where Save does not.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Feb 14, 2017, at 11:56 AM, Stephen M. West <stephen.west@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Ken,

I have experienced the issue where RDi will not save (Ctrl-S). I
manually copy/paste my source from RDi into Notepad, re-start RDi,
then copy the changes back from Notepad.

On another occasion, one of the developers here spent several hours
making changes to a source member, when his PC crashed un-expectedly.
Who knows why it crashed; these things happen. However, he did not do
a <ctrl-s> to save his source, so all his changes were lost. He did
not get the normal prompt to recover his changes at RDi startup.
Never would have happened in SEU, because the changes are always
retained, even when the green-screen app fails. I submitted an RFE to
IBM requesting that RDi be changed to save source to the IBM Power i
at regular intervals. It can be viewed by the public at:
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=7
1090

The RFE was "Declined". Here is the help text behind "Declined":

"Declined: IBM has evaluated the request, and has determined that it
can not be implemented at this time or does not align with the current
multi-year strategy. This request may be resubmitted for consideration
after 12 months from the date of decline. The request submitter will
automatically be notified by email when the request qualifies for
reconsideration and resubmission."

Kinda felt like I was told "shut up and sit down" after requesting
simple functionality that should have been in RDi from the beginning.

Since I never received an email stating that it "qualifies for
reconsideration and resubmission", I presume it was a hard "NO!!!".

b.t.w. - Thanks for your persistence in pushing for improvements to RDi.
It has some awesome features that blow SEU away. You are not the only
programmer having issues with RDi. Please keep up your efforts on
behalf of us programmers who gave up after our efforts (it takes time
to craft an
RFE) were shut down with a simple "Declined". You are our
[un-official] advocate for RDi improvements.

Stephen West
Lead Software Engineer
Stillwater Insurance Group
12500 I Street, Suite 100 Omaha, NE 68137
W: (402)599-8325 | C(402)659-0452
Stephen.West@xxxxxxxxxxxxxxxxxxxxxxx

-----Original Message-----
On Tue, Feb 14, 2017 at 10:12 AM, Ken Killian <kkillian@xxxxxxxxxxxx>
wrote:

Mark,

I can understand that...

At work, I am called "Mr. RDI", since I promote RDI.

This morning, my co-worker just called me over to his Cube....

He was UNABLE to save his source changes in RDi 9.5.1.1, and he was
perplexed. It gave some cryptic Java Error, but unable to save his

source.

This is a BIG ISSUE!!!

He changed the code, and NEEDS to be able to save his CHANGES!

So, we manually copied his PC-File over to another file. Close his
source WITHOUT CHANGES; since we were UNABLE to save changes.

And manually re-open the member with NO CHANGES....

Now, he is forced to MANUALLY re-apply his changes, looking another
PC file. Where RDI was unable to allow him to save his changes!!!
WTF. It is NOT JUST ME!

Saving a change source file "should NEVER FAIL" period! Not even ONCE!

He wants to use RDI, but with issue, why not just use SEU, where you
KNOW it will SAVE YOUR CHANGES??????

PS. Once I get the error message from his Laptop, I will post it on
this message.

-Ken Killian-
Mobile Comm Back-End
Senior IBM i Developer using Rational Developer for I RDI 9.5.1.1
Running IBM I, that supports: Java, PHP, Ruby/Ruby on Rails, Python,
Node JS, RPGLE

--
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: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.

--
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: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.