DG>
  >   How do we extend the number of files that may be opened?
DG>

  If you are using fopen() from the C Library, then you are limited by
  your C language vendor's implementation of the Standard C Library.
  Many implementations use a fixed-length table of FILE structures, and
  thus place an absolute limit on the number of files that can be opened
  via fopen() at any one time.

  If you are using the AT&T iostreams library for your file access,
  there is even more scope for variation, since iostreams can either be
  implemented over a POSIX.1 layer, or directly over the native system
  API.  In the former case (as is done by Borland C++, for example), the
  number of open file streams is affected by the number of avaialble
  POSIX.1 file descriptors available (which in Borland C++ is again
  limited by the size of a fixed table built into the C Library).

  Some vendors, such as Watcom, do not hard code such limitations into
  their C libraries.  The Watcom C library provides a call (I believe
  that the name is __growhandles -- it's in the manual anyway) to
  increase the number of file handles available via the C library, and
  at the same time to ensure that the maximum number of file handles in
  the underlying O/S for that process is increased to match.

  However, the limit of the native system API (i.e. DosOpen,
  DosCreatePipe, DosCreateNPipe, and so forth) defaults to 50 and is
  adjustable, via the DosSetRelMaxFH system call (read the on-line
  documentation in your OS/2 Developers' Toolkit), up to 32767 open file
  handles per process.

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 3.00