|
Please take the time to read the Q&A in note 238.*, and learn exactly
what is involved. (For many customer sites -- other than, say, those
running/using specific products or specific versions such as OpenVMS
Alpha V7.0 -- 19-May-1997 will be a big yawn. The Q&A will explain
what should be done, and -- real soon now -- a procedure to determine
if your customer's system or application will be affected.)
:Will the DELTA TIME problem as fixed by the ALPLIBR05_070 and VAXLIBR05_070
:(or now VAXLIBR06_070) also occur on ALPHA's running VMS 1.5.
I am not aware of any extensive research on this release.
The upcoming Q&A includes procedures which a customer can use
to test for the problem. (One can effectively use the Y2K testing
procedure that is posted at DIGITAL's http://www.openvms.digital.com
webpage -- it's basically the same procedure for 10K.)
:I have searched various databases and this conference, so if it has already
:covered, then I haven't found it.
Please see note 238.*.
:I told the customer that it may be that
: 1. AXP VMS 1.5 is now unsupported and it wasn't tested to see if the
: problem would occur there;
:or
: 2. It may may occur but there is no patch since AXP VMS 1.5 is unsupported.
OpenVMS Alpha V1.5 has not been supported for a while now.
I'd strongly recommend an "upgrade" -- we (engineering) have been
told that a concerted effort was made to get our customers to upgrade
to the OpenVMS Alpha V6.1 release (or later), and that we (DIGITAL)
specifically "desupported" these earlier Alpha releases.
We (engineering) are not presently planning on a (wide-spread)
distribution of the patch kit for versions of OpenVMS Alpha prior
to V6.1. DIGITAL Support may choose to create (and charge for) a
custom kit for specific earlier releases. (When feasible, of course.)
|
|
I just got a direct mail from a customer also concerned about 1.5
Perhaps OpenVMS Alpha 1.5 is sufficiently 'off' the beaten track
to warrant this specific topic 378. I think it does.
For starters, my reaction is ofcourse: move to a supported version!
I tend to explain it as 'OpenVMS 1.0 was a proof of concept, to
allow implementors to get going. OpenVMS 1.5 was a 'Beta test /
Prototype' platform. Only with 6.1 did VMS mean 'businnes' on Alpha.
Anyway... Here is my concrete suggestion / question: what are the
chances to succesfully slap a fixed 6.1 RTL onto a 1.5 system.
Anyone have a system to try it on? Images linked against the RTL
would supposedly keep on working (upward compatible). The RTL itself
may however refuse to install, being more recent than the rest, and
perhpas being linked against something (system?) creating a downward
compatibility conflict.
Looking for a specific confirmation as 1.5 is not in the Q&A.
- There was no DECthreads on 1.5 and thus no thread?
- No security server issue
- No Time server issue
- Yes LIBRTL 9999 day artificial restrictions.
2�,
Hein.
|