I don't have RDp (at least not yet--maybe within the next year), but have
you tried the method in the wiki? It doesn't require CVS, SVN, etc.
Here's the URL:

The method changed from WDSC to RDi--the article contains instructions for
both WDSC and RDi/RDp. But I don't know what the story is in RDp 8. It
was updated this past February (2011). I"m not sure how current it is for

wdsci-l-bounces+michaelquigley=theway.org@xxxxxxxxxxxx wrote on 11/24/2011
03:57:54 AM:
----- Message from Paul Bailey <PaulBailey@xxxxxxxxxx> on Thu, 24
Nov 2011 08:44:37 +0000 -----


Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>


Re: [WDSCI-L] RDp 8.0.3 crashes during Verify

I had similar problems not so long ago, and they cleared up after I
cleared the cache files. (Go into the Preferences option on the
Windows menu, type Cache into the little search option and press the
Clear Cache buttons in both of the highlighted options under Remote

In earlier versions of RDP/WDSC the next step would be to create a
brand new workspace if clearing the caches didn't work. I know you
can lose a lot of setup in creating a new workspace, but I once had
to "make it easy" for other new WDSC developers and used the Team
view to save and restore connections and filters. There may be
mileage in looking into this yourself in order to save and restore
your filters. (You'll need a CVS, SVN or Mercurial repository
somewhere handy.) Looking at the Team view now in RDP 8.0.3 and it
doesn't look the same as when I had to set it up in WDSC so I don't
think I can help very much in telling you how to do this for the
latest version. If you try this and have success then I'd be
interested to know what you did.


This thread ...


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

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