I've read the referenced manual, and the SCRT tool appears to deal only
with the reporting aspect, and while that's important, it's not my main
I've read enough other related material that perhaps I can phrase my
question with more precision and correct terms.
With z/OS running directly in an LPAR: When the four-hour rolling average
MSU consumption is greater than the defined Capacity MSUs, the LPAR gets
soft-capped via Workload Manager interacting with PR/SM.
If z/OS is a guest of z/VM: It seems inappropriate, and perhaps not
possible, for WLM in z/OS to implement soft-capping of the z/VM LPAR. It
seems more appropriate for some WLM equivalent software at the z/VM level
to implement soft-capping of the z/VM LPAR.
What are the options (if any) in order to keep a z/VM LPAR within some
defined Capacity MSU's the way WLM does for a z/OS LPAR?
On Mon, 13 Feb 2006 14:21:41 -0500, David J. Chase
There are some items I don't know enough about yet to gauge the
- Workload Manager is used to throttle back the z/OS LPARS below a
specified 4 hour rolling average of CPU usage (for cost reasons).
I've never used Workload Manager, but wonder: (a) will it work if
z/OS is a guest of z/VM, and (b) if not, what would accomplish the
same thing? Setting SHAREs is obviously not up to the task because
we're talking about the whole CP side.
Unless all of the z/OS images on the machine (guest or LPAR) are at the
z/OS 1.7 level then running any z/OS guest under z/VM will cause the
software charges for the z/OS guests to be levied against the size of
the VM LPAR and not against the 4 hour rolling average utilization.
Please see Chapter 5 of SG24-6522-16 Using the Sub-Capacity Reporting
Tool (aka the SCRT User's Guide)for more information.
-- David J. Chase, WW zSeries Software Sales --
-- IBM 18th Fl, 11 Madison Ave, NYC, NY 10010 --