LPAR-level and group-level parameters

Name of the LPAR or capacity group that you want to add to the policy or subpolicy

This value must match the LPAR or capacity group name as defined to PR/SM.

Whether the name specified in the LPAR/Group Name parameter refers to an LPAR or capacity group

Possible values are L (LPAR) and G (group).

This parameter corresponds to the Type (Type) column in the iCap reports.

Relative priority of an LPAR or capacity group

Possible values are 1 through 5.

iCap uses this parameter to determine recipient and donor LPARs when LPARs and capacity groups compete for MSUs.

Proportion of the MSU limit to which an LPAR or capacity group is entitled

iCap uses proportion to calculate the number of MSUs to which an LPAR or capacity group is entitled when the combined 4HRA of all LPARs and groups is approaching the MSU limit.

The simplest way to calculate proportion is as a percentage of 100. For example, assume that three LPARs are running on the system. Proportion is specified as follows:

• LPARAAA = 30
• LPARBBB = 50
• LPARCCC = 20
• Total = 100

You can also calculate proportion as a percentage of MSU Limit, or you can use LPAR weights.

The iCap reports from Cost Management also calculate a value for proportion that is 0.1% of Peak MSU. For more information, see iCap-report-parameter-descriptions.

For more information about how entitlement is calculated, see Overview-of-entitlement.

The maximum DC or GCL that an LPAR or group is allowed at any time

An LPAR or group will never receive DCs or GCL above this limit. That is, if the LPAR or group requires MSUs above Max DC/GCL, iCap cannot assign additional MSUs even if the MSUs are available. Therefore, the LPAR or group might be capped even though MSU usage for the policy is below MSU limit.

You might want to use this parameter in the following circumstances:

• A test LPAR is being used by an application group that has a tendency to write loops.
• An LPAR is running software that must be limited to a specific number of MSUs for contractual purposes.
• You want to limit the cost of a particular subsystem that runs on an LPAR, and ensure that the DC never goes over MAXDCGCL. Therefore, you can use this parameter to make the MSU costs for that LPAR more predictable.

Relative cost of the LPAR or group

The MSU cost for each LPAR or group contributes to the cost limit for the iCap policy. If you specified YES for Manage Cost, you must specify a value for this parameter.

This value can represent the actual cost of one MSU on an LPAR or group, or you can specify a relative value:

• If you know the exact cost of one MSU on an LPAR, you can specify the value in any currency (such as dollars, pounds, or euros).

  Warning

  Example

  On LPAR A one MSU costs $752, so MSU cost is 752.

• If you do not know the exact cost of one MSU on an LPAR, you can specify a relative value.

  Warning

  Example

  The cost of an MSU on LPAR A is double the cost of an MSU on LPAR B, and the cost on LPAR C is half the cost of an MSU on LPAR A. Specify as follows:

  • LPAR A: MSU Cost = 2
  • LPAR B: MSU Cost = 4
  • LPAR C: MSU Cost = 1

You can determine MSU cost for an LPAR or group in one of the following ways:

• Access the iCap report from Cost Analyzer. For more information, see iCap-report-parameter-descriptions.
• Use the SCRT report and the IBM MLC bill for an LPAR or group.
• Calculate a value based on your knowledge of the software running on the LPAR.

Whether the LPAR is a container LPAR

Specify YES when the LPAR is a container LPAR and you want to enable iCap to adjust the MSULIMIT of a policy based on the discount from container workload transaction reductions.

Name of the subpolicy to which you want to add the LPAR

Leaving this field blank adds the LPAR only to the main policy.