Shane:
I appreciate the reference and have now read portions dealing with
capping. It just never quite got to the point of telling for certain
how PR/SM cuts off service, but it hints at it being a non-dispatch of
an LCP by a real CP.
I was not surprised by capping extending into lunch. What
Esteemed colleges:
A topic that has occasionally graced IBM-MAIN for over a decade is
capping, and technology keeps changing so as to adjust the answer.
Having newer technology, we now have a handful of capping issues, and
IBM is coming up with new microcode (about now as I recall) to manage
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 06/13/2007
12:37:38 PM:
Ordinarily, as PR/SM dispatches CPs to LPARs, a Logical CP may have a
task dispatched to it, but beneath it, it has no physical CP.
Milliseconds later, the CP may well be back and the task actually
runs.
But
All of these statements are true enough. But the one that makes the day
is the one that says 'but I was able to show management ... and save'.
Performance issues, of course, serve a good supporting role.
A boss somewhere was recently heard saying of a proposed penalty box 2nd
mainframe: 'And
Esteemed MVS colleagues:
We have a 2-LPAR, both MONOPLEX, machine environment today that has only
the sysprogs using the 2nd LPAR. z/OS 1.4 soon to be 1.6, then 1.8. It
has DASD HCD-defined as shared, and we have been very careful. Our GRS
effort of a few years ago was not pursued.
But now we
5 matches
Mail list logo
