An understanding of the y2k bug
Neither managers nor programmers of that time expected their programs to remain in use for many decades.
One way the year problem was handled was by creating new software programs that saved dates as four digits instead of the two digits previously used.
Countries such as South Korea and Italy invested little to nothing in Y2K remediation,  yet had the same negligible Y2K problems as countries that spent enormous sums of money. These were followed by accusations that the likely incidence of failure had been greatly exaggerated from the beginning.
Y2k problem in hindi
Some programs may have relied on the oversimplified rule that a year divisible by four is a leap year. Facts Matter. This view also asserts that there would have been only a few minor mistakes and that a "fix on failure" approach would have been the most efficient and cost-effective way to solve these problems as they occurred. As a long integer in bit systems uses 64 bits, the problem does not realistically exist on bit systems that use the LP64 model. These were generally minor, apart from reports of some Norwegian trains that were delayed until their clocks were put back by a month. The Y2K Scare was a phenomenon at the turn of the 21st century where computer users and programmers feared that computers would stop working on December 31, Rollover of such systems is still a problem but can happen at varying dates and can fail in various ways. This was thought acceptable, as older legacy systems tend to eventually get replaced by newer technology. The US Government followed a three-part approach to the problem: 1 outreach and advocacy, 2 monitoring and assessment, and 3 contingency planning and regulation. But midnight passed on the 1 January and the crisis failed to materialise - planes did not fall from the sky, power stations did not melt down. This delays the eventual roll-over problem to the end of the year There was no computer malfunction.
Instead of a date readingit read However, this method was costly, requiring massive testing and conversion efforts, and usually affecting entire systems. Reputable preachers were advocating food storage and a "head for the caves" mentality.
Y2k bug explained
Computer experts were later accused of exaggerating the concept of the "Millennium Bug" as millions of dollars were spent in preparation of the Y2K problem. For instance, for much of financial history, financial institutions have not generally been considered cutting edge tech-wise. But midnight passed on the 1 January and the crisis failed to materialise - planes did not fall from the sky, power stations did not melt down. Extended to a global scale, these worries of an epidemic-like panic had international markets holding their breath heading into the turn of the century. Individual companies also offered their estimates of the bug's economic impact on their top-line figures. It was thus possible that database programs might act on the records containing unknown dates on that day. Please help improve this section by adding citations to reliable sources. Software and hardware companies raced to fix the bug and provided "Y2K compliant " programs to help. There was also the issue of software developers taking advantage of the sudden urgency, charging exorbitant prices for Y2K consultancy work, which hit those countries with the greatest number of legacy systems the hardest. These were generally minor, apart from reports of some Norwegian trains that were delayed until their clocks were put back by a month. This put Uganda in the "top 20" out of national governments, and on a par with the United States, United Kingdom, Canada, Australia and Japan, and ahead of Germany, Italy, Austria, Switzerland which were rated as only "somewhat informative".
Since programs could simply prefix "19" to the year of a date, most programs internally used, or stored on disc or tape, data files where the date format was six digits, in the form MMDDYY, MM as two digits for the month, DD as two digits for the day, and YY as two digits for the year.
based on 105 review