× 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 Michael, we had a similar problem (using v7.5 ...): "Save As" on a
member already open from a previous session.

Since then we adopted a new rule: close the member, open again and then
Save As.

HTH

--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco

2015-01-21 16:10 GMT+01:00 Koester, Michael <mkoester@xxxxxxxxxxxxx>:

Thanks Ken.
While I await further responses, I made a new source member
(RSE>FILE>New>New IBM i Source Member) with a slightly different member
name, then in LPEX I copied the contents of my dysfunctional source member,
pasted into my new empty source member, and clicked Save. I now have a new
source member that exists on the host, and I can continue development with
this work-around.
Still puzzled about why the other one doesn't create a host source
member...
-- Michael
~~~~~~~~~~
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken
Killian
Sent: Wednesday, January 21, 2015 9:49 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
for
System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.1 SAVE-AS Source member not saved on host?

Michael,

I apologize; I see you already found your PC source, please disregard...

I had too much going on this morning...

-Ken Killian-


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken
Killian
Sent: Wednesday, January 21, 2015 9:45 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
for
System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.1 SAVE-AS Source member not saved on host?

Michael,

Just for a start, trying searching your PC for your source file...

To keep it simple, here is what I would do:

1.) Open a dos Window. Windows+R and type in "Cmd.exe"
2.) Navigate to your where your work-spaces
Ex: C:\Users\KKILLIAN\IBM\rationalsdp, in my case, I am on windows-
7
3.) type in "DIR MyProgram.RPGLE /s" to scan and find the source....

Of course you could use the "Search" in windows, I just showed the "Old
way" to scan on the PC. Since the search is different depending on your
version of Windows...

That would just be a starting point, to see if the source is on your
PC....

This is only a start... But, it might give you some answers, and help you
recover your code...

Worth a try, I guess...



-Ken Killian-

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
Koester,
Michael
Sent: Wednesday, January 21, 2015 9:30 AM
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] RDi 9.1 SAVE-AS Source member not saved on host?

My RPGLE Source member does not appear to be on the host.
Working in a "connected-to-host" environment, I created a new RPGLE
member
by saving an existing source in LPEX using File>SaveAs, and providing a
new member name. That was Monday morning. I continued modifying the new
source throughout the day, and again yesterday. I noticed (and was
slightly disturbed) that my source member did not show in my RSE tree, so
I selected the source file name above the members, and clicked RSE's
Refresh button. My new source member name did not appear still. In
LPEX,
I hovered the pointer over the tab of my source, and confirmed that the
source path and name were correctly showing the same place as all the
other RPGLE source members I had open from the same source file. That all
looked fine.
I restarted RDi again this morning, my workbench maintained the LPEX view
of my open source members as before, but again, no sign of that source in
RSE.
I opened WRKMBRPDM, and saw that the source did not show there either and
got more concerned that it was not being saved on the host. Other
members
that I'd worked on yesterday showed on PDM as having been modified
yesterday, so I know my RDi session was connected. I also saw that the
source from which my new source originated maintained the old last-
modified date, so I know my new source was no longer associated with the
original source.
I checked the Verify Connection in my current RSE instance, and see that
I
am indeed connected with no issues.
I verified that the folder in IFS showed those other members having been
updated yesterday, but the member created on Monday was not among them on
the IFS.
I see that my new source is in the .../workspace/RemoteSystemsTempFiles
folder, but apparently nowhere else. When I click the Save button in
LPEX, it saves to the PC, but apparently nowhere else.
When I first noticed this, I was running RDi 9.1.0. Last night,
Sys-Admin
upgraded me to 9.1.1, and that did not change the results.
Has anyone seen this before? Does anyone have any suggestions? (I made a
copy of my source from the RemoteSystemsTempFiles folder, so I don't lose
two days of work), but I need to get this pushed back to the host and
working properly.

Thanks,
Michael Koester
Programmer/Analyst
DataEast
--
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.


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.