limits on called program's variable and/or array space?

[Richard Kreiss]

I have operated under the impression that an array was global. 

I think that *clerk.exe and *report.exe allocate memory for arrays and variables at the start of the run. This is why it is important to tokenize a processing table with the auto processing table to be used. 
When no auto table is “used” the tokenize with a non-existent auto table name. That will allow memory to be allocated correctly. 

One could dim an array at @once processing or a a sub-routine that only runs at the start of processing. That avoids the program hitting a dim or declare more the once. 

Only on of the FilePro programmers can answer the question of how much memory the executables can access. I would expect the the 64bit version will eventually be able to make better use is available memory. 

Richard
Sent from my iPhone

> On Jul 16, 2018, at 9:00 AM, Richard Veith via Filepro-list <filepro-list at lists.celestial.com> wrote:
> 
> I appreciated all the comments and suggestions, but after much testing I discovered that there was one variable in the called program that did not have a declared size (even though I thought I had taken  care of that), and fixing that resolved the problem.  None of the other suggestions would get the programs to run successfully without that one change.  (As noted in the original post, there is a calling program and a called program, and it was the called program that was causing the abort when the pair of programs was run on all records in a 22 million record database, producing only a Windows 7 message saying "dreport.exe has stopped working" when about 80% through the database.)
> 
> But I still have some questions:
> 1.  Is PFFORMTOKSIZE the only env variable that affects the size of space available for a called program's variables?
> 2.  If so, is there an upper limit other than 999,999 in FilePro 5.7.00D9? (Because my varying the size from 200000 up to 990000 had no impact).
> 3.  Do the calling programs and called programs share a limited amount -- and the same overall limited amount -- of FilePro-reserved memory regardless of overall RAM?   And does more reserved for the calling program mean less reserved for the called program?   (On our standalone PC with 16 GB of RAM and no other user programs running, there was always about 12 GB of free RAM whether these two FilePro programs were going to abort or not.) 
> 3.  One of my tests was to change the two arrays (not mapped to any record fields) in the called program from local to global, making sure I clear them at the start of each record's processing.  This did not affect the abort/no-abort issue, but it had a big impact on processing time.   When the arrays were NOT global it added over an hour to overall processing time.  Is that because the arrays get set up once, rather than 22 million times?  Would the same thing be true for dummy variables?
> 
> Thanks again for any comments or suggestions.
> Rich   
> 
> -----Original Message-----
> From: Richard Kreiss [mailto:rkreiss at verizon.net] 
> Sent: Friday, July 06, 2018 5:14 PM
> To: Richard Veith <richard.veith at smrresearch.com>
> Subject: RE: limits on called program's variable and/or array space?
> 
> I realize that many have responded earlier. But one thing came to mind this afternoon, have you considered that there may be in issue with disk space.
> 
> filePro creates a temp file with data for the output.  I have some reports with 8 sort levels which can create a fairly large temp file.  The size depends on the size of the fields being indexed.  Just take a look at the size of indexes.
> 
> If ACL is being run on a Windows machine, one variable is the amount of space and user can use,  this may be causing an issue if the limit is reached.
> 
> Just something more to think about.
> 
> 
> Richard Kreiss
> GCC Consulting
> 
> 
> 
>> -----Original Message-----
>> From: Filepro-list [mailto:filepro-list-
>> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Richard
> Veith via
>> Filepro-list
>> Sent: Tuesday, July 3, 2018 8:34 AM
>> To: Filepro-list at lists.celestial.com
>> Subject: RE: limits on called program's variable and/or array space?
>>