IBM PVU License Consumption Report
- When this check box is clear, so that ILMT is the source of truth, the report shows the data most recently imported from ILMT. For this reason, you cannot set a date range in this mode, since the data is always the most recently available.
- When this check box is set, so that FlexNet Manager Suite is the source of truth in "PVU mode", the report displays the results calculated during the most recent full inventory import and license reconciliation (normally calculated overnight), and includes retrospective data covering the entire reporting period that you choose. The default start date for the reporting period is controlled by , and the period defaults to 90 days long. You may need to fine tune the start or end dates, for example to start the day after your last archived report, or to finish on the last day of a month.
Generating the report
- Navigate to .
- In "PVU mode", when FlexNet Manager Suite is the source of truth for PVU sub-capacity calculations, use the two date pickers labeled Reporting period (in the top left corner) to adjust the reporting period.
- The report controls include a search field labeled
Licenses, which for audit reporting defaults to
All IBM PVU licenses. For special purposes,
to narrow your report to one or several candidate licenses:
- Click the edit icon in the field to open a search panel.
- Type all or part of a license name in the License search field, and click Search. Results display in the list at the bottom of the panel (across multiple pages, if your search returned a large number of licenses).
- Select the check box to the left of the license (or licenses) to include in the report. Your current selection(s) are displayed in the Selected license box, and also in the Licenses text box.
- Close the search panel. for example by again clicking the Licenses field.
- Click Run report.
Reading the report
The following columns are available. By default, all available columns are displayed in the report (although for special purposes, you may move any columns that you do not want included into the column chooser).
- License
- Region
- Host
- Inventory device
- Application.
Column name | Description |
---|---|
Application properties | |
Application name |
The application's name, which may be:
|
Primary |
Describes whether this product is primary for this license. The default value of this field is Yes for a single-product license. In case of licensing product bundles, you can select one or more primary product(s) for this license. When the application displays No in this column, the installation does not consume any points, as its licensing is covered by the primary product(s) on the same license. |
Host properties | |
Computer type |
Specifies the type of the inventory device, which may be any of the
following values:
Most commonly, this displays VM Host. However, if it happens that a stand-alone device (neither a VM nor a VM host) is included in the report for its full capacity contribution, its details are repeated in both the host section and the inventory device section of the report. In this case, the Computer type typically displays Computer. |
Host consumption |
The total points consumed for all of the relevant software
installations on this host (both on its hosted VMs and directly on this server). The
simple sum of points for all installations may be modified in either of two ways:
|
Host licensing |
Displays one of the following values:
A host may be forced to consume to its full capacity for either
of the following reasons:
|
Host manufacturer |
The company making and selling the computer hosting the relevant virtual machine. |
Host model |
The manufacturer’s model name or number for this device. |
Host name |
The system name of this device. You may click the hyperlinked name to open the inventory device properties for this host. |
Max clock speed |
The maximum clock speed displayed in the computer’s own property sheet. The Clock speed value is not directly editable. See the property sheet for the computer. |
Physical server CPU core sub-capacity |
The number of processor cores used in the consumption calculation
for this row of the report.
Tip: When Host licensing is
Full capacity or blank, this figure is the same as
Physical server CPU core sub-capacity limit. In contrast, when
Host licensing is Sub-capacity, this
figure is the same as the Cores count displayed for the inventory
device (guest VM) in this row.
|
Physical server CPU core sub-capacity limit |
The total number of processor cores available in the host, which acts as a cap or upper limit on the sum of possible cores assigned to its guest VMs. |
Physical server PVU sub-capacity |
The PVU points consumption for the current row. This is the result of multiplying together the Physical server CPU core sub-capacity value and the PVU per core value. |
Physical server PVU sub-capacity limit | The maximum number of PVU points available for this server. This is the result of multiplying together the Physical server CPU core sub-capacity limit value and the PVU per core value. This figure acts as a cap for the total consumption of points on this host. |
Processors |
The total number of central processing units (CPUs) available in this host. |
Processor type |
The type of processor installed in this host. Processor type influences the selection of points from the points table linked to the IBM PVU license. |
PVU per core |
The value chosen from the PVU points table for use on this host server. The choice is based on the host manufacturer and model, along with processor type. |
Inventory device properties | |
Allocated |
Indicates whether this row of the table records an allocation of the license to the inventory device or user. (Allocations are independent of installations.) The Allocated value is editable in the Consumption tab of the license properties. Furthermore, the type of allocation can be adjusted on the Licenses tab of the inventory device properties. |
Computer |
The name of the device consuming from this IBM PVU license. Click to open the properties of this inventory device. Editable in the Name field on the General tab of the inventory device properties (for manually-created records). |
Computer deleted |
Displays No when this virtual machine is still fully operational and reporting inventory. Displays Yes when an operator has attempted to delete the record for this device — strictly speaking, the device has been given a status of Archived, and its historical records are maintained for retroactive consumption calculations. In all other respects, it acts as if deleted. (Its complete deletion follows when the historical records of consumption are no longer required, because they fall outside the data retention period.) |
Cores |
When the inventory device is a guest VM on the host in this row, this is the number of processor cores assigned to the VM. If the Host licensing column displays Sub-capacity, this count of assigned cores matches the Physical server CPU core sub-capacity value used to calculate the points consumed for this row. However, where the Host licensing was forced to Full capacity, those two values are different, with this column still showing the cores assigned, even though that number had to be ignored for full capacity calculations. (In those cases where this row is reporting consumption for the host itself, or for a stand-alone server, this is the number of processor cores available in the physical inventory device.) |
Domain name |
The domain for this inventory device reported in its inventory. Often blank for guest VMs hosted on UNIX-like servers, unless the configuration has been especially set up to report a Windows domain for the non-Windows device. Information only, and does not affect device matching or consumption calculations, nor the attribution of device consumption to an IBM region (which is handled through locations). |
Eligible for sub-capacity |
Displays Yes when all of the
following are true:
Tip: Check this value against the results for
other VMs on this host, and also against the Host
licensing column. Even though this
individual VM may qualify for sub-capacity calculations, the
presence of any one or more VMs that are ineligible (for
example, because they are not reporting FlexNet inventory)
forces calculations for the entire host and all its VMs to
be Full capacity.
Inconsistencies in this value for VMs on a common host can
help you diagnose where you are missing installations of
FlexNet inventory agent.
|
Exempted |
Displays Yes when an Exemption reason is set, meaning that the use of the licensed application on this inventory device does not count towards points consumed for the license. Displays No in the normal case, where the points consumed by the inventory device are calculated, and used in deriving the peak consumption for the appropriate IBM region. |
Exemption reason |
The reason why the individual computer or user is exempt from consuming an entitlement under this license, even though the application is in use. When this column is blank, application use on this computer, or by this user, can count towards consumption of the license. The Exemption reason may be set on the Consumption tab of the license properties; or it may be based on the setting of the device role which matches an exemption reason identified in the product use rights of the license. |
Inventory source |
The most recent source of inventory that reported the majority of the hardware properties for this device (if a device is reported by multiple inventory sources, some details may come from the main or primary source, and other details may be augmented from other sources). When FlexNet Manager Suite is the source of truth for sub-capacity PVU calculations, this column should always represent FlexNet inventory, collected and uploaded by the locally-installed FlexNet inventory agent. (The column may also display ManageSoft, a legacy name for FlexNet inventory agent.) |
IP address |
The IPv4 address (if any) reported in inventory from this device. Reflects the IP address shown in the General tab of the inventory device properties, and may be blank if the device reports an IPv6 address as its first or only IP address. |
Last inventory date |
The date when inventory information was most recently collected by the Inventory source for the inventory device. |
Operating system |
The operating system that this inventory device reports in inventory. In the case of a virtual machine, this is the guest operating system. |
License properties | |
License consumption |
The total number of points consumed for this IBM PVU
license, which is the sum of:
|
License name |
The license name may be:
|
License publisher |
The name of the software publisher (responsible for its development and distribution), as shown in the license properties. |
License version |
The version assigned to the license. This may be tracking versions of a linked application, or may an independent value. |
Region properties | |
Region consumption |
The peak consumption (the highest number of points consumed on an individual day) for the IBM region identified in this row, being the region to which consumption by the host server contributes. |
Region name |
Shows, for each device, the region in which its PVU points are included (or,
if the device is not yet assigned to a region, Unknown region
is displayed, and this should be corrected as soon as practical). This is one of the three
regions of the world that IBM makes mandatory for reporting points consumption on IBM PVU
licenses.
Tip: In any list of inventory devices, a
virtual machine shows the IBM region linked to
its host server. This is because an IBM PVU license licenses the host, and
therefore the total consumption for the host is rolled up into the IBM region that
is linked to the host (through its owning location). This total consumption of PVU points
includes both software installed on the host and/or on any guest VMs running on that host.
(In contrast, if the host for the VM is unknown, the VM displays its own properties, so
that in this case, the location and its mapped IBM region are those from the orphan
VM.)
Values may be:
|
Region peak consumption time |
The date (within your chosen reporting period) when the peak
value for the named region first occurred. Since calculations
for each reporting period are independent (that is, do not carry
over any peak values from the preceding period), this may well
be the first day of the reporting period.
Tip: To
synchronize reporting for the three regions worldwide, dates
are UTC (that is, the date rolls over at midnight
UTC).
|