Contingency planning for 2000: the time is now

Article Abstract:

Surveys of software and financial executives in the US and Europe indicate that a significant number of software applications with date problems will not be repaired before Dec 31, 1999. It is highly improbable that databases will be fully compliant with year 2000 computer date transition (Y2K) requirements even in the early part of the 21st century. A one-year planning calendar which highlights the major contingency activities for the critical period from Jan 1, 2000, through Dec 31, 2000, is suggested.

Information systems

---

Understanding the Y2K glitch

Article Abstract:

Glitches in hardware equipment could be one of the most ignored and unpublished areas in the year 2000 computer date transition (Y2K) problem. In most cases, there actually is no need for concern. Those who rely on personal computer systems to run their businesses, however, should take notice as a simple PC component called the CMOS real time clock could cause problems. This component runs the personal computer's date function and could be affected by the Y2K problem.

Microcomputers

---

Similar abstracts:

• Abstracts: Conflict management training for today's engineering managers. Worthy goals: behind the wheel and nowhere to go
• Abstracts: Conference highlights understanding variation. A preview of the 1998 quality expo. Break old boundaries with concurrent engineering
• Abstracts: Versatile is the word for this online monitor. Reshaping clay. A renewed boost for ethanol
• Abstracts: A crude awakening for refiners. Reeling in regulations
• Abstracts: Seven tips for cal accreditation success. Say goodbye to Joe: replacing the quality craftsman. Selecting the right stylus: improve the performance of touch-trigger probes

This website is not affiliated with document authors or copyright owners. This page is provided for informational purposes only. Unintentional errors are possible.