Frequently Asked Questions
Instant Capacity Software
How does Instant Capacity interact/coexist with partitions running software other than
Instant Capacity is only supported on
| What | ||
| The following table lists the | ||
| Instant Capacity software: |
| |
Table |
| ||
|
|
|
|
| Triggered By |
|
|
|
|
|
|
| icod_modify (if a |
| Information about the configuration change |
| configuration change occurs) |
| is sent to the |
|
|
| and change notification is set to “on”. |
|
|
|
|
| icodd (daily, when the |
| A temporary capacity expiration notification |
| projected TiCAP balance |
| is sent to the |
| expiration is less than the |
| and root. |
| warning period: by default, |
|
|
| when less than 15 days) |
|
|
|
|
|
|
| icodd (daily, if more than |
| An exception report (for |
| expected processors, |
| sent to the |
| memory, cells, are active — |
| root. |
| also if TiCAP has a negative |
|
|
| balance) |
|
|
|
|
|
|
| icodd (if one or more |
| A temporary capacity enforcement message |
| processors is deactivated at |
| is sent to the |
| boot time to enforce |
| and root. |
| compliance) |
|
|
|
|
|
|
| vPars startup (when the |
| Information about why the virtual partition |
| virtual partition has more |
| is not being allowed to boot is sent to the |
| processors assigned to it |
| |
| than are licensed) |
|
|
|
|
|
|
Chapter 8 | 117 |
