SQL Memory problem. Maybe?

["George Alderton" <galderton@xxxxxxxxxx>]

Hello all,

  I'm stuck.

  I have an SQLRPGLE program that has been working for months.  This month
if failed.

  This is a report program with  a LOT of SQL and some very LARGE arrays.
It prints a report for either a single warehouse or for all warehouses based
on a parameter.  This month when it was run, it stopped after printing four
pages.  It'd didn't crash, it just stopped running.  It was using CPU but no
I/O, and, the call stack wasn't there.

So, I thought some goofy data had caused a run away query.  I ran the report
selecting the suspected warehouse and it worked fine.

In debug, I traced to the point where it was about to do the query, went to
the command line, started interactive SQL and ran the query manually and
that worked fine.  I returned to the debug session and tried to run the
query and it just sat there.

Here's where it gets strange, for some reason, I can't remember why, I made
some of the larger arrays smaller.  I ran it in debug again. This time the
query worked, but the next query hung up.

So, it seems to be memory related.  As far as I can tell nothing has
changed.  But I know something must have changed somewhere.

Any ideas?

TIA,

   -- George


--
George A. Alderton IV                george@wstick.com
Walkingstick Software, Inc.      http://www.wstick.com
--
When people agree with me I always feel that I must be wrong.
   - Oscar Wilde

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---