y2k38 : seminar report report and ppt

[attachment=64407]
definition
the y2k38 problem has been described as a non-problem, given that we are
expected to be running 64-bit operating systems well before 2038. well, maybe.
the problem
just as y2k problems arise from programs not allocating enough digits to the year,
y2k38 problems arise from programs not allocating enough bits to internal
time.unix internal time is commonly stored in a data structure using a long int
containing the number of seconds since 1970. this time is used in all time-related
processes such as scheduling, file timestamps, etc. in a 32-bit machine, this value is
sufficient to store time up to 18-jan-2038. after this date, 32-bit clocks will overflow
and return erroneous values such as 32-dec-1969 or 13-dec-1901.
machines affected currently (march 1998) there are a huge number of machines
affected. most of these will be scrapped before 2038. however, it is possible that
some machines going into service now may still be operating in 2038. these may
include process control computers, space probe computers, embedded systems in
traffic light controllers, navigation systems etc. etc. many of these systems may not
be upgradeable. for instance, ferranti argus computers survived in service longer
than anyone expected; long enough to present serious maintenance problems.
note: unix time is safe for the indefinite future for referring to future events,
provided that enough bits are allocated. programs or databases with a fixed field
width should probably allocate at least 48 bits to storing time values.
hardware, such as clock circuits, which has adopted the unix time convention, may
also be affected if 32-bit registers are used.
in my opinion, the y2k38 threat is more likely to result in aircraft falling from the
sky, glitches in life-support systems, and nuclear power plant meltdown than the
y2k threat, which is more likely to disrupt inventory control, credit card payments,
pension plans etc. the reason for this is that the y2k38 problem involves the basic
system timekeeping from which most other time and date information is derived,
while the y2k problem (mostly) involves application programs.
emulation and megafunctions

while 32-bit cpus may be obsolete in desktop computers and servers by 2038, they
may still exist in microcontrollers and embedded circuits. for instance, the z80
processor is still available in 1999 as an embedded function within altera
programmable devices. such embedded functions present a serious maintenance
problem for y2k38 and similar rollover issues, since the package part number and
other markings typically give no indication of the internal function.
software issues
databases using 32-bit unix time may survive through 2038. care will have to be
taken to avoid rollover issues.
now that we've far surpassed the problem of "y2k," can you believe that computer
scientists and theorists are now seminar reporting a new worldwide computer glitch
for the year 2038? commonly called the "y2k38 problem," it seems that computers
using "long int" time systems, which were set up to start recording time from
january 1, 1970 will be affected.