| re .0
VMS itself was engineered not to have Y2K problems. That applies from
version V1.0 to the current version. There are a very small number of
genuine Y2K problems in VMS. Broadly speaking these will exist in most
if not all versions of VMS due to the high level of compatibility that
VMS provides from one version to the next.
As far as I understand, it is still a subject of internal debate as to
whether Digital will formally certify early versions of VMS and, if not,
whether Digital will provide retrofixes for those versions wherever
possible. Given that there are still 2� years between now and D-day the
customer should probably be planning an upgrade and not asking the
question at all.
Of far greater concern would be the applications (regardless of the
operating system on which it was developed or on which it runs).
This is not a formal statement of course. You don't generally get them
out of notes conferences. You will find in here though a lot of
relevant discussion.
No amount of discussion will establish that the customer's business
systems will continue to run in the year 2000. Please have them TEST.
|
|
Beyond the general statements you have been pointed at, I am aware
of no decisions around preparing any ECOs for any pre-V6.0 releases,
nor even any decisions around ECOs for some V6.0 and later releases.
We are concentrating on the "due diligence" work and any resulting
ECOs that might be found necessary, and we have not yet decided what
additional releases (if any) will receive any ECOs found necessary.
In the interrum, the customer's own applications and local application
environment will need to be tested -- the recommended tests are listed
at the web site, and these will help determine if there are problems
at the customer's site.
Even if DIGITAL were to say that a particular version of OpenVMS was
Y2K-safe, one *must* test the local software environment and the local
software configuration -- there are *no* blanket Y2K-safe statements,
nor do I expect there ever will be...
|