Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?

To: daffodil who wrote (6737)	7/19/1999 12:12:00 PM
From: C.K. Houston	Read Replies (1) \| Respond to of 9818

daffodil, <The date I'm most interested in is 9/9/99. That's the easiest programming of all to find in mainframe applications, but I haven't been able to find anyone who is aware of this date in an embedded system. Therefore, I expect that this date will also pass without any significant problems.> I didn't think 9/9/99 would be an issue with embedded systems. Looks like I may be wrong. I came across a verified instance where it is an issue. Apparently the 9/9/99 problem DOES exist with embedded systems. This is VERY bad news. Especially since, in many instances, documentation no longer exists. I don't know how extensively 999 was used as an end of file marker in embedded systems. I hope not much. Guess we'll find out in about 6 weeks. ======================================================= The Institution of Electrical Engineers Embedded Systems Fault Casebook (May 1999) Equipment Type: OTHER Industry Sector: Rail Transport PC or Computer based: No APPLICATION Vibration monitoring on rail network. If train wheels have a flat spot, or axles are damaged, the rail will vibrate due to the uneven load distribution. These vibrations are detected by monitors on the rails, allowing faults to be identified. DESCRIPTION OF THE PROBLEM There are two models of this system: Mark 1 will fail to operate completely after 09/09/99 due to the fact that 999 was used as an end of file marker; Mark 2 will operate until the end of 1999, but its internal clock will fail to rollover into the next century. HOW WAS IT IDENTIFIED Supplier information was referred to initially, rollover testing was then carried out. WHAT WAS THE SOLUTION Both systems were rolled back to determine which, if any, of the previous leap years it would be possible to use. - The Mark 2 systems cannot be rolled back to a date prior to system installation, for example 1996. - *Mark 1 systems can be rolled back to any date, but will fail again once their internal clock reached 9/99.* CONSEQUENCES FOR THE "SYSTEM" Erroneous Result CONSEQUENCES OF FAILURE TO THE "BUSINESS": Catastrophic if a problem, which subsequently leads to an accident, cannot be identified. updated 1999-07-09 by webmaster@iee.org.uk iee.org.uk ======================================================= *SEPTEMBER SHOULD BE AN INTERESTING* MONTH SEPTEMBER 9 Nationwide Test of entire American Electrical System "Drill may include reducing planned outages, modified committment of resources, redispatch of generation and transmission loading, cooperation with electric market participants, and staffing of all critical facilities. Simulate system conditions and operating plans for the Y2K transition as closely as possible..." Message 9568312 "For the purpose of this memorandum, the Y2K transition date period is defined to be from 1 SEPTEMBER 1999 through 31 March 2000 …" DoD Year 2000 (Y2K) Support to Civil Authorities From Deputy Secretary of Defense cr-iiacfs1.army.mil British Soldiers pull out of Kosovo to deal with Millennium Bug Chaos The extent of the military's role has been disclosed as the armed services prepare for the critical date of SEPTEMBER 9, or 9/9/99*, when the scale of the computer chaos could become apparent. Message 10554243 Cheryl 165 Days until 2000*