Re: LPEX CL prompt caching

Thanks Violaine!  I guess I assumed the disable cache would work and didn't
bother to test.  It worked when I tested because I had just cleared the
cache.
While we are on the subject of CL, do you know of a future modification to
allow changing elements of a list in a command when prompted from a CL?
For example, changing a library name in a list of libraries on a command.
The only available options are: Add, Remove, Move up, and Move down.

Craig Strong

** Violaine wrote:
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