Too Many Open Files (was Re: The CLOSE command)

[Jeff Harrison]

--- Tony Ryder <tryder at westnet.com.au> wrote:

> What about just using close or close filename before
> returning
> from a chained or called processing table.
> 
> Tony Ryder
> 
> 
> |There is a company that I used to work for that for
> |years has been getting these "Too many open files"
> |errors from time to time.  In fact certain
> processes
> |would get them all the time.  I could never figure
> out
> |why before, but it seems to make sense now.  The
> |original programmer there made extensive use of
> |chained and called processing tables.  There were
> many
> |lookups and re-use of lookup aliases.
> |
> |If anyone else is getting this error I would
> suggest
> |that they be on the lookout for this "feature"
> |
> |Perhaps a solution for this that fptech could
> supply
> |would be a PFCLOSEONCHAIN and a PFCLOSEONCALL
> |environment variable, and perhaps a CLOSEALL
> command. 
> |The CLOSEALL command would close all open files
> (via
> |lookups) if called without any arguments.  With
> |arguments, it would close all files associated with
> |the entire filepro file(s) specified.
> |
> |Jeff Harrison
> |jeffaharrison at yahoo.com
> 

That works fine unless you have multiple lookups that
re-use the same alias.  For example:

lookup fil = file1 k=ky i=a -nx
lookup fil = file2 k=ky i=a -nx
lookup fil = file3 k=ky i=a -nx
close fil

The above code only closes the open files from file3. 
I would like an option to close all of the open files
from lookups.

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The easiest and
fastest ways to generate code for filePro exports and imports.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com