Re: Downside of Disable Caching in WDSC 7.0 ?

["David Wright" <dwright@xxxxxxxxxxxxxxxxxx>]

-----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
> Sent: Wednesday, June 16, 2010 10:50 AM
> To: wdsci-l@xxxxxxxxxxxx
> Subject: Re: [WDSCI-L] Downside of Disable Caching in WDSC 7.0 ?
>
> Real cure of course is to upgrade to RDP!

Completely by coincidence, I just came to the list to search for reports
of a caching problem we encountered with RDP here today....

For some unknown reason, every time I asked RDP to open a member it was
displaying an OLD copy of that member.  The member must have been cached
locally somehow.  I discovered the issue because a service program
module I opened, modified, saved, and compiled would not allow an
UPDSRVPGM.  The update failed because 5 procedures were now missing from
the module.

Only after exiting RDP completely and restarting, then when I opened the
member I would get the same one I could see in PDM.

Very odd, and very dangerous!  Luckily we had an archive copy of that
source file.