[Info-vax] Process memory settings

[John Reagan]

"JBloggs" <JBloggs at acme.com> wrote in message 
news:487c8514hdtod210telijkvttqp2b8gdas at 4ax.com...
>
> This suggestion might be along the lines of throwing stuff
> at the wall, and seeing what sticks, but you might look at what
> files are getting opened (and closed?)  during the compile.
> ($set watch/class=mumble  FILE)
>
> I'm thinking along the lines of a recursive include, or
> whacked directory and/or search path.
>
> One project I worked on in the distant past, (written in C)
> MMS often had in excess of 8000 files open (peak),
> most of them were  include files.  (COBOL != C. but you get the idea)
>

That wouldn't change based on the optimization level.  Any COBOL COPY 
statements (aka #include) would be in the front-end and independent of /OPT. 
Plus since you can't have nested COPYs in our COBOL, it is almost impossible 
to really open that many COPY files.  And you'd hit your CHANNELCNT limit 
before you'd run out of memory like this.

John