After the temporary capacity is depleted, and
you continue to have more active cores than usage rights across the
complex, a notice appears at the bottom of the icapstatus output similar to the following:
WARNING: Temporary capacity has expired and this complex is out
of compliance with the Instant Capacity contract because there
are 2 more active cores than there are core usage rights.
Deactivation of cores may occur during partition reboot to
bring the complex into compliance. In order to avoid the
deactivation of cores upon reboot, you need to take corrective
action immediately. Either deactivate 2 core(s), apply
additional temporary capacity codewords, or purchase and apply
Right to Use codewords for 2 core(s). |
 |
As stated in the warning, if cores without usage
rights continue to be used, then on the next reboot of any partition
in the complex, the software will automatically deactivate one or
more cores in order to bring the system into a state closer to compliance.
The Instant Capacity software will deactivate as many cores as is
necessary to either stop consumption of temporary capacity or to bring
the partition to the minimum number of required active cores. You
must purchase additional temporary capacity or purchase the appropriate
number of usage rights (RTU codewords) to be in full compliance.
See “Temporary Instant Capacity Exceptions” for examples of the error messages
that are sent as a result of compliance enforcement.
Auditing of temporary capacity is done at the
complex (OpenVMS node) level on Instant Capacity systems that support
partitioning (and are not part of a GiCAP group). While temporary
capacity may have been purchased for use by a specific partition,
it is available to all partitions in the complex or OpenVMS node (or
to the entire GiCAP group, if applicable).
Purchasing the appropriate RTU product that provides
additional core usage rights for the system and applying the associated
RTU codeword clears out any previous violation of Temporary Instant
Capacity.