Re: [WDSCI-L] LPEX CL prompt caching

[Violaine Batthish <batthish@xxxxxxxxxx>]

At this point, CL always caches, even with the disable cache button
checked.  This will be fixed in an upcoming release.

The first time a command is prompted, it is much slower than the subsequent
times.
The settings for CL caching do not really affect the speed, but rather how
the cache is built so that it is most useful to the users.
For example, if you prompt the CRTBNDRPG command on one machine and you
have the default cache setting, and then try to prompt on a different host,
then the prompter will have to go back to the host to retrieve the command
information.  If you choose to cache by release, then the CL prompter could
just use the definitions already cached.

We are also exploring several ways that a command can be refreshed when its
been changed.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab




wdsci-l-bounces@xxxxxxxxxxxx wrote on 10/12/2004 08:58:17 AM:

> 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?