I4GL - Problems with Version 7.20
Hi everybody, We have the following configuration/equipment: SNI RM400-225 RISC machine, running fine, ReliantUnix 5.44 operating system, running fine, ReliantUnix CDSDEV 1.0C32 C compiler, doing its work, IDS 7.31.UC2AX4, meanwhile also running fine, I4GL 7.20.UD6, making problems (at run-time). We have compiled several different 4GL sources and ever an executable becomes bigger than about 4 MB in size we get an error 25588 (...cannot connect to Dynamic server...) at run-time of that executable. When we reduce the code so that such an executable becomes slightly smaller than that magical limit it will start first, i.e. connect to IDS, but later terminate unexpectedly with some 4GL error message concerning memory allocation problems. We started playing around with kernel parametes but that ended up in frustration. Then we changed I4GL from the current 7.20.UD6 to our former 6.04.UC1, recompiled and, voila, everything runs fine. What's wrong with Version 7.20 ? TIA Hartmut Marten
Hartmut Marten wrote: > Hi everybody, > > We have the following configuration/equipment: > > SNI RM400-225 RISC machine, running fine, > ReliantUnix 5.44 operating system, running fine, > ReliantUnix CDSDEV 1.0C32 C compiler, doing its work, > IDS 7.31.UC2AX4, meanwhile also running fine, > I4GL 7.20.UD6, making problems (at run-time). > > We have compiled several different 4GL sources and ever an executable > becomes bigger than about 4 MB in size we get an error 25588 (...cannot > connect to Dynamic server...) at run-time of that executable. When we reduce > the code so that such an executable becomes slightly smaller than that > magical limit it will start first, i.e. connect to IDS, but later terminate > unexpectedly with some 4GL error message concerning memory allocation > problems. > > We started playing around with kernel parametes but that ended up in > frustration. > > Then we changed I4GL from the current 7.20.UD6 to our former 6.04.UC1, > recompiled and, voila, > everything runs fine. > > What's wrong with Version 7.20 ? Shared Memory Connections? Try setting INFORMIXSHMBASE to a larger value. Most probably, the preferred address for the shared memory communication segment just happens to coincide with data allocated to store your ever growing program. Or use network connections. Or olipcstr connections. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v1.00.PC1 -- see http://www.perl.com/CPAN #include <disclaimer.h>