Re: 4GL Question

Hello Andrew! Thanx for your answer. > > > Basically, you are very deep in smelly brown stuff. I think your right... A .4ge cannot be > converted back to 4GL code unless you are an absolute legend with assembly > language; or a 15 year old hacker/virus author... A .4gi could be converted > back to .4gl code; in fact I once made some inroads into such a project but > never completed it - it was more of a fun project that nobody would pay the > development costs of. The developer deleted all .4gl and 4.gi files. I can see parts of the code with an hex-editor. But its not enough to restore the code. > Here's a ritual that will probably work, assuming of course that you are > still using the same processor family, for example SCO to SCO or HP to HP. > Stop reading now if you have changed the machine type. I'm assuming that you > are installing 7.?? 4GL and engines, but anything > 4.?? is relevant to the > discussion. > > 1) Find out exactly what the ?? is in 4.??. If it's 4.10 and above then you > should be in business. Ok. Its 4.10.UE2 on a HP-UX 10.01 machine. The db is 4.00.UH2 (SE). The new is 7.20.UE1 RDS on a HP-UX 10.20 machine. The db is 7.30.UC7 (Online). > > 2) When you run your .4ge program, export this shell variable: > > SQLEXEC=$INFORMIXDIR/lib/sqlrm sqlrm don't exist here on the old server. On the new machine a message told to install an 4GL runtime license. I only have an RDS there. I think its not good to install an old i4gl to an new r4gl. So will read my manuals well and write new 4gl files :-(. (Sh.., my education was more than one old and I don't use 4GL... Best regards. Dirk Emmermacher

Dirk, Do you have any really old backup tapes on the old system that might have the source code on them? Might be worth someone's time to look thru them. Do you have any LEGAL recourse against the idiot savant developer who deleted the files? Perhaps you could contact him and see if he has a copy of the files you could have/re-purchase? Food for thought. Otherwise you can get REALLY good at Strings or contact INFORMIX directly and see if they have a tool or expertise to do the impossible. Rob Vorbroker robv@iiug.org Dirk Emmermacher <NDSTURNERBUND@t-online.de> wrote in message news:933s9m$pf9$1@news.xmission.com... > > Hello Andrew! > > Thanx for your answer. > > > > > > Basically, you are very deep in smelly brown stuff. > > I think your right... > > A .4ge cannot be > > converted back to 4GL code unless you are an absolute legend with assembly > > language; or a 15 year old hacker/virus author... A .4gi could be converted > > back to .4gl code; in fact I once made some inroads into such a project but > > never completed it - it was more of a fun project that nobody would pay the > > development costs of. > > The developer deleted all .4gl and 4.gi files. I can see parts of the > code with an hex-editor. But its not enough to restore the code. > > > > Here's a ritual that will probably work, assuming of course that you are > > still using the same processor family, for example SCO to SCO or HP to HP. > > Stop reading now if you have changed the machine type. I'm assuming that you > > are installing 7.?? 4GL and engines, but anything > 4.?? is relevant to the > > discussion. > > > > 1) Find out exactly what the ?? is in 4.??. If it's 4.10 and above then you > > should be in business. > > Ok. Its 4.10.UE2 on a HP-UX 10.01 machine. The db is 4.00.UH2 (SE). > The new is 7.20.UE1 RDS on a HP-UX 10.20 machine. The db is 7.30.UC7 > (Online). > > > > 2) When you run your .4ge program, export this shell variable: > > > > SQLEXEC=$INFORMIXDIR/lib/sqlrm > > sqlrm don't exist here on the old server. > On the new machine a message told to install an 4GL runtime license. > I only have an RDS there. I think its not good to install an old i4gl to > an new r4gl. > > > So will read my manuals well and write new 4gl files :-(. (Sh.., my > education was more than one old and I don't use 4GL... > > Best regards. > > Dirk Emmermacher > >

Dirk Emmermacher wrote in message <933s9m$pf9$1@news.xmission.com>... > >sqlrm don't exist here on the old server. > Yup - you won't find it on the old machine because sqlrm is a new concept from the 7.XX engines. It allowed the 4.XX tools to work with their expected $SQLEXEC - or at least, with something pretenting to be sqlexec or sqlturbo. >On the new machine a message told to install an 4GL runtime license. >I only have an RDS there. I think its not good to install an old i4gl to >an new r4gl. > If you follow the ritual of loading the 4.10 4gl runtime, then all the 7.XX stuff in proper order then you will have a clean system. The complaint about "install a 4GL runtime licence" means that some 4.10 files are not found. Now I know from experience that this is merely because of some "missing" 4.XX files in the msg directory and a few other files that have been moved around by informix - mainly to annoy people I think? No, really, they did it to enable better support of GLS and so on, so It's A Good Thing. When you load the 4.10 stuff then all it's files (well, all the important stuff for you) will be there in the proper place, and then when you install the 7.XX stuff all their files will be in their expected place, and it should all work like it was born to run. But don't expect to compile 4.10 programs etc without a bit more work. That takes a bit of extra effort, and one that you obviously don't need to go into. Getting a single running program is your goal here. I have every confidence in the sequence of installs, because I've done it several times on several machines, covering a few different platforms. Remember: the last cpio or tar wins, and that's the most important thing for ensuring that the 7.XX stuff is working properly. Extra files hanging around that are not relevant to 7.XX will not hurt 7.XX but will allow 4.10 to work. Go back to my first e-mail and follow the sequence. Of course, you will: 1) Archive the engine and stop it on the machine you choose to install. 2) Take a copy of your $INFORMIXDIR or start a fresh one. 3) Test thoroughly on another machine before putting it onto a critical system with a critical database. I'm afraid warranty cannot extend thru this newsgroup, so make sure you protect your arse while you are learning the tricks.