zAAPs are configured via the normal PR/SM™ logical
partition image profile. There are some requirements regarding zAAPs
and standard CPs. The following requirements are associated with
zAAPs:
- The number of zAAPs must not exceed the number of standard CPs
for a server.
- You must have at least one standard CP defined for a partition.
The z/OS® system needs at least
one standard CP online at all times.
- You have the ability to set the number of zAAPs for an LPAR, although
you cannot specify a weight or if the zAAPs are dedicated or shared.
The zAAPs inherit the dedicated or shared attribute from the standard
CPs in that LPAR.
- There is hard capping for zAAPs, but there is no support for soft
capping (which is the WLM support for 4-hour rolling average). The
existing single set of PR/SM logical
partition processor weights (INITIAL, MIN, MAX) are applied independently
to the shared standard CPs - capping only applies to shared standard
CPs configured to the logical partition. If you use WLM weight management
for the LPAR with SCRT, then z/OS WLM
will manage shared standard CPs as today, but not the zAAPs.
- zAAPs will not participate in Intelligent Resource Director. The
zAAPs will not participate in dynamic share management or in the
number of logical zAAPs online.
Note that zAAPs are brought online and offline like standard CPs.
To define the zAAPs to your logical partitions, see PR/SM
Planning Guide.