The resource entitlements for the pool are procured through your CoD licenses, which include a grace period for overuse of these resources. The resource entitlements for the pool must synchronize with the actual usage of those resources. You can temporarily overuse the Mobile CoD pool resources. However, the grace period in your licenses restricts this overuse. When resources are in use beyond the grace period, those resources are overdue and the server is out of compliance with the CoD license. Compliance policies for the Power Enterprise Pool are based on your CoD licenses and these policies enforce resource availability and usage restrictions for the pool.

The Mobile CoD resource compliance of the servers in the pool determines the compliance state of the pool itself. A server is in compliance if the server does not have any unreturned Mobile CoD resources.

When Mobile CoD resources that are removed from a server become unreturned, a grace period timer starts for the unreturned resources on that server. There is a separate grace period timer for unreturned Mobile CoD processors and for unreturned Mobile CoD memory on each server.

Before a server grace period expires, you must release the unreturned Mobile CoD resources and make them available for the server to reclaim. If a resource remains unreturned after the end of the grace period, the pool is out of compliance. When the pool moves to the out of compliance state, a new grace period timer starts for the pool itself. There is only one grace period timer for the pool. If any servers have overdue Mobile CoD resources when the pool grace period expires, add operations for Mobile CoD resources are restricted to servers with unreturned Mobile CoD resources. This restriction is enforced until there are no servers in the pool with overdue unreturned Mobile CoD resources.

When a server in a pool is out of compliance, or the pool is out of compliance, console messages are displayed on the HMC s that manage the pool.

Resolving compliance issues

To avoid compliance issues, ensure that Mobile CoD resources are released on a server before you remove the resources from that server. Also, do not remove Mobile CoD resources from a server that is not connected to the master HMC for the pool.

If you want to overuse your Mobile CoD resources when migrating partitions, ensure that all Mobile CoD resources removed from the source server are released and reclaimed by the source server as soon as the migration completes. If the migration fails, immediately remove the Mobile CoD resources added to the destination system and add them back to the source system.

If the server is not connected to the master HMC for the pool, you must establish a connection from the master HMC to that server. After you reestablish the connection, if any unreturned Mobile CoD resources remain on the server, take one of the previously stated actions to release them. If you cannot reestablish this connection, you can add Mobile CoD resources to the server to resolve the unreturned resources.