Enable the injection of IBM i License Keys from a PowerVC repository. The Repository should know M/T & S/N and IBM i Version to be able to inject correct keys.

1) IBM has (unfortunately) moved to term-based licensing for IBM i.
2) When additional cores, or BR2, or (future product) core licenses are ordered, keys only are good until the EARLIEST expiry date. (e.g. Order 2 cores on 1/Jan and 2 cores on 1/July.  The keys you get on 1/July expire on 1/Jan. When those are renewed, they will expire 1/July. Now orders some in May and some in August and you got yourself a mess.)
3) Now understand that also IBM i Users expire as well and there are minimum 3 keys that must be updated at every renewal.
Example: We have one Power10 with 39 LPARs, and SIX different expiry dates. That means signing on to 39 LPARs, 6 times a year and pasting in 3 License keys to every one of them. 
They are NOT all on the same network and are not all reachable via IP, so: HMC Console!

Since the HMC has the ability to inject keys into LPARs then PowerVC should adopt a way to store the keys for injection to the LPARs at build time and whenever keys need updating, automatically.  

================================================================================
ADDITIONALLY IMPORTANT!

PowerVC needs to understand FLASH COPY and REMOTE COPY.  So an LPAR on Machine A is remotely replicated to Machine B and Flash Copied there as well. PowerVC needs ALSO to inject keys to the running LPAR on Machine A such that remote copies and Flash Copies will have the needed keys when those target LPARs are fired up!!