A complex can get out of compliance with the Instant Capacity
contract if any of the following occurs:
More cells
are active than expected (not enough inactive cells)
More memory is active than
expected (not enough inactive memory)
More processors are active
than expected (not enough inactive processors)
There is a negative temporary
capacity balance
 |
 |  |
 |
 | NOTE: Your system may be out of compliance due to having different
Instant Capacity software products installed. For example, if a
partition has the old product B9073AA installed
(Instant Capacity versions B.03.x through B.05.x) and another partition
in the same system has the new product B9073BA installed
(Instant Capacity version B.06.00 or greater), the B9073BA software
assumes that all components in partitions that have B9073AA installed
are active. See “Upgrading
to Instant Capacity versions B.06.x or B.07.x Software” for
details of correcting this non-compliant state. |
 |
 |  |
 |
The Instant Capacity software sends an exception report (via
e-mail) if one of the above exception conditions occurs. Exception
information is also written to the system log file. In some cases,
licensing compliance is enforced by deactivating processors at boot
time. See also “Temporary
Instant Capacity Expiration and License Enforcement” and virtual
partition “Boot
Time Compliance” for
more details about license enforcement.
The following page contains an example of the e-mail exception
report for having more processors active than expected:
Example 7-1 Exception
Report for More Processors Active than Expected
To: root@par1.yourorg.com
Subject: iCOD Exception Report
This message is being sent to inform you that your iCOD system (containing the
partition, par1) is in an exception state based on the following detected
exceptions:
More processors active than expected
This system is out of compliance with the iCOD contract. The listed exceptions
must be corrected as soon as possible.
'More processors active than expected' means that one or more unlicensed iCOD
CPUs have been detected to be in use. For details of CPU usage, use the
icod_stat command. This exception state may be corrected by deactivating CPUs
until the number of inactive CPUs matches the expected number of iCOD CPUs
reported by icod_stat. Alternately, the CPUs can be purchased for permanent
activation or temporary capacity (TiCOD) can be purchased and applied to the
system.
NOTE: When a system is in an exception state, many system management operations
are likely to fail. These include, but are not limited to: the ability to
activate processors, the ability to manage hard partitions (nPars), the
ability to manage virtual partitions (vPars).
NOTE: One or more of the exceptions listed in this mail may be due to assumptions
made because of an inability to get complete information (see icod_stat
output for details).
In some cases, exception states arise when partitions are not shut down
properly, or have been loaded without iCOD software. To eliminate these
possibilities, do the following:
1) always use the "shutdown" command when shutting down a partition.
2) boot any partitions that may have been shutdown improperly.
3) ensure that all cells in the system are powered on.
4) ensure that iCOD software is properly loaded and configured on all
partitions.
NOTE: An exception related to cells, memory, or processors may occur if a cell
containing iCOD components is removed from the system (e.g. for repairs or
upgrades). Because iCOD RTU licenses can float between components, it is
important, when removing a cell from the system, to be careful to not
remove iCOD components with the cell.
See the iCOD User's Guide at /usr/share/doc/icodUserGuide.pdf for more
information.
As mentioned above, you can also get an exception report for
other exception conditions. Here are the other conditions and examples
of the appropriate exception report content:
Example 7-2 Content
of Exception Report for More Cells Active than Expected
More cells active than expected
'More cells active than expected' means that one or more unlicensed iCOD
cells have been detected to be in use. To find out how many inactive cells
are expected on the system, run icod_stat and look at the expected number
of iCOD cells. This exception may be corrected by using parmodify to set
the use_on_next_boot flag for an assigned cell to "n", followed by a
partition reboot. Alternately, cells may be turned off after a partition
reboot, unassigned from partitions, or purchased for permanent activation.
Example 7-3 Content
of Exception Report for More Memory Active than Expected
More memory active than expected
'More memory active than expected' means that unlicensed iCOD memory has
been detected to be in use in the system. To find out how much inactive
memory is expected on the system, run icod_stat and look at the expected
amount of iCOD memory. Typically, this exception occurs when an iCOD cell
is activated, but it may also occur when a cell with a small amount of memory
is deactivated and replaced with an iCOD cell with a greater amount of memory.
To correct this exception, one or more cells will have to be deactivated in
order to deactivate the appropriate amount of memory. This can be done by
using parmodify to set the use_on_next_boot flag for an assigned cell to "n",
followed by a partition reboot. Alternately, cells may be turned off after a
partition reboot, unassigned from partitions, or the appropriate amount of
iCOD memory may be purchased for permanent activation.
Example 7-4 Content
of Exception Report for Negative Temporary Capacity Balance
Negative temporary capacity balance
'Negative temporary capacity balance' means that the temporary capacity
(TiCOD) balance on the system is negative. To correct this exception, first
correct any 'More processors active than expected' exception so that the
temporary capacity balance does not continue to grow more negative. Then,
purchase additional temporary capacity and apply the temporary capacity
codeword to the system. Alternately, the processors consuming temporary
capacity can be purchased and the Right-to-Use licenses applied to the system.