|
Mike, I work for a very large southeastern bank, and the OCC is VERY strict when it comes to Y2K testing and contingency plans. We have tested all of our AS/400 applications (Both of 'em!), on a separate Y2K test box that we rolled the dates on. We basically had to test for several scenarios, 12 Dec 1999, 1 Jan 2000, and 29 Feb 2000. Our testing had to be completely documented and has even been reviewed by internal auditing as well as internal Y2K department, and the OCC. As part of our testing we also had to implement a Change Management system so that we could prove every change after the test was documented. We even have to have a contingency plan for everything. We will lock out all changes beginning in November and a moratorium will be in place until March 1999. We will have a support staff on site on Jan 1 2000 to verify all major critical applications and systems. In short, you have a big job ahead of you, if you like I can offer some more detailed docs for you to looks at. As for me, I bought extra Girl Scout cookies this year, just in case!! ;) +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.