Online&4GL-Upgrade related probable problems?
I'm having trouble finding info on potential upgrade related problems. Our Department will upgrade several Informix products and I'm attempting to anticipate what action our development team will have to take. The new versions are: Product Old Ver New Ver ------- ------- ------- Online 7.23.UC1 7.30.UC7-2 SQL/4GL 6.04.UC2 7.20.UC7 ESQL ? This will become Client SDK 2.20.UC2-1 (inclds Java connectivity) I've heard that some programs will not be named the same after the upgrade. Does anyone know if we'll have to: A) make code changes, or B) re-compile everything, or C) cross our fingers and do nothing until a problem arises? Elijah -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
elijahtx@my-dejanews.com wrote: > > I'm having trouble finding info on potential upgrade related problems. Our > Department will upgrade several Informix products and I'm attempting to > anticipate what action our development team will have to take. The new > versions are: > > Product Old Ver New Ver > ------- ------- ------- > Online 7.23.UC1 7.30.UC7-2 > SQL/4GL 6.04.UC2 7.20.UC7 > ESQL ? This will become Client SDK 2.20.UC2-1 > (inclds Java connectivity) > > I've heard that some programs will not be named the same after the upgrade. I can't immediately think of any name changes, which isn't the same as saying there are none. > Does anyone know if we'll have to: > A) make code changes, or B) re-compile everything, or C) cross our fingers and > do nothing until a problem arises? A applies if you want to use new features, of course, but shouldn't apply otherwise. B applies. You will need to recompile all your I4GL code unless you're a much braver (more foolhardy) person than I am. You should expect to recompile your ISQL forms and reports, though this should be redundant. I'd expect to recompile any ESQL/C programs you wrote. C: problems will happen immediately if you try to run a 6.04 I4GL program against a setup with only the 7.2 I4GL and 7.3 IDS -- the message files were relocated between 6.0x and 7.2x, courtesy of GLS support. When you upgrade, install the new software in a new directory. Don't try to overwrite the old one. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>
Hello Jonathan, I certainly appreciate you quick response. I have 2 related questions regarding you answers: 1) You said: "problems will happen immediately if you try to run a 6.04 4GL program against a setup with only the 7.2 I4GL and 7.3 IDS -- the message files were relocated between 6.0x and 7.2x, courtesy of GLS support." My question: Can you please tell me the 'old' and the 'new' locations of these message files? Are they Informix 'error' message files? 2) You said: "When you upgrade, install the new software in a new directory. Don't try to overwrite the old one." My question: What are the consequences of of overwriting the same directory? Thanks! In article <371177A4.3961@earthlink.net>, jleffler@earthlink.net wrote: > elijahtx@my-dejanews.com wrote: > > > > I'm having trouble finding info on potential upgrade related problems. Our > > Department will upgrade several Informix products and I'm attempting to > > anticipate what action our development team will have to take. The new > > versions are: > > > > Product Old Ver New Ver > > ------- ------- ------- > > Online 7.23.UC1 7.30.UC7-2 > > SQL/4GL 6.04.UC2 7.20.UC7 > > ESQL ? This will become Client SDK 2.20.UC2-1 > > (inclds Java connectivity) > > > > I've heard that some programs will not be named the same after the upgrade. > > I can't immediately think of any name changes, which isn't the > same as saying there are none. > > > Does anyone know if we'll have to: > > A) make code changes, or B) re-compile everything, or C) cross our fingers and > > do nothing until a problem arises? > > A applies if you want to use new features, of course, but shouldn't > apply otherwise. > > B applies. You will need to recompile all your I4GL code unless > you're a much braver (more foolhardy) person than I am. You should > expect to recompile your ISQL forms and reports, though this should > be redundant. I'd expect to recompile any ESQL/C programs you wrote. > > C: problems will happen immediately if you try to run a 6.04 I4GL > program > against a setup with only the 7.2 I4GL and 7.3 IDS -- the message > files were relocated between 6.0x and 7.2x, courtesy of GLS support. > > When you upgrade, install the new software in a new directory. > Don't try to overwrite the old one. > -- > Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) > Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN > #include <disclaimer.h> > > -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
elijahtx@my-dejanews.com wrote: > > Hello Jonathan, > > I certainly appreciate you quick response. I have 2 related questions > regarding you answers: > > 1) You said: "problems will happen immediately if you try to run a 6.04 4GL > program against a setup with only the 7.2 I4GL and 7.3 IDS -- the message > files were relocated between 6.0x and 7.2x, courtesy of GLS support." My > question: Can you please tell me the 'old' and the 'new' locations of these Old: $INFORMIXDIR/msg New: $INFORMIXDIR/msg/en_us/0333 > message files? Are they Informix 'error' message files? 2) You said: Yes Informix message files for errors and other messages also. "When > you upgrade, install the new software in a new directory. Don't try to > overwrite the old one." My question: What are the consequences of of > overwriting the same directory? Dire. It is just not worth the minor niggling problems you will spend days solving. Also you will have to go through reinstalling the original software if for some reason you need to back down to the older versions. Install in a different directory and you just have to change INFORMIXDIR and bounce the engine to back down the IDS version or change the path and shared library path to back down the 4GL version. [SNIP] Art S. Kagel