Memory Error Issue - Need some ideas I am fresh out

[Jeff Harrison]

> From: Nancy Palmquist <nlp at vss3.com>
>To: filePro Mailing List <filepro-list at lists.celestial.com> 
>Sent: Tuesday, December 6, 2011 12:42 PM
>Subject: Memory Error Issue - Need some ideas I am fresh out
> 
>We are installing a big update for FastEMC and so far one customer has 
>this issue.
>
>After saving a claim (record) it runs a CALL table to validate the 
>data.  Same for everyone.
>
>On this customer it crashes every time it hits the CALL table.
>
>If I have them call a different table first by running another option on 
>the claim, then the Validation CALL table works without the memory 
>error.  And on each claim after that it continues to work without 
>incident for new and updated claim records as long as they do not leave 
>rclerk.
>
>This same solution - does not work on a client just the server.
>
[snip]

I have been doing what you describe - calling a dummy table prior to the "real" call - for years.  Ever since you could do a call I suppose.  It seems to me that there was an old filepro bug - or a quirk if you will - that could cause a memory error upon a call if you did not do this.  Due to this it has become standard procedure for me to include the dummy call.

So I would leave the dummy call in there.  You mention that this solution does not work for the client - is that true if you try calling a different table?  Is there something about this particular table that is causing the memory error (or does every call fail)?  Perhaps it is the size of the table?  Does upping the -ty and -ty, -tf have any effect (probably -tf for call tables if I recall properly) ?   Does decreasing the size of the called table have any effect?

If it is something specific within the call table, you can test for this by successively cutting out parts of the table until it works - then add lines back in until you identify the culprit.

That is all that comes to mind at the moment.

Good Luck.

Jeff Harrison
jeffaharrison at yahoo.com
Author of JHExport and JHIMport