× 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.



Exactly, Jon.  The other workaround I use is to copy and paste the file in the Remote Systems view before doing any work.  That makes a file named "Copy of myfile.txt" in mydir, which I can then rename and edit.  But of course that doesn't help when you've already made a bunch of changes and decide you want to do a Save As.

But yeah, I think the RSE view needs to have a more formal hook for Save As to support remote file creation.

On 2/7/2019 7:07 AM, Jon Paris wrote:
That explains a few of my "lost" php sources Joe!

I got to a point where I was just creating a new source file on the host and then copy/pasting into it to get the current version.

Maybe the enhancement is needed in the RSE component.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Feb 7, 2019, at 12:58 PM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:

And while I haven't done extensive testing on the permutations, I can attest that the Save As to Temporary behavior seems to be the default for the Remote Systems view in non-RDi Eclipse applications. I use the Eclipse PDT (PHP Development Tools). When I use the the Remote Systems view to access my local drives, I can edit and save the actual files and the files are updated in my C drive (as an example). However, when I attempt to do Save As, the newly saved file goes to RemoteSystemTempFiles/LOCALHOST/c/mydir/mynewfile.txt. It does not show up in the folder mydir on my C drive. This seems to be a base behavior of the Remote Systems view.

On 2/7/2019 6:37 AM, Doug Davie wrote:
I did some testing on this this morning to verify Vern's findings.

When a member is initially opened in RDi, then Save As is performed, the
QSYSSaveAsDialog is shown, which will save the member to IBM i.

However, if RDi is closed with that member open, then re-opened, the Save
As uses the org.eclipse.ui.ide.save dialog.
And that dialog shows that the member will be saved to the local system's
remoteSystemTempFiles location.
Presumably because when RDi starts, it opens the member from the local
system's remoteSystemTempFiles location. The 'connection' between the
opened member and the IBM i is lost.


So what is needed would be an option to present the QSYSSaveAsDialog for
objects opened from the remoteSystemTempFile location.




On Thu, Feb 7, 2019 at 7:18 AM Mike Hockings <hockings@xxxxxxxxxx> wrote:

Hmm, if you have closed and re-opened RDI then I suspect that to be
different from just opening a source member in a connected session. That
is when you close RDI the lock on the source member is released. This
won't be re-acquired until you do a save or something with the edit
session. So on re-open of RDI the edit window is just reloaded from the
local source so it is essentially a local file on your PC. As a result the
dialog presented when you do a SaveAs will likely be different?

Mike

Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199




From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Date: 2019/02/06 16:52
Subject: Re: [WDSCI-L] Save AS with RDi - local only?
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>



Yeah Michael - only one connection - well, I use connections to 3 LPARs,
all in the same workspace.

My goal was to make a copy of an existing source member with a different
name in the same source file. The original had been left open over
several shutdowns and restarts over several days. If I create and save a
new member, then do a save as from the file menu, it does give me the
library list and the source file that it came from -- so that feels
different.

Thanks
Vern

On 2/6/2019 2:36 PM, MichaelQuigley@xxxxxxxxxx wrote:
See below:

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 02/06/2019
01:00:01 PM:
----- Message from Jon Paris <jon.paris@xxxxxxxxxxxxxx> on Wed, 6
Feb 2019 17:22:04 +0000 -----

To:

Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] Save AS with RDi - local only?

There is some odd-ball behaviour with this Vern. Sometimes it works
and sometimes it only offers a local target. I've never formally
reported it as I can't get it to repeat consistently.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Feb 6, 2019, at 3:48 PM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:
Y'all

I have tried from time to time to save a source member as a
different name, and using the Save as... menu item.
This must be saving only to the local workspace, because it
doesn't seem to add a member on the IBM i.
I must have missed something, as this wasn't my expectation. So
what do we have to do? Go to RSE and make a copy, then open that up to
edit?
This feels clumsy - I'm curious what else I've missed in this process.

Cheers
Vern
Nothing solid here, but could it be the connection it's using. (That's
assuming you have multiple connections.)

Michael Quigley
Computer Services
The Way International
--
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@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:

https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mailman_listinfo_wdsci-2Dl&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=wo0uDJijITU2f7aW2HWa1KiNWzc2cb7dgMN4W-85iwI&m=4FuZD2ZC9butmdm7PpqhkQvpz0T4ro1VFjw7g0P3_qc&s=Z0EmsRwpVgt92d0k_8XHu8YVh9v41ka-tyfaNh4zDm4&e=

or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at

https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_wdsci-2Dl&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=wo0uDJijITU2f7aW2HWa1KiNWzc2cb7dgMN4W-85iwI&m=4FuZD2ZC9butmdm7PpqhkQvpz0T4ro1VFjw7g0P3_qc&s=8CvRZCYjtxhP_QhHtHSh6QN8ZD0QQqaDDaaVaE4Edl0&e=
.

Help support midrange.com by shopping at amazon.com with our affiliate
link:

https://urldefense.proofpoint.com/v2/url?u=https-3A__amazon.midrange.com&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=wo0uDJijITU2f7aW2HWa1KiNWzc2cb7dgMN4W-85iwI&m=4FuZD2ZC9butmdm7PpqhkQvpz0T4ro1VFjw7g0P3_qc&s=80WpPO3Pxal1MU8SMbY02kTP-5PWGS8yCBu6rgp4sdw&e=




--
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@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.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
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@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.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com



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-2024 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.