Thermo writes :
>Get a life!  Who compiles in batch anymore?  So what if the

>production system comes to a screeching halt whilst I compile

>that 10,000 line monster program?  Users are used to waiting.

>If they complain too much I just put their session in the DQ.

>That'll teach 'em! :-)

   Sorry, but quite a few production houses still do compiles in
   batch.  Reason being is that it puts a cap on resources, in particular
   CPU and memory.  Programmers (myself included)  are notorious
   for grabbing said resources for their own greedy uses, and using
   well-documented job streams for launcing compiles can evenly
   distribute resources in a both production/developement environment.
   Likewise, the use of good spoolfile management systems can
   deliver excellent analytics of job output in a timely manner to
   any of those on-line, while keeping system resources at a premium.


>Sorry, I'm headed to El Paso again and am getting a little

>testy.



>Jim Phillips

   Boy, I can see the reason for your temperment.  I went through El Paso
   Del Norte recently (on my way home for a snowed-in Albuquerque), and
   was it a mess!  I'll make sure never to book through there again.

   Craig V. ([log in to unmask])