Y2K Problem

By -
It was simply the ignorance about the adequacy or otherwise of using only last two digits of the year.
The 4-digit date format, like 1964, was shortened to 2-digit format, like 64.

The Year 2000 problem (also known as the Y2K problem, the millennium bug, the Y2K bug, or simply Y2K) was a problem for both digital (computer-related) and non-digital documentation and data storage situations which resulted from the practice of abbreviating a four-digit year to two digits.

In computer programs, the practice of representing the year with two digits becomes problematic with logical error(s) arising upon "rollover" from x99 to x00. This has caused some date-related processing to operate incorrectly for dates and times on and after January 1, 2000 and on other critical dates which were billed "event horizons". Without corrective action, it was suggested that long-working systems would break down when the "...97, 98, 99, 00..." ascending numbering assumption suddenly became invalid. Companies and organizations worldwide checked, fixed, and upgraded their computer systems.

While no globally significant computer failures occurred when the clocks rolled over into 2000, preparation for the Y2K problem had a significant effect on the computer industry. There were plenty of Y2K problems, and that none of the glitches caused major incidents is seen by some as vindication of the Y2K preparation. However, some questioned whether the absence of computer failures was the result of the preparation undertaken or whether the significance of the problem had been overstated.

Comments

Post a Comment

Popular posts from this blog

Progress 4GL interview questions for QAD technology

By -
1.        What is “No-undo” in the variable declaration? 2.        What are the different .pf parameters 3.        What are the different types of  locks in progress? Explain with example. If a record is locked Exclusively, can a shared lock be provided over the same? 4.        What are different type of procedures in progress? Can internal procedure call other internal procedure? If yes how? If no why no? Can external procedure call internal procedures? 5.        How is array defined in progress? What is the limit of extent for progress? Can we create 2 dimensional / multi dimensional arrays in progress / How? If no then how can we achieve the same? 6.        What are browses? 7.        What are queries? 8.        Can we call excel application from progress? How? 9.        What is the difference between can-find and find? 10.     What are the different types of triggers available in progress? Name few database level triggers. 11.     What are the different type
Read more

QAD interview questions for SE and Eb2 version

By -
1.       What is the difference between WO close and WO accounting close. 2.       What are the different types of transaction types in mfg-pro 3.       What is tag count when it is used 4.       Explain the purchase cycle 5.       What is the difference between the WO module and Repetitive  module. 6.       Explain the Payment cycle 7.       Explain the Sales Cycle 8.       What is a schedule order 9.       Explain GTM why and where it can be used 10.   How can u ensure that the supplier is given a schedule on a particular day of the week say only on Monday. 11.   What is MRP .What are the different types of MRP 12.   Can the  status of the the material can be changed 13.   What are financial transactions passed when you do voucher and payments. 14.   What are the transaction  passed when the payment is made 15.   The financial transaction passed when the sales  order is  updated. 16.   What are the primary input for MRP explain  in details 17.   Expl
Read more

Use of API in QAD EE

By -
/*Sample API Program to create currency in QAD EE*/ {us/mf/mfdtitle.i} {us/bbi/gplabel.i} {us/wb/wbrp01.i}         {us/gl/glsec.i} {us/gp/gpuid.i} {proxy/bcurrencydef.i } /* ======== FOR API ========= */ DEFINE VARIABLE viReturn                     AS INTEGER     NO-UNDO. DEFINE VARIABLE ilReturnDataset              AS LOGICAL     NO-UNDO. DEFINE VARIABLE ilPartialUpdate              AS LOGICAL     NO-UNDO. DEFINE VARIABLE icPartialUpdateExceptionList AS CHARACTER   NO-UNDO. DEFINE VARIABLE ocPrimaryKey                 AS CHARACTER   NO-UNDO. DEFINE VARIABLE ocRowid                      AS CHARACTER   NO-UNDO. DEFINE VARIABLE oiDraftInstance              AS INTEGER     NO-UNDO. DEFINE VARIABLE ocPrimaryKeyName             AS CHARACTER   NO-UNDO. DEFINE VARIABLE vho                          AS HANDLE. DEFINE VARIABLE oiReturnStatus               AS INTEGER     NO-UNDO. empty temp-table tCurrency. for first RoundingMethod no-lock where RoundingMethodCode = "
Read more