Problem
Why would a customer try to run their application in 1972 to avoid the Year 2000 problem?
Solution
Some customers have applications that cannot handle dates beyond 99 (that is, 1999). These customers are also not in a position to upgrade their application before the year 2000 and so they are looking for alternative ways of continuing to use their application.
Customers select 1972 because this is the last year when the 1st of January fell on a Saturday. The 1st of January also falls on a Saturday in the year 2000. 1972 is also a leap year and this means that their application will report the correct day and date (with the exception of the year).
The problems with this approach to "solving" the Year 2000 problem is that SCO operating systems that use a License Manager to control the licenses of the SCO Software on the customer's system will refuse to grant licenses if the date on the system is set outside of the years 1995 to 2038. SCO operating systems that use a License Manager include:
SCO OpenServer Release 5 based systemSome SCO UnixWare Release 2.1 based systemsUnixWare 7 based systemsCustomers trying to work around their Year 2000 problems in this way should be advised to:
1. Upgrade their application to one that works in the year 2000.
2. Use a product like Date2Date from ICL (http://www.icl.com) to create up to 16 virtual RTCs on their machine providing bogus dates to their applications.
3. Run the application on an SCO platform that does not make use of a License Manager.