| A customer has reported this problem to me. Specifically, he is
calling CMS$CMS anywhere from several hundred to several thousand times
to create elements from his application. He needs to be able to clean up
the excess virtual memory allocated by CMS from within his application.
I see that wishlist item #58 already has this request, but that such a
cleanup routine (CMS$CLEAR_LIBRARY?) apparently isn't planned for the
next release or anytime soon.
This customer has an urgent need for this cleanup capability.
They are basing their entire configuration management scheme upon callable
CMS. What is the proper method of raising the priority of wishlist item
#58, in order to ensure that it gets implemented within the next six months?
I'm sending a copy of this note to the DECset product manager, to ask the
same question. Yes, this is the same customer who finally chose to give up
on using MMS, because we chose not to implement a feature, which he believed
that he needed. Maybe we can have a happier outcome with CMS, since he is
asking for a feature that we have been planning to implement anyway.
Thanks,
Bob Sampson
|
| Hi Bob,
What you'll want to do is to call Cathy Axel (the product manager) and
give her as much business justification you can for the inclusion of
this particular feature. The more justification you can muster, the
higher consideration it will likely be given.
One note, though: we're just putting the finishing touches on DECset
V12.2, and it will be another six months or so before the field test
for V12.3 begins. The target release time-frame for V12.3 is about this
time next year.
This is a perfect time to be raising this request.
-- Daryl
|