We've just moved from a 5.5 system with 240M of memory to a 6.0 system with
768M.  Traditionally we would get in an watch the output spoolfiles of running
jobs with NBSpool's "l all wait" and we have fairly good response.  Now, if
we do that, we sometimes have long pauses between when something has been
written and when we see it.  In watching the $STDLIST, say, the job can now be
far ahead of where the $STDLIST says it is.

I'm conjecturing that this is due primarily to the significant decrease in
memory pressure.  Is that true?  Either way, is there anything we can do to
make "l all wait" once again useful as it was?

Thanks,
Ted
--
Ted Ashton ([log in to unmask]), Info Sys, Southern Adventist University
          ==========================================================
A topologist is one who doesn't know the difference between a doughnut and a
coffee cup.
                        -- Kelley, John
          ==========================================================
         Deep thoughts to be found at http://www.southern.edu/~ashted