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

Did a fresh Re-Install of RDI and new workspace, and the save to resequence line numbers seems to now work with save.

I *assume* that possibly, I had a memory corruption earlier with RDI 9.6.0.4, and possibly a corrupt workspace. Who knows? I don't...

When in doubt, restart RDI, Restart with -clean, or create a new workspace.

PS. I did open a PMR# 52212, 442, 000 with IBM on this issue, and sent them my entire "OLD" workspace zipped up. I did my duty! <Big Smile>

-Ken Killian-


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Wednesday, August 1, 2018 1:49 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] RDI 9.6.0.4. Re-Sequence Lines at Save DOES NOT WORK...

Hi,

Using RDI 9.6.0.4, and I have this set on:
Window > Preference > Remote Systems > Remote Systems LPEX Editor --> check-box "CHECKED" for "Resequence Lines at Save"...

Surprise!!! It does not work!!!

Works in old, broken in new... Oh well, just say "Oh well..." and continue on...

PS. Doing a manual re-sequence from the source menu works! But, then why have that Preference? If it does not work? I expect too much, I expect it to work. <My bad, maybe it is "just me">

-Ken Killian-


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.