Informix 4.1 and Y2K
The original poster found that Informix 4.1 turns a two-digit year such as 01/01/00 into 1900 and asked whether upgrading was the only fix. John Carlson said to enforce four-digit year entry or upgrade; DBCENTURY worked on 4GL 7.20. Jonathan Leffler confirmed the 1900 behavior and suggested 4.2 I4GL/ISQL with 5.10 OnLine/SE, or 7.2x I4GL with 7.24-7.31. Pete said entering four-digit years works and he moved his app to a patchable UNIX.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Tracing old messages I found what I thought... Informix 4.1 does won't convert 01/01/00 to 01/01/2000 but 1900. Is it to upgrade Informix to higher version really the only solution? And if so - will my programs run under the higher version without ane problems? And what version would you suggest me (the main thing my chefs are interested in is money...) Magic. --== Sent via Deja.com http://www.deja.com/ ==-- ---Share what you know. Learn what you don't.---
See below . . . maga@mailbox.sk wrote: > > Tracing old messages I found what I thought... Informix 4.1 does won't > convert 01/01/00 to 01/01/2000 but 1900. Is it to upgrade Informix to > higher version really the only solution? And if so - will my programs Unless you enforce keying a 4 digit year at the program level, you'll need to upgrade. We're on 4gl 7.20.ud6 and DBCENTURY works as expected. > run under the higher version without ane problems? And what version > would you suggest me (the main thing my chefs are interested in is > money...) > > Magic. > 4GL tightened it's error-trapping between 4.1 and 6.02. Other than that, it shouldn't be too bad. John Carlson Informix DBA WHSmith USA
maga@mailbox.sk wrote: > Tracing old messages I found what I thought... Informix 4.1 does won't > convert 01/01/00 to 01/01/2000 but 1900. Correct. If you read the 4.1 documentation, it says that 1900 is added to a 2-digit year. > Is it to upgrade Informix to > higher version really the only solution? Yes. > And if so - will my programs > run under the higher version without ane problems? And what version > would you suggest me (the main thing my chefs are interested in is > money...) Depends, but probably 4.2 I4GL/ISQL and 5.10 (or 5.11?) OnLine or SE. Nothing earlier than those, anyway. Or go to 7.2x I4GL/ISQL and 7.24 or even 7.30 or 7.31 OnLine (IDS, whatever it is called this week). -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>
<maga@mailbox.sk> wrote in message news:7henpq$9kt$1@nnrp1.deja.com... > Tracing old messages I found what I thought... Informix 4.1 does won't > convert 01/01/00 to 01/01/2000 but 1900. Is it to upgrade Informix to > higher version really the only solution? And if so - will my programs > run under the higher version without ane problems? And what version > would you suggest me (the main thing my chefs are interested in is > money...) > > Magic. > > > --== Sent via Deja.com http://www.deja.com/ ==-- > ---Share what you know. Learn what you don't.--- No. If you enter a 4-digit year it'll work. We've been looking at this for a while. Our app was put together a fair number of years back and put on a really stupid version of UNIX, not one of the regular ones. It then turned out the box wasn't compliant and the UNIX wasn't compliant. The supplier then decided the only way forward was to pay a REALLY stupid amount to them to upgrade to a later version of Informix. Anyway needless to say the app is going onto a standard UNIX, which can be patched, on the same versions of Informix. Hence our problem is cured, until some fool puts in a 2 digit year. The above was anonamised, I have no desire to be sued, but then again it'd be less than the six figure sum that our supplier wanted. -- Pete pete@viper.karoo.co.uk www.karoo.net/viper