× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Greg,

By any chance, had you recently changed the host name? Not the connection name, the host. IE to add the domain? MYIBMHOST to MYIBMHOST.mycompany.com

I was able to simulate your error today by having a member open. Then renamed the host by changing the domain only and reconnected. When I tried to switch the changed member to browse mode, RDi opened a new member with the old data.

When I looked at the "properties" of the changed one and see it's using the old host name in the RemoteSystemsTempFiles folder, without the domain name.

I kept the browse one open, changed the host name back without the domain, and reconnected. My changes made it back to the host. But now the browse with the domain name was out of synch. I simply closed that one.

I'll add a Jira for this. It appears if you only change the domain name on the host, it doesn't get updated in the cache/RemoteSystemsTempFiles directory.

If you run into this issue in the future, switch to browse mode. If it opens another member with the old content, open the properties view, and look at the temp system names on both. Switch it back to the name used in the one with changes, then save it again.

For now, if users are renaming hosts to add the domain, it's best to close all open members.

TIP: You can open the "Remote Edit History" pane to see the last 10 files you had open. You can also go into properties and make it larger than 10 if you wish. I look at adding a video for this panel.

Steve Ferrell
Fortra





-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Greg Wilburn
Sent: Thursday, August 21, 2025 7:38 AM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Local Source Member out of Sync

External: Pause and review the sender's email address, any URLs before clicking links, opening attachments, or following requests. When in doubt, contact the Service Desk.


Mike,
Thanks for chiming in.
Yes, the cached (local) source was changed/saved. However the source on the host was not getting updated.

One other weird thing that happened (I forgot about).

I received source from a software vendor as a "text" file via email. So I right-clicked on my source file, then clicked New to create a new member. I copied/pasted the text (viewing in Notepad++) into the new source member and saved it.
When I tried to view the source member on the IBM i using SEU, it said the source member had no records.

This was the prior day.

I've used RDi for quite some time - I have only ever experienced this once before (that I can recall).

Thx,
Greg

-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mike Hockings
Sent: Wednesday, August 20, 2025 10:42 AM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Local Source Member out of Sync

When you save the source the first step is only to save it locally. Under the covers the saved source will be transferred to the IBM i in a two-step dance. Transferring to the IBM I takes time so if you clicked Save then closed RDI right away and then closed Windows it could very well be that the save did not complete.

I suspect that you could open the source (does it show the latest changed stuff?), it should open from the local cache, the make a change, like change a space to a space then save to fire the save process up again or do save-as or whatever.

Clearing the cache is a solution for some issues but in this case it would zap the source you want into oblivion...

All the best, Mike

---

Mike Hockings, M.Eng.

IBM Rational Developer for System z and Power Systems Software Technical Support

IBM Canada Ltd. Laboratory

hockings@xxxxxxxxxx<mailto:hockings@xxxxxxxxxx>



From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Wednesday, August 20, 2025 at 8:30 AM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [WDSCI-L] Local Source Member out of Sync

I had saved a copy of the source text in Notepad++

So I was able to create a new source member and just paste it into the editor and save.

I'm not using iProjects. The odd part is that the "disconnect" was me closing the application after saving the source. That is the source change date/time on the IBM i. It's like when I opened it all back up around 1:30 pm it didn't sync.
Very weird.

Thanks for reply.

-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Brian Parkins
Sent: Tuesday, August 19, 2025 5:52 PM
To: wdsci-l@xxxxxxxxxxxxxxxxxx
Subject: Re: [WDSCI-L] Local Source Member out of Sync

This does happen from time to time in RDi, possibly as a result of a temporary (network) disconnect between the desktop and the host. (You're not using the iProjects facility in RDi, are you? I'm assuming not.)

The simplest fix is to drill down in your Workspace using RSE and find the local copy of your source member:

LOCAL FILES > DRIVES > ....... > REMOTESYSTEMSTEMPFILES > [server] > QSYS.LIB > [library] > [source file] > [member]

Then manually Copy/Paste to the IBM i source file. (You might wish to paste to a different source file rather than overwrite the host copy - until you've double-checked.)

HTH,
Brian.

On 19/08/2025 22:21, Greg Wilburn wrote:
I have no idea how I've done this, but the local copy of the source member (where I'm making changes) is not the same as the source member on the IBM i.

The local copy has my current changes, but the remote copy hasn't been updated since before noon today (when I closed and signed off the PC for lunch).

How do I get these to sync?

TIA,
Greg

--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l .


Greg Wilburn
Director of IT
301.895.3792 ext. 1231
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l .


--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.


Greg Wilburn
Director of IT
301.895.3792 ext. 1231
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2025 by midrange.com 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.