Re: DBCENTURY and Y2K

Allen It will be 1/1/2000. We found this indirectly from our Y2K testing. We get a feed with 2 digit years, which a Java program puts into one of our Informix databases. We had set the DBCENTURY in our environment but the Java program which used Intersolv's JDBC driver sees the environment variable only when its setup in the driver's configuration file, so it was not visible to the program. Setting the system date in the year 2000, we found the dates being inserted "correctly", ie 20xx. However, if we moved our system date to the 1999, the dates were inserted as 19xx. By setting the DBCENTURY=C inside the driver's config file, the dates were inserted correctly, ie 00 became 2000 and 99 became 1999. HTH Sujit allenj <allenj@ndr.com> on 12/30/99 07:16:57 AM Please respond to allenj <allenj@ndr.com> To: informix-list@iiug.org cc: (bcc: Sujit Pal) Subject: DBCENTURY and Y2K I am using 7.31.UC2 IDS. My DBCENTURY env var is not set. The manual says that, in this case, Informix will use the current century for 2 digit years. Depending on whom you believe, 2000 is either the last year of the 20th century OR the first year of the 21st century. (There was no year zero, so you could say that 2000 years will not have PASSED until Jan 1st, 2001). My question: If I leave DBCENTURY unset, and give Informix a date of 1/1/00 on Saturday, will it store 1/1/1900 or 1/1/2000???? Any help appreciated. allen