Re: RDi not saving changes back to system

FWIW,

I began changing one specific property a few years ago, because I was getting a lot of these source save issues... The property in question is on the first level "Remote Systems", at the bottom is "Use cached information to restore the Remote Systems view". When that was checked, if I had shut down RDi with LPEX editors still open on the workbench, then when the product was restarted, the LPEX panels would re-open, but from the locally cached version of the source. The connection and member lock were not reestablished, and even though it appeared that I could edit and save the source, it was updating to the local cache only. I lost many changes this way in the WDSC years, so I began to UNCHECK the "Use cache" property... I think I remember threads from a few years back that the source member locking mechanism had been fixed, but I never really tried it...

Hth,
-Eric DeLong

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Bailey
Sent: Tuesday, May 20, 2014 4:23 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi not saving changes back to system


The potential for lost source because of bugs is present and really dampens the enthusiasm when it happens to you, but otherwise SEU isn't even close to RDi for development purposes and I'm not sure I can even use SEU anymore.

If I could tell my team that the minor bugs are gone I think I'd get the team up to 75% utilisation instead of the paltry 50%.


-Paul.


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Young
Sent: 19 May 2014 18:29
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi not saving changes back to system

Ken,
I have to agree with you regarding RDi beating SEU hands down.
I have been using this product since it first came out as WDSC.

Over the years as it was enhanced and then became RDi, the product has just gotten better.
The only time I use SEU is when I need a quick patch.

Do not know when I will be getting the updated RDi 9.1, as it requires a new license key. It took the better part of a year before the PTB got us the license key for RDi from RDp. (sigh)


Jeff Young
Sr. Programmer Analyst


On Mon, May 19, 2014 at 12:28 PM, Ken Killian <kkillian@xxxxxxxxxxxx> wrote:

Sort of along the same line... (Maybe?)

A newbie complained to me that the RDi 9.0.1. is not allowing him to
save member-source. He had to save to a new member name and then later
rename it. He said what a pain.

I had to tell the newbie that RDi 9.0.1 is "FLAKY", and greys out the
save-icon. It is a "Known Issue".
<Big Frown>

I also have issues with the right-click Context menu not popping up
with all options. I have to do it second time for it to give me all the options.
Hit Esc, and then do a re-try...

I also have to click on another tab to get the compiler menu to show
up. I haven't had this issue with previous version of LPEX.

Oh well, I hope this if fixed on RDi 9.1, due to be released on May 23rd.

I have created a new work space, and I still have this "Flaky Repaint
Issue"...
<frown>

Too bad, only 1/3 of the developers here use RDi. Because they over
hear about "flaky" issues... It is too bad, they are afraid to even try it...


PS. It still beats SEU by a LOT!!!
<Big Smile>

-Ken Killian-
Over 8 years of using RSE/LPEX.


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff
Young
Sent: Monday, May 19, 2014 9:40 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries
Subject: Re: [WDSCI-L] RDi not saving changes back to system

Well,
The problem appears to have corrected itself (for now).
I had to edit the same source member today, and everything is working fine.

Just for the record, I was the only one editing the source member at
the time, and did not attempt to edit it in SEU.
The only reason I went into SEU (after I closed the edit session for
the member in RDi) was that I was getting undefined field errors on
the compile, and the field name it was referring to did not exist in
the source. I had that name earlier, but changed it and that is when
I started noticing that my changes were not being saved to the original source file.

Thanks for all the suggestions, and if it occurs again, I will try them.



Jeff Young
Sr. Programmer Analyst


On Sat, May 17, 2014 at 4:08 PM, Gerald Kern <jp2558@xxxxxxxxx> wrote:

I used to have that problem, but haven't for some time (knock,
knock), but one thing I'm fairly certain that causes this behavior
is doing work in RDi, then myself or someone else touches the same
member in SEU, and if I don't refresh the object table, the
situation you describe happens. One thing I've learned to do is
refresh the object

table rather often.

Hope that helps.

--
Thanks, Jerry

Gerald Kern - Information Technology Programming Supervisor IBM
Certified RPG IV Developer Lotus Notes/Domino Administrator The
Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623
Phone 419-479-5535
--
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.
--
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.

Scanned by MailDefender - managed email security from intY - www.maildefender.net

Important, this email transmission and any files with it are strictly confidential to the intended recipient and may be legally privileged. Any views or opinions presented are solely those of the author and do not necessarily represent those of BHSF. If you are not the intended recipient, you must not copy, disclose or distribute its contents in any way. If you have received this e-mail in error, please notify the sender and delete the e-mail from your system.

We have taken steps to ensure this email and attachments are free from any virus but do not accept any responsibility once this e-mail has been transmitted. You should scan any attachments for viruses. No contract may be concluded on behalf of BHSF Limited by e-mail.

Registered Office: BHSF Limited, Gamgee House, 2 Darnley Road, Birmingham, B16 8TE. www.bhsf.co.uk Registered in England number 35500. BHSF Limited is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority.
--
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.