![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|||
![]() |
![]() |
![]() |
||||||||
![]() |
![]() ![]() |
![]() |
![]() ![]()
|
![]() ![]() |
prv![]() |
|||||
![]() |
Year 2000 Date Issue at BC Hydro |
![]() |
![]() |
|||||||
![]() ![]() |
P ![]() |
![]() eople involved in the Information Technology (IT) industry have been preparing for the rollover to the Year 2000 for some time now. Based on previous system designs and programming techniques, some applications will not function correctly and will even fail when the Year 2000 is reached. In fact, these problems will manifest themselves earlier in systems which forecast into the future. The problem stems from the early IT industry's desire to capitalize on efficiency. When 80-column punch cards were in use, the century was assumed to be "19". Storing the year portion of dates as two digits, rather than four, was a means of saving two characters on a card, on screens, and in storage. This made sense because computing resources were more constrained and expensive than they are today. It is also common practice for people to write dates such as "DD/MM/YY". This practice continued, even after resource costs came down, until recently when system developers incorporated solutions to the Year 2000 into their designs. These two-digit years can be found in places such as
All hardware and software needs to be reviewed and potential problems
identified so that changes can be planned and implemented in an effective
and efficient manner. Being proactive on this issue will stop a lot
of the problems, along with the costs and frustrations associated
with them. Many questions have been raised about the Year 2000. See the answers
to some of the most frequently asked questions. |
||||||||
![]() |