We couldn't recover like that - Unfortunately it wasn't obvious that the source hadn't been uploaded. When you opened the source in RDi you had the changes (because of local source cache files, I guess). When you compiled the source, it used the source on the IBM i. Eventually, after trying to work out why their changes weren't working, they opened the source using SEU and discovered that the changes weren't on the IBM i.
To recover we closed all source members, closed RDi, re-opened RDi with the -clean option and then re-opened the source members. Because I fell foul of this bug sometime back, I have insisted that to shut RDi down we must not leave source members open, but they forgot and eventually got hit by the bug. Now they'll remember.
Paul.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of MichaelQuigley@xxxxxxxxxx
Sent: 20 December 2013 21:55
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Promoting WDSCi, RDp and/or RDi
Losing source hasn't happened to me for quiet a while. But a couple years ago when it did, I would navigate to the source in the workspace and open it from there. Then I would press Ctrl+A followed by Ctrl+C to select and copy everything to the clipboard. Then I would close the editor, delete the source from the workspace, and reopen it. This would open the original, unmodified source. Then I would do a Ctrl+A and Ctrl+V to replace the entire member with my updated version. You still lose the source-line change dates, but at least the source is correct.
Michael
wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/20/2013 07:37:01 AM:
----- Message from Paul Bailey <PaulBailey@xxxxxxxxxx> on Fri, 20 Dec
2013 11:19:29 +0000 -----
To:
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject:
Re: [WDSCI-L] Promoting WDSCi, RDp and/or RDi
Just to be clear, I'm not trying to force RDi on to my colleagues but
when green-screen programmers of 20-30 years experience do adopt the
new tool solely on my casual advice but then fall foul of such a
critical bug as losing/misplacing source code changes then I feel a
fool for promoting the tool. Happily, both programmers who suffered
yesterday are (as I type) upgrading RDi to v9.0.1 and look like they
will continue using it. (The SEU users who like to argue against RDi
are looking a little smug today, though.)
I don't think I ever used the REXX macros in Code/400... what did you
do with them then that would be useful in today's RDi?
-Paul
--
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.
midrange.com
