iCap
supports only LPARs that are running on z/OS.
iCap
uses the IBM Base Control Program internal interface (BCPii) service to identify the host operating system for an LPAR. Therefore, LPARs that are not running on z/OS are excluded from
iCap
views.
For iCap to manage a z/OS LPAR, the LPAR must meet the following guidelines:
- Is not hard capped
Uses Wait Completion=NO
Note
For more information about wait completion, see the IBM Processor Resource/Systems Manager Planning Guide.
- Does not use dedicated processors
- Exists on the system
Any LPARs that do not meet the above criteria are excluded from iCap policies. (The POLOVER view lists each excluded LPAR and specifies the reason for exclusion.) iCap still monitors the excluded LPARs but will not modify their DCs.
Notes
- All managed LPARs and groups must be accessible by the same HMC.
- Each CPC requires at least one active LPAR that is running a version 3.0 master or agent PAS.
- If you want to run iCap across multiple CPCs in a CMP environment, version 2.0 agent PASs are not supported. You can run version 2.0 agents when iCap is managing only a single CPC.
BMC recommends running an active agent on every LPAR that you want iCap to manage.
iCap can function with only one active agent on every managed CPC, however, WLM importance data is not available for LPARs that are running without active agents. iCap manages LPARs that are running without active agents by priority, instead.
- BMC recommends that LPARs do not use the Absolute Capping or Absolute MSU Capping options. Using these capping options might prevent an LPAR from receiving its entitled MSUs. In addition, if one LPAR in a capacity group is using Absolute Capping or Absolute MSU Capping, the entire capacity group might be capped.