Enable Virtual Serial Number (VSN) for Shared Processor Pool (SPP)

As currently defined, a Virtual Serial Number (VSN) can only be used once for a single LPAR, with cores fully assigned. This approach significantly limits flexibility.

For example, consider a scenario with three LPARs, each assigned 0.4 cores. The customer owns two IBM i licenses and operates these LPARs in a Shared Processor Pool (SPP) with two cores. This setup allows them to leverage the flexibility provided by PowerVM, efficiently utilizing their two licenses.

However, if the customer wants to transition these LPARs to VSN, they would require at least three licenses—one for each LPAR. The situation worsens if an LPAR occasionally demands more than one core. In such cases, that LPAR would require two licenses. The challenge compounds with additional products licensed per core, such as BRMS or PowerHA.

Proposed Solution for Improved Flexibility

To address this, VSN could be redefined to operate at the Shared Processor Pool (SPP) level. For instance, a serial number could be assigned to an entire SPP, with some limitations to maintain manageability, such as:

1. Allowing a maximum of four LPARs per SPP.
2. Requiring all LPARs in the SPP to move together when changes occur.

This approach would enhance usability while maintaining control. Many customers have expressed interest in VSN, but its current inflexibility has prevented adoption. Implementing these changes could make VSN a more viable option for customers.