[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference evms::y2k

Title:	OpenVMS Year 2000

Moderator:	EVMS::MARIONN

Created:	Mon Aug 26 1996
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	82
Total number of notes:	427

67.0. "how far back do we go ?" by HANSBC::BACHNER (Mouse not found. Click OK to continue) Thu Apr 24 1997 10:25

Many customers keep asking: which OpenVMS versions will be Y2K compliant ?  Many
cannot easyly upgrade to V7.2 (or whatever the compliant version will be).
Especially in production environments, where the software lifecycle sometimes
spans 10, 15 or more years.

Beyond the committed Y2K-compliant version, which we expect to ship some time
this calendar year, what are the current plans for patches of older versions ?
Specifically, we have several customers around which still use OpenVMS 5.*
versions (before 5.5) and have no plans to upgrade unless absolutely necessary.
Apparently, their applications *are* Y2K compliant.

Thanks for any information on this topic.

Hans.

T.R	Title	User	Personal Name	Date	Lines
67.1	V7.1 and V6.2 definately	EVMS::MARION	So many fish ...	`Thu Apr 24 1997 11:40`	6
	We are planning to provide Y2K support for V7.1 and V6.2 by the end of calendar year 1997. We're still discussing earlier versions but will let folks know as soon as plans are confirmed. In fact, today we have a meeting with OpenVMS Ambassadors to discuss this very topic. Karen.
67.2		STAR::MEZZANO	What's up, doc?	`Fri Apr 25 1997 12:52`	4
	Please check note 68 for a discussion about the opportunity for supporting V5.5-2.
67.3	Will support = compliancy?	EVMS::KAUFFMAN		`Fri Apr 25 1997 20:08`	17
	I want to make sure I understand what "support" of those earlier releases means. The original question asked which releases would be compliant; unless we have another process about to be put in place, the investigations in progress will not guarantee due diligence or compliancy on anything other than V7.1 or later. My interpretation of support is that we will find problems in the 7.1 sources, then retrofit the error fixes (potentially only catastrophic ones) to previous incarnations. That hopefully covers most everything in the earlier releases, but for full compliancy we have to start the investigation - both base OS and layered products - on the earlier sources. Are we planning to do that, or some subset of that process to catch just the differences between them and what we've already investigated? If we are going for full compliancy, are we prepared to reissue kits for those releases if we trip across something that can't be "patched" in the field?