Ted,

What you are seeing is caused by the absence (never created) of a
particular patch in 6.0 pp2.  The symptoms you describe first appeared in
5.5 around pp4 or pp5.  A patch was created and the problem was resolved.
When we moved from 5.5pp7 to 6.0pp2 the problem reappeared because the 5.5
patch was not carried forward to 6.0.  I think it only causes 'problems'
for NBSpool for if you were to use SPIFF or would repeatedly 'text' the
spoolfile with NBSpool before each 'list all' you'd see that the
spoolfile's eof is more 'current'.

I contacted QUEST and the RC when I noticed the problem.  QUEST indicated
that they were not aware of any of their many sites that had moved to 6.0
of encountering the problem again, and the RC confirmed that the 5.5 patch
never went GR in the 6.0 release (I don't remember the reason).

Personally I feel that sites that are experiencing the problem are using
the 'work around' of re-texting the spoolfile and are living with it.  I
know that QUEST knows the patch in question and perhaps what is needed is
for more sites experiencing the problem  to 'chime in'.

Regards
Paul Christidis




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