Re: 5.0 Upgrade Path

>Date: Wed, 2 Dec 92 10:22:31 +0800 >From: Richard Ridley <uunet!sin-pss.DHL.COM!rridley> >Subject: 5.0 Upgrade Path >X-Informix-List-Id: <list.1664> >We currently have about 40 sites running Informix 4.0 Front-end and >4.1 Back-end (Both On-line and Standard Engine). Our problem is: >We can follow a 'gradual' upgrade path, eventually getting to 5.0 >Front-and-back end, or we could go straight to 5.0. The way we see it >our options are : > 4.0 Front ____(A)____\\ 4.1 Front ___(B)____\\ 4.1 Front > 4.1 Back / 4.1 Back / 5.0 Back > > | | > |_______(D)__________\\ 5.0 Front /________(C)_____| > / 5.0 Back \\ Comment: 5.0 Front does not exist yet, so 4.1 Front and 5.0 Back is your current target. Comment: You have missed the following upgrade route 4.0 Front ____(E)____\\ 4.0 Front ___(F)____\\ 4.1 Front 4.1 Back / 5.0 Back / 5.0 Back The combination of 4.00 Front and 5.00 Back is supported as far as I am aware. >Which steps require re-coding and/or re-compiling in order to be 'safe'? If you are using RDS, when you change from 4.0 to 4.1, my experience suggests that you should recompile all the I4GL source -- the p-code versions are different and it is safest not to try mixing them. >What problems are we likely to encounter at each stage ? You should have no major problems. The error handling in 4.10 reverts to 1.10.03 style unless you use the directive WHENEVER ANY ERROR STOP/CONTINUE However, this is simpler to handle than the change from 1.10.03 to 4.00 was; in fact, no action is normally necessary. >If we have to re-compile for stage A and/or C, then it would seem >obvious that we may as well re-compile for stage D instead - is this >true or are there some hidden implications ? You can't do stage D or C yet due to products not being available. Yours, Jonathan Leffler (johnl@obelix.informix.com) #include <disclaimer.h>