| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 689.1 | I don't have the answer but... | CHEFS::BEATON_S | I just loooooooook innocent ! | Thu Mar 06 1997 08:35 | 10 |
| I think this could be a major problem for existing customers (who have
no plans to take on further development of their original TeMIP based
solutions. (Like Energis for example.)
New releases of TeMIP and UNIX, etc. may well cope with the year 2000,
but it will not be a simple task integrating, say XTESS or the ENOBAM,
with a new release of TeMIP or UNIX. (It could be a real financial
headache as well when customer support contracts say things like
"upgrades are free".)
|
| 689.2 | | RDGENG::COBB | Graham R. Cobb (Telecom PSC), REO1-F8, 830-3917 | Tue Mar 18 1997 10:00 | 9 |
| Terry,
If it is BT then please co-ordinate with me and Chris -- we are working this
issue very carefully with BT and MCI for the Cambridge programme.
For any other customer you might like to talk to us but you also need to
work with the Engineering group to get a formal statement.
Graham
|
| 689.3 | Year 2000 Compliance | GLRMAI::VANDERLEE | | Thu Mar 27 1997 14:23 | 9 |
| My customer, MCI requires that Digital formally document that all
products being proposed are year 2000 compliant. My understanding is
that UNIX V4.0 is the first version of UNIX that is fully Year 2000
compliant. Since TeMIP is not currently supported on UNIX V4.0 we
cannot currently assure our customer that the products proposed in our
$100M (US$) bid are Year 2000 compliant. The note 689.1 raises a
further issue around the complexity of integrating XTESS as compliant
as well. New releases of these products MUST be fully Year 2000
compliant.
|