IRD weight management and Defined Capacity work fine. The problem comes with IRD and LPAR Group Capacity Limits (introduced in z/OS 1.8). The problem is when an LPAR Group is capped IRD stops adjusting weights. This is rather unfortunate as this is the time when a customer would most want IRD to adjust the weights within the limits of the LPAR Group Limit.
When a group of LPARs is capped the effect is the same as that group being out of capacity. That is there is more workload trying to run than the amount of capacity available. When this group cap is set some LPARs may be running low importance work consuming CPU time in the group. Simultaneously other LPARs may really be feeling the capacity stress and these may stop running importance 4, 5 and discretionary work. At this point is would be great if IRD would move capacity away from the low importance work in the group, to the LPARs that are impacting more important work. This is what IRD weight management would do. You can use both of these capabilities together, but you must understand that weight management stops, as it is at the time the group cap "turns on". Al Sherkow, I/S Management Strategies, Ltd. Consulting Expertise on IBM Workload License Charges (WLC), LPARs and LCS Software Seminars on IBM Mainframe Software Pricing +1 414 332-3062 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
