[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

81.0. "Y2K - Consilium & MANMAN." by MSAM03::SHANMUGA () Tue Jun 03 1997 23:33

   Hi, 
   
   	I'm Shanmuga from Y2K team from Malaysia. We in Malaysia have lot 
   of manufacturing customers who are using VAX/VMS 5.5-2 with layered 
   products & applications like Consilium Work Stream and MANMAN which, are 
   not Year 2000 ready. These customers haven't upgraded their OS and 
   applications due to the application constraints (e.g. Consilium doesn't 
   run on VAX/VMS higher then version 5.5-2). 
   
   	In some cases there are customers having our PDPs running RDBs and 
   MUMs, what will be the solution for these customers.
   
   	What is the case in other part of the world ?. Do we have plans to 
   make these customers Year 2000 compliant ? if yes, what are the plans. 
   Do we know of Y2K plans from Consilium and CA on their products ?.
   
   	Please advice, hope to here from you soonest possible.
   
   Thanks & Regards.
   
   MSAVC::SHANMUGA
   [email protected]

T.R Title User Personal
Name Date Lines

81.1 Contact Vendors XDELTA::HOFFMAN Steve, OpenVMS Engineering Thu Jun 05 1997 11:58 29

T.R	Title	User	Personal Name	Date	Lines
81.1	Contact Vendors	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Thu Jun 05 1997 11:58`	29
	Y2K requires everyone perform at least some testing for themselves. In general, OpenVMS fares fairly well around Y2K support -- though nothing is certain and the necessary research is not complete. And in any event, one or more key customer applications running on OpenVMS might Y2K-fail. As for OpenVMS VAX V5.5-2, there are presently no public statments available around what we plan to do for Y2K on this release -- at present, I'd not expect to see DIGITAL "Y2K-certify" this release. See the existing statements posted at the DIGITAL web site. And for most of your specific questions, you will need to contact the appropriate third-party vendors -- the vendors of the third-party products and applications used on the customer's systems. There is a Y2K statement for PDP-11 systems over in the PDP-11 notes conference -- we outsourced the PDP-11 operating systems products a while back. As for Rdb and MUMPS, contact the product maintainers for Y2K info. And in any event, I'd strongly suggest basic testing, to see if there are any problems in the environment -- this Y2K testing is required regardless of any vendor Y2K-support statements. These tests might show the systems have serious problems, or they might indicate that there are few or no Y2K problems visible. And these tests may/will show Y2K problems in any site-specific or rarely-seen software...

   Y2K requires everyone perform at least some testing for themselves.

   In general, OpenVMS fares fairly well around Y2K support -- though
   nothing is certain and the necessary research is *not* complete. 
   And in any event, one or more key customer applications running on
   OpenVMS might Y2K-fail.

   As for OpenVMS VAX V5.5-2, there are presently no public statments
   available around what we plan to do for Y2K on this release -- at
   present, I'd not expect to see DIGITAL "Y2K-certify" this release.
   See the existing statements posted at the DIGITAL web site.

   And for most of your specific questions, you will need to contact
   the appropriate third-party vendors -- the vendors of the third-party
   products and applications used on the customer's systems.

   There is a Y2K statement for PDP-11 systems over in the PDP-11 notes
   conference -- we outsourced the PDP-11 operating systems products a
   while back.

   As for Rdb and MUMPS, contact the product maintainers for Y2K info.
   
   And in any event, I'd strongly suggest basic testing, to see if there
   are any problems in the environment -- this Y2K testing is required
   *regardless* of any vendor Y2K-support statements.  These tests might
   show the systems have serious problems, or they might indicate that
   there are few or no Y2K problems visible.  And these tests may/will
   show Y2K problems in any site-specific or rarely-seen software...