Please Help With Y2K Problem
This should be an easy one for one of you Informix techies. I have recently been given responsibility for a small database that uses an Informix-SE engine (ver 4.10.UC2) and runs on an SCO OS5 box and am attempting to test it for Y2K compliance. I have discovered that dates inserted or referenced with two digit centuries are interpreted by the engine as 1900 even if the system date is 2000. Is there a setting or environment variable that is causing the system century to not be the default? Any ideas on this will be greatly appreciated. Sent via Deja.com http://www.deja.com/ Before you buy.
Unfortunately, DBCENTURY will not work with this version of the engine. Also of note, the Y2K statement released by Informix boils down to "You put in a four digit year and you will get the same four digit year out". That one covers all of their products, I believe. The 2 year->4 year conversion may have one or two 5.X abilities but it really doesn't come into effect until 7.2 and is buggy until the most current version of 7.31. Someone please correct me if I am wrong but this is what I have been thinking the whole time. wtmckown@my-deja.com wrote: : This should be an easy one for one of you Informix techies. I have : recently been given responsibility for a small database that uses an : Informix-SE engine (ver 4.10.UC2) and runs on an SCO OS5 box and am : attempting to test it for Y2K compliance. I have discovered that dates : inserted or referenced with two digit centuries are interpreted by the : engine as 1900 even if the system date is 2000. Is there a setting or : environment variable that is causing the system century to not be the : default? Any ideas on this will be greatly appreciated. : Sent via Deja.com http://www.deja.com/ : Before you buy. -- Rob Wilson rwilson@ntsource.com
Informix's web site has extensive web pages concerning the Y2K issue. Please check out http://www.informix.com Click on "Year 2000" Click on "Product Readiness" On that page there are three tables which define the levels of support for Y2K as well as a listing on which products are Y2K compliant. wtmckown@my-deja.com wrote: > This should be an easy one for one of you Informix techies. I have > recently been given responsibility for a small database that uses an > Informix-SE engine (ver 4.10.UC2) and runs on an SCO OS5 box and am > attempting to test it for Y2K compliance. I have discovered that dates > inserted or referenced with two digit centuries are interpreted by the > engine as 1900 even if the system date is 2000. Is there a setting or > environment variable that is causing the system century to not be the > default? Any ideas on this will be greatly appreciated. > > Sent via Deja.com http://www.deja.com/ > Before you buy. -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================
The gist of your answer is correct. 4.10 has no clue about DBCENTURY and behaves exactly as it is documented to behave; if a (1 or) 2-digit year is entered, 1900 is added. Period. Version 4.20 tools, 5.10 servers have DBCENTURY in them. Version 7.20 upwards has DBCENTURY. I am not sure what bugs are present in 7.30 or 7.24 that Rob is referring too; I would not be vastly worried about those versions. However, I have a blinkered view of life; I use /dev/null as my archive device and there may be some archive-type problems. They aren't strictly DBCENTURY issues, but they are Y2K ones. There is a difference (IMNSHO). Rob Wilson wrote: > Unfortunately, DBCENTURY will not work with this version of the > engine. Also of note, the Y2K statement released by Informix boils > down to "You put in a four digit year and you will get the same four > digit year out". That one covers all of their products, I believe. > The 2 year->4 year conversion may have one or two 5.X abilities but it > really doesn't come into effect until 7.2 and is buggy until the most > current version of 7.31. > > Someone please correct me if I am wrong but this is what I have been > thinking the whole time. > > wtmckown@my-deja.com wrote: > : This should be an easy one for one of you Informix techies. I have > : recently been given responsibility for a small database that uses an > : Informix-SE engine (ver 4.10.UC2) and runs on an SCO OS5 box and am > : attempting to test it for Y2K compliance. I have discovered that dates > : inserted or referenced with two digit centuries are interpreted by the > : engine as 1900 even if the system date is 2000. Is there a setting or > : environment variable that is causing the system century to not be the > : default? Any ideas on this will be greatly appreciated. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.62 -- see http://www.perl.com/CPAN #include <disclaimer.h>
Jonathan Leffler (jleffler@earthlink.net) wrote: : I am not sure what bugs are present in : 7.30 : or 7.24 that Rob is referring too; I would not be vastly worried about those : versions. I am thinking of some reports including that hpl does not honor DBCENTURY and (my favorite) DBCENTURY does not work with 1 digit years. However, I cannot remember which versions these are. The general belief where I am currently stationed is pretty much that you should not rely on the DBCENTURY setting and should use a four digit year (which will always work).