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,
><< 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). >>
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
IBM Certified Specialist
Phoenix Consulting LLC
East Elmhurst, NY USA
Phone 718 898 9805 Fax 718 446 1150
___________________________________ +--- | 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: email@example.com +---
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact