IDS Forum

RE: 4GL run-time error number -4339

Posted By: LARRY SORENSEN
Date: Wednesday, 10 March 2010, at 4:53 p.m.

In Response To: Re: 4GL run-time error number -4339 (Jonathan Leffler)

The load is handled by a separate process; each record is entered by a program one at a time and committed each time. Once the claim is in, the Traffic Cop moves the record along a series of Java programs; it is the final step in the services that spawns out the thread to a 4ge program.

The 4ge program reads data from the Informix database and creates a 4GL report (that is later printed and sent out. It updates one record in the one table which indicates that the report has been completed and saves a compressed copy of the report to the another table.

Each set of programs handles one record at a time and begins and commits work as appropriate. I believe that the problem arises when the process that calls the 4ge program continues on to the next record while the 4ge is still running. As a result we get a situation where multiple 4ge threads are running for different record reports and a wall might be hit; I don't know if the wall relates to just the Shared Memory limits or if it has to do with the number of open files being written to or some other limiting factor but once that wall is hit no more reports are created for a while. Then "magically" the reports start up again until the wall is again hit. So when you look at the first record table you see a number of entries where the record_id is set (indicating the report was created and saved to the correct table). Then there will be a series of records that don't have a record_id, then some with record_ids, and so one. So it appears that the original process continues to spawn out the threads but they are killed during or just before the 4ge program is run.

Any clearer? I know that was involved. I tried to leave it a little generic on purpose leaving off program and table names.

> To: ids@iiug.org
> From: jleffler.iiug@gmail.com
> Subject: Re: 4GL run-time error number -4339 [19304]
> Date: Wed, 10 Mar 2010 16:20:03 -0500
>
> On Wed, Mar 10, 2010 at 09:49, LARRY SORENSEN <lsorensen25@msn.com> wrote:
>
> > Another bit of information -
> >
> > The 4gl program inserts data into tables and calls and forks off a call to
> > another program that does further processing. It is usually quick, but if
> > the
> > data is too large, there may be a number of forked processes out there.
> > First,
> > could this result in the error message, and second, what parameters might I
> > need to adjust to overcome this limitation?
> >
>
> What form does the 'further processing' take?
>
> Specifically, does the forked process try to use the database?
>
> If so, you are going to have problems; connections are not for sharing
> between processes, and if you have two processes trying to use 'the same
> connection' then you run into problems which could easily include the error
> you are seeing.
>
> > Larry
> >
> > > To: ids@iiug.org
> > > From: lsorensen25@msn.com
> > > Subject: RE: 4GL run-time error number -4339 [19299]
> > > Date: Wed, 10 Mar 2010 11:54:47 -0500
> > >
> > > This is code that has been compiled. It ran just fine on the Solaris 5.6,
> > IDS
> > > 7.32 platform before we migrated. Apparently, parameters, etc. were set
> > > corrrectly and somehow missed during the migration. Now I am looking for
> > > something to tweak so that it will run as it did before the migration.
> > >
> > > Larry
> > >
> > > > To: ids@iiug.org
> > > > From: art.kagel@gmail.com
> > > > Subject: Re: 4GL run-time error number -4339 [19298]
> > > > Date: Wed, 10 Mar 2010 08:42:24 -0500
> > > >
> > > > There are suggestions in the output from "finderr -4339" for how to
> > help
> > > > resolve this problem. I also would look though at the code for this
> > module
> > > > to see if there are statements, forms, windows, etc. that have been
> > opened
> > > > and are no longer needed but have not been closed and freed.
> > > >
> > > > Is this Compiled 4GL (C4GL) or pcode 4GL (R4GL)?
> > > >
> >
> >
>
> > > >
> > > > On Tue, Mar 9, 2010 at 10:26 AM, LARRY SORENSEN <lsorensen25@msn.com>
> > wrote:
> > > >
> > > > > I am running on Solaris 5.10 and IDs 11.50. I have I4GL 7.32
> > > > >
> > > > > I would like some direction on what parameters that can be changed to
> > > > > alleviate this problem. There is plenty of memory on the server. I am
> > > > > currently checking into what program changes may have taken place,
> > but I
> > > > > need
> > > > > direction in the mean time.
> > > > >
> > > > > Error
> > > > >
> > > > > Program error at "eob.4gl", line number 192.
> > > > > SQL statement error number -406. --- Similar -406 errors are reported
> > > after
> > > > > this one in different lines of the application.
> > > > > Memory allocation failed.Date: Time: 22:36:55Date: Time: 22:36:55 --
> > at
> > > > > this
> > > > > point the errors start getting jumbled
> > > > > Program error at "eob.4gl", line number 192 Program error at
> > "eob.4gl",
> > > > > line
> > > > > number 192.
> > > > > SQL statement er.
> > > > > ror number -406.SQL statement error number -406.
> > > > > Memory allocation failed.
> > > > >
> > > > > Date: Time: 22:37:03
> > > > > 4GL run-time error number -4339.
> > > > > 4GL has run out of data space memory.
> > > > > Date: Time: 22:37:05
> > > > > 4GL run-time error number -4339.
> > > > > 4GL has run out of data space memory.
> >
>
> --
> Jonathan Leffler #include <disclaimer.h>
> Email: jleffler@earthlink.net, jleffler@us.ibm.com
> Guardian of DBD::Informix v2008.0513 -- http://dbi.perl.org/
> "Blessed are we who can laugh at ourselves, for we shall never cease to be
> amused."
> NB: Please do not use this email for correspondence.
> I don't necessarily read it every week, even.
>
> --001636b2b0304f2adb048178dc13
>
>
> *******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>

Messages In This Thread

• RE: 4GL run-time error number -4339
  LARRY SORENSEN -- Tuesday, 9 March 2010, at 10:26 a.m.
  • Re: 4GL run-time error number -4339
    Fernando Nunes -- Tuesday, 9 March 2010, at 10:37 a.m.
    • RE: 4GL run-time error number -4339
      LARRY SORENSEN -- Tuesday, 9 March 2010, at 12:16 p.m.
      • Re: 4GL run-time error number -4339
        Fernando Nunes -- Tuesday, 9 March 2010, at 12:33 p.m.
  • RE: 4GL run-time error number -4339
    Andrew Lennard -- Tuesday, 9 March 2010, at 5:35 p.m.
  • Re: 4GL run-time error number -4339
    Art Kagel -- Wednesday, 10 March 2010, at 8:42 a.m.
    • RE: 4GL run-time error number -4339
      LARRY SORENSEN -- Wednesday, 10 March 2010, at 11:54 a.m.
      • RE: 4GL run-time error number -4339
        LARRY SORENSEN -- Wednesday, 10 March 2010, at 12:49 p.m.
        • Re: 4GL run-time error number -4339
          Jonathan Leffler -- Wednesday, 10 March 2010, at 4:20 p.m.
          • RE: 4GL run-time error number -4339
            LARRY SORENSEN -- Wednesday, 10 March 2010, at 4:53 p.m.
            • Re: 4GL run-time error number -4339
              Art Kagel -- Wednesday, 10 March 2010, at 7:48 p.m.
              • RE: 4GL run-time error number -4339
                LARRY SORENSEN -- Thursday, 11 March 2010, at 12:26 p.m.
                • Re: 4GL run-time error number -4339
                  Art Kagel -- Thursday, 11 March 2010, at 4:12 p.m.
            • RE: 4GL run-time error number -4339
              mosserp@wellsfargo.com -- Thursday, 11 March 2010, at 6:43 p.m.
      • Re: 4GL run-time error number -4339
        Art Kagel -- Wednesday, 10 March 2010, at 1:54 p.m.
        • RE: 4GL run-time error number -4339
          LARRY SORENSEN -- Wednesday, 10 March 2010, at 3:59 p.m.
          • Re: 4GL run-time error number -4339
            Art Kagel -- Wednesday, 10 March 2010, at 5:47 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.