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



It's not unheard of for RDI to get bogged down.

Have you checked your error log?
RDI may have spent the time trying to do something unrelated to the refactoring.

Has this only happened for one program or has it happened for multiple programs?
Have you tried starting RDI with the -clean (dash clean) option?
Have you tried creating a new workspace?

Whenever I've used the refactoring, it's been quick enough.
45 seconds for such a short program seems extreme.


Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Monday, May 8, 2017 1:47 PM
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Slow refactoring...

Hi all, I'm using RDi 9.5.1.2.

Does anyone else find that refactoring the name of a variable is slower than expected? For example, renaming a variable in a 130 line program takes approximately 45 seconds from the time I press Shift-Alt-R to the time when the window opens to enter the name the new name.

Refactoring works great. I just wondered if everyone experienced a slow time or if it is my installation.

Thanks,

Rob

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.