Oninit cdi / Archive
Talk to an expert →

4GL error -4339

Posted in 2006

Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Platform-Specific Issues, Versions, Editions & End-of-Life

alesak@gmail.com — — source: Usenet: comp.databases.informix

Hi there, I have very funny problem with 4GL, version 7.30, running on IDS 9.40 FC4, SparcV9 Solaris 8. Our non-interactive 4GL program (not modified for years) begun to fall with "4GL run-time error number -4339. 4GL has run out of data space memory". There is no C-functions calling, no nothing, and what's worse - it is undeterministic, I've tried to call that program hundred times and it has fallen for 99 times and passed once (somewhere in the middle). I've seen similar problems, announced here years ago, but none of them looked matching my conditions. I'd be glad for any suggestions, if you have an idea what it does, or what should I avoid. Alesak

↪ replying to alesak@gmail.com
Jonathan Leffler — — source: Usenet: comp.databases.informix

alesak@gmail.com wrote: > I have very funny problem with 4GL, version 7.30, running on IDS 9.40 > FC4, SparcV9 Solaris 8. Our non-interactive 4GL program (not modified > for years) begun to fall with > > "4GL run-time error number -4339. > 4GL has run out of data space memory". > > There is no C-functions calling, no nothing, and what's worse - it is > undeterministic, I've tried to call that program hundred times and it > has fallen for 99 times and passed once (somewhere in the middle). > > I've seen similar problems, announced here years ago, but none of them > looked matching my conditions. > > I'd be glad for any suggestions, if you have an idea what it does, or > what should I avoid. Programs don't start failing if you haven't changed anything, so you should look to see what has changed recently. Something has changed. Possibly a workload pattern, possible an environment variable, possibly the size of a data set, possibly something else. If you really can't identify either what changed or why it is failing, consider whether you can stop using shared memory connections to IDS. If that isn't it either, have you contemplated an upgrade to I4GL 7.32? With no C code of your own, that shouldn't be too painful. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/

Glossary