Try saving your changes to a new member so they are not lost then clear the
file cache?


Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
IBM Canada Ltd. Laboratory
voice 1-905-413-3199 T/L 313-3199 ITN 23133199

From: Jeff Young <jyoung0950@xxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>,
Date: 2014-05-16 14:23
Subject: [WDSCI-L] RDi not saving changes back to system
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>

RDi 9.0.1
I have a large source member that I am making changes to.
After I complete my changes, I save the source member. It *should* be
saving the changes back to the original source file/member on the remote
system, but it does not.
After the save is complete (the compile option is available when I right
click on the member, I view the source using SEU on the remote systems, and
my changes are not there.
If I close the member in RDi, and re-open it, it does not bring in the
source from the i, but rather from what appears to be the local copy that
it saves to prior to pushing the change to the i.

This just started happening today.
I have closed RDi and restarted it, and it downloaded the correct source
the first time, but after I made changes and saved it, I had the exact same

Ideas anyone?

Jeff Young
Sr. Programmer Analyst
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,
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.