Mar 27, 2018 - 09:35 AM
This will be important for ILMT compliance back to entitlement for parallel sysplex pricing PSLC (Virtualization) and where it is a great difference in price for software products FOR ALL THE LPARS, (in some device configurations 16 LPARS VS RUNNING ON ONLY 2 LPARS), the ability to track Identification and Usage TO THE SPECIFIC LPAR would have as an advantage a CI in a CMDB which included the full identification of the mainframe location DOWN TO THE LPAR THAT THE PRODUCT ID WAS IN FACT INSTALLED AND RUNNING ON ONLY. This provides not only a backup source to your ILMT for Virtualized processing costs savings but should your bundling of products in the ILMT identification of those bundles not produce clear and “believable” results with what you believe is true to not only your entitlements but how you actually process, you’ll have this source. Add the SMF 89 records to gather the usage on said LPARS and double back up to IBM for compliance as a secondary data source. So YES, carry the LPAR identification and ensure your entitlements are a match to those LPAR’s running on the physical servers that the entitlements are said to be enabled for.From the IBM s/390 System overview document found in IBM REDBOOKS - Use the s/390 G6 System overview document as it is the last of the great 3090 architecture for large processing environments. The following information describes the method used for identifying a particular logical partition (LPAR) when the CPU's can be serialized in LPAR mode, allowing for licensing benefits for virtualization and or LPAR pricing depending upon the software product and environment. Below are the relevant sections opening lines and I have pasted the source document into the link area below.
HOPE THIS HELPS!
3.11 CPU ID CPU ID information is system-generated for each Central Processor Complex (CPC) and consists of a version code for the model number field, a CPU identification number that is unique for each logical processor, a model number for the machine type, and four hexadecimal digits of zeros. The Store CPU ID (STIDP) instruction stores the CPU ID for each logical processor in storage in the following format (Figure 3-1): Figure 3-1. CPU ID Format
The version code is associated with the number of central processors in the CPC and is not affected by the operating mode (basic or LPAR) of the CPC. For the basic modes, the CPU identification number consists of the CPU address of the central processor and digits derived from the serial number of the CPC. For LPAR mode, the CPU identification number for each logical processor consists of a one-digit logical CPU address, a one-digit logical partition identifier, and digits derived from the serial number of the CPC.
3-18 System Overview - S/390 G6 Enterprise Servers