Re: Porting from SCO 3.2.4 to SCO ODT 5.0.4

On Thu, 13 Aug 1998 01:12:23 +0100, David Williams <djw@smooth1.demon.co.uk> wrote: >In article <6qt405$7tj$1@news.xmission.com>, Ciaran Kelly ><Ciaran.Kelly@rte.ie> writes >> >>Hi, >> >>I have a problem porting an application compiled for SCO 3.2.4 to SCO ODT >>5.0.4 >> >>The system is a PC running Informix SE 5.0 and 4gl 4.1 "C" runtime. >> >>I have copied the informix se and 4gl rt files over to ODT and the database >>seems to work fine - dbaccess works and is able to successfully query the >>db. >> >>When I copy the 4gl binary over, it works until the second iteration of a >>fetch .. update loop and then crashes with a coredump. The corefile just >>says that there was a bad memcpy at an address. No trace information. >> >>Is ODT binary compatible with SCO? ODT seems to use ELF format binarys > > No, different kernelx = different system call interface. But SCO 3.2.4.x and SCO 5.0.x are supposed to be upward compatible at this level. >>while SCO uses COFF. >> >>If this isn't a binary compibility problem, then maybe it's to do with the >>ISAM version of SE - the database interfaces with a C-ISAM system. Does > >>anyone know what C-ISAM versions are in each release of SE? >> > NO but they are not compatible across OS's or Os versions...get the >right verxion for your version of the OS. This is right and allways what one should do. However we have a version of SE 5.x and 4GL 4.x that we originally bought for Interactive Unix for our own development work. We moved this to SCO Unix 3.2.4.2 and later to 5.0.4 and it have worked without a hitch all the time. We can both run the original binaries, even those from the Interactive Unix time and those created on 3.2.4.2 on 5.0.4 and we can recompile. We now even recompile on 5.0.4 and install the binaries on 3.2.4.2 without any problems. There are no problems at the C-ISAM level as to incompatibilities with your dataformat or call interface due to different versions, as this product is included with the engine and copied over with it. Despite this there may be incompatibilites at the level David is saying with the exact version of your SE and 4GL you have. It may be that Informix in this exact product used some special kind of os-call or whatever that doesn't work exactly the same way on 5.0.4. I can't tink of any other problems that may cause the behaviour you see. The only possible solution may be to recompile your 4GL code under 5.0.4. That may solve this problem. It still remains that it may fail in some other area though despite our success in doing a similar thing. There is no other real solution than to get an upgrade. Nils Myklebust NM Data AS Norway E-mail: Nils.Myklebust@nmdata.com FAQ at: http://www.iiug.org/techinfo/faq/faq_top.html (Now with ODBC info under "Third party products".)