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


  1.  Home
  2. WDSCI-L
  3. October 2004

LPEX CL prompt caching

By default, in WDSC, CL help and prompts are cached on your PC.  If a
command changes, you would not know about it in the LPEX editor.
You can change this behavior in Windows > Preferences > Remote Systems >
iSeries > Cache.
Click on "Clear" to clear the cache.  Then check "Disable caching".
I did not notice any difference in performance whether this was checked or
not.  But, disabling caching let me see the new changes to the command.
Even when caching was enabled, I did not notice any difference between the
different cache settings.  Maybe I have a quick connection to the iSeries.
Why would we want to cache CL help and prompts if performance is apparently
not an issue?
Even if performance were an issue, shouldn't WDSC (with caching) still
check for changes to the command?

As an Amazon Associate we earn from qualifying purchases.

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