Before verify can operate it needs to retrieve and cache the file details. I'm guessing that when you moved to the new machine you started a new workspace and therefore files that may have been cached over months now need to be retrieved all at once.

The other situation that I have seen cause this kind of slowdown is when the workspace is mapped to a network drive. Sometimes folks even have a "part" of their C drive on a network drive to facilitate backing up the documents folders etc. The large amount of traffic that occurs naturally with the workspace which normally takes place at drive speed is now occurring any the speed of the network.

If neither of these ring true then you may need to open a support case with IBM.

On Jan 22, 2020, at 1:25 PM, Kerwin Crawford via WDSCI-L <wdsci-l@xxxxxxxxxxxxxxxxxx> wrote:

I recently got a new computer I went from a Windows 7 to Windows 10. The network/PC guy told me that the hardware is much faster/better now.
But when I do some things I used to do like verify compile on a very large program that has many files in it. RDi goes into a 'Not Responding' status and the only way to get out is close it. Granted on my old system it was slow. We have increased the memory some and changed the windows page file size.
I still have issues. Is there anything different for Windows 10 that I should look at or do?

Kerwin Crawford

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,
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives

Help support by shopping at with our affiliate

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by 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.