The 'Y to K' Problem

I have completed the months of work for this project on time and under budget. Even though I had open heart surgery, I never skipped a day. I have gone through every line of code in every program in every system. I have analyzed all databases, all data files, including backups and historic archives, and modified all data to reflect the change.

I am proud to report that I have completed the "Y-to-K" date change mission, and have now implemented (via dial-up from home) all changes to all programs and all data in production, to reflect the following new standards:

                      Januark, Februark, March, April, Mak, June, Julk,
                      August, September, October, November, December
                                        and...
                      Sundak, Mondak, Tuesdak, Wednesdak
                      Thursdak, Fridak, Saturdak

I trust that this is satisfactory, because to be honest, none of this Y to K problem has made any sense to me. But I understand it is a global problem, and I was glad to help in any way possible.  And what does the year 2000 have to do with it?  Speaking of which, what do you think we ought to do next year when the two digit year rolls over from 99 to 00?

I'll await your direction.

Subscribing to the DB2 List

The DB2 list is a great (and free!) e-mail forum for exchanging information related to DB2. You are able to post a question to the list (nearly 2,000 subscribers from around the world), or just look at the messages from everyone else. This is an active list so expect a lot of messages.

For more details see the RYC page.

(Thanks to Patricia Aylsworth of Wells Fargo for pointing this out!)
 

Home