davek@informix.com (Dave Kosenko) writes:
>In article <CLqs49.JE0@group1.com>, karla@group1.com (Karla Leibowitz) writes:
>|> : However, if you are installing an Informix tool which is older
>|> : (lower version number) than any other Informix tool you did install
>|> : previously, these ".iem" files are simply WRONG. The newer ones are
>|> : silently overwritten with the old versions.
>|> It means reinstalling the
[ some text deleted ]
>Actually, it doesn't even have to be that complicated. As pointed out
>in your included text, it is only the .iem files that cause the conflict.
This included test was written by me, btw.
>I know sql.iem is one of the primary offenders (it contains the set explain
>text) but there may be a couple more. If you just make a copy of the .iem
>files common to both the server and tools before your install, then copy
>them back after, you should be fine. The following is the list (circa 5.0)
>of .iem files that come with tools (4gl, ISQL) that also come with the
>server:
> msg/dbload.iem
[ very useful list of .iem files - thank you ! - deleted ]
That's exactly what I did. I did install the run-time version, again,
in the right order on a different system and compared these .iem files.
Than I copied the ones which differ to the real system and that's it.
Of course, I did remove the temporary installation of the run-time system
from the other system, after that change.
If I didn't do the second installation I had to travel to the customer,
re-install everything, etc. instead of just comparing the files (date, size
and checksums) and sending just the right ones (after compression) via the
network to the customers site. Now, it works.
Norbert.
--
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52 FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt