Re: A silent Y2K bug

Hank Heath wrote on Thu, 6 Jan 2000
>
>The obvious answer is that a contract applied a mask of 20xx to all dates,
>figuring that no new dates would back track into the 19xx's. The fix was to
>put a window into the date.
>
>
>In a message dated 01/05/2000 11:01:34 PM Eastern Standard Time,
>tomh@simas.com writes:
>
><< We just want to know about the error, how it was 'fixed' - not about the
> illness, or why the onset date is 12-31-2000 (boy that's weird). >>
>+---
Hank
Thought we went into code to seek out this type error as a part
of Y2K remediation and again in IV &V code reviews?

I'd be careful of the window standards against the full system




Glenn
__________________________________
Glenn Ericson,
IBM Certified Specialist
Phoenix Consulting LLC
East Elmhurst, NY USA
Phone 718 898 9805 Fax 718 446 1150
mailto:Glenn-Ericson@att.net
___________________________________ +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---