The year 2000 problem

Abstract

The purpose of this article is to discuss the root causes of the Year 200 Problem, the effects of the problem and how a systematic approach can be used to solve this problem. INTRODUCTION The Year 2000 Problem (Y2K), also known as the 'millennium bug,' may well be one of the largest problems facing organizations as they enter the 21st century. Computers are an integral component of an organization, organically of equal importance as financial resources and human resources. An organization's information system is the base on which all strategic and informa­ tional processes are developed, defined, and redefined. Therefore, the Y2K problem is not just a computer problem, it is a systemic business problem. A systemic approach will be needed to solve this problem. This is a business problem because information system (IS) managers must effectively plan for the reallocation of hundreds of IS workers and millions of dollars in each organization. The average cost to examine a line of COBOL code is $8.35, and the Gartner Group estimates that there are 180 billion lines of COBOL world wide (Freeman, 1998). This problem requires a commitment of business resources (humans, financial, and capital) and if left uncorrected puts the organization and its customers at risk. DEFINITION OF THE Y2K PROBLEM The Y2K problem is the failure of computers to correctly store, manipulate, and calculate dates from the 1900's to the year 2000, including leap years. The Y2K problem has existed since the beginning use of computers. Computers, like most technological products, are relatively ex­ pensive in the beginning of their product life cycle. They become less expensive as innovation and the evolution of technology produces superior products. Hard disk space in the beginning use of computers was very expensive and very precious, almost as precious as silver or gold. The cost