Hello Rick, > Since you've not closed any of the files after processing, I suspect you > are running out of file handles, not memory.
Thanks! I discounted this idea as the output stream to the log file is the very first file stream I open and don't close it. I left them open for two reasons: 1) I thought Windows 10 allowed for 10K+ file handles. 2) Closing them is time consuming. Right now the read loop takes about 90 seconds on an Samsung 850 EVO drive and adding the closes I suspect will add about a minute to 90 seconds. Of course this is a small price to pay to keep the system / program working, but if not really necessary . . . Is there a way to - in Windows 10 - determine if the handle issue is the problem external to ooRexx? Thank you, Bertram Moshier
------------------------------------------------------------------------------
_______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
