| On the back of this recurring question I would like to add the weight of
one of my customers (a major Telco).
Due to all sorts of reasons (never going to *.0 of operating systems,
migrating to DECnet/OSI, beginning to look at UNIX etc) this customer
has remained static on v5.5-2 of VMS. However, I am now encouraging
them to move on to OpenVMS v6.1 and DECnet/OSI.
They generally like to know exactly where they stand as regards
software support and the strong messages about committed support for MCC
for a significant period have - 12 months later - resulted with only a
vague message that if you move some libraries about it should work but
might mess other products up.
Please inform the field whether you are planning a new version of
DECmcc to run on OpenVMS v6.1 compiled against the real libraries.
Alternatively who is now in charge of the maintenance of this product
as responses to earlier questions have not really had that official
stamp on them.
It is important that we give this particular customer a positive
statement as regards the short/ medium term future of this product as
we will loose credibility when offering Polycentre Netview for their
longer term support.
They are looking at Netview but it will be quite a while before they
can write off he costs of the MCC system. They are also looking at
Openview though.
Cheers
Neil
|
| Hello,
> Please inform the field whether you are planning a new version of
> DECmcc to run on OpenVMS v6.1 compiled against the real libraries.
The next MCC version V1.4 will support OpenVMS 6.1 with Decnet/OSI
Regression tests are actually runnning against the field test kit.
Field test version T1.4 will be available in November.
The SSB release should be available in March/April 1995 timeframe.
For more marketing information, please contact Susan Pomerleau who
is the product maanger in Valbonne (France) ULYSSE::POMERLEAU,
for more technical information, please contact Hubert Langensteiner,
who is the project leader of the MCC maintenance group in Valbonne,
AZUR::LANGENSTEINER.
> Alternatively who is now in charge of the maintenance of this product
> as responses to earlier questions have not really had that official
> stamp on them.
As you have already undestood, the maintenance of this product is now
done in Valbonne.
Hope this helps.
Eric
|