| A IFAURP program level |
The version.release.modification level of program IFAURP.
Several error messages reference the IFAURP level. |
| B Execution date |
The date that IFAURP was run to produce this report. |
| C Customer information |
The customer name, number, and address, obtained from the control
statements. |
| D Software vendor information |
The product owner, obtained from the SMF type 89 record, and
the name and address of the software vendor, obtained from the control
statements. |
| E Processor |
Identification of the processor. Product registrations will
be reported on a processor basis. For all other processors, the heading
shows "Standalone" with the following values: - Type-Serial: the type and serial number of the processor.
- Model: The model number of the processor or cluster. A model value
of ???????????????? indicates that IFAURP does not
recognize a specified processor model. Unrecognized processors are
always listed on reports as if they are standalone, even if they
are 9672 servers. You can use a report listing unrecognized processors
for collection purposes but not for billing purposes. You must correctly
identify all processors on reports that you submit to IBM® for billing.
- Category:
-
- “Machine”
- 9672 Enterprise Server. This category represents IBM asset information associated with 9672-Rxx
model processors.
- “9672 CEC”
- 9672 CEC within a Parallel Transaction Server or Enterprise Server
- “Standalone”
- All other processors
- Type-Serial
- The type and serial of the processor or cluster.
- Model
- The model number of the processor or cluster. A model value of
???????????????? indicates that IFAURP does not recognize a specified
processor model. Unrecognized processors will always be listed on
reports as if they are standalone, even if they are 9672 servers.
You can use a report listing unrecognized processors for collection
purposes, but not for billing purposes. You must correctly identify
all processors on reports you submit to IBM for
billing.
- Begin-End Dates
- The first and last dates for which product registration data is
reported, obtained from the SYSHIN input file(s) or the history file.
|
| F Product information |
The product name, feature name (if any), product version.release.modification
level, and product identifier obtained from the SMF type 89 subtype
1 and subtype 2 records. Some of the SMF type 89 subtype 1 fields
are modified by IBM product-specific
exits before they are formally processed by IFAURP. The TYP
field indicates the licensing status of the product or feature. The
product or feature provides this information during its registration:
- P
- The software license applies to the product name.
- F
- The software license applies to the product name/feature name
combination.
|
| G Maximum Concurrent Product Registrations |
A column, one for each of the thirteen months or less
ending with the latest end date, that lists the maximum number of
concurrent uses of each product or feature for the month, as measured
by the number of concurrent product or feature registrations. The
products are listed in ascending order by product name, feature name,
and version.release.modification level. When multiple product numbers
or levels of the product or feature are reported for the same month,
the values for each are listed on a separate line, starting with the
values for the product's highest level. For multiple LPARs the value
listed is for the hour at which the combined LPAR use values is the
maximum. Note: When multiple MVS™ LPARs
are measured, the report might overstate the maximum use value; the
value listed represents the combined use values that occurred over
a particular hour rather than at any single instant in time within
that hour.
Special usage values are printed as follows:
- 0
- This particular version (vv.rr.mm) of the product or feature is
no longer in use.
- -
- There is no usage to report.
- N/A
- Use counts are not available; the product information comes from
SMF 89 subtype 1 records. Subtype 1 records collect measured usage
statistics rather than use counts. The measured usage products are
listed on this report so that you have a convenient place to track
the use of all products.
- ????
- The use count exceeds 9999
The following symbol can follow a use value:
- #
- The data is for less than a complete month, either because it
is for the first month in which a product or feature was reported
or because it is the latest month reported and presumed to be incomplete.
|
| H Max MVS/ESA LPARS |
The total number of processors and LPARS for which SMF type
89 records were received in a month. A processor in single-image
mode is represented by an LPAR value of 1. |
| I Percent missing hours |
For each month, the hours for which no SMF type 89 records
were received, shown as a percentage of the total number of hours.
A blank in this field indicates that no hours are missing. This value
(described in I ) is calculated as follows,
where total hours is the total number of hours for
all LPARS producing SMF type 89 records: (total hours) X 100
24 X no. days in mo. X MVS LPARs
The preceding
calculation is different for the very first two months the
START keyword is used on a processor. Note: Initial collection periods
beginning prior to December 1, 1998, were only one month in duration.
The
total number of hours in the month is calculated based on the earliest
START date, rather than the first day of the month. Note: The last
month on the report for which usage is printed is typically an incomplete
month (followed by a #) and usually indicates a relatively large outage
value.
|
| J * Product or feature begin date |
The earliest date for which product use data was collected.
This date appears on the report only while the data in the report
reflects product or feature use on that date. For example, if the
product or feature begin date is 06/01/96, “* 01Jun96” appears for
the entire year. Once there is data in the report for June, 1997,
this date is dropped from the report. |
| K (Note number) |
The number of a note in the Notes® section L that
describes any exceptional conditions encountered with the SMF type
89 records. The same note number might be associated with more than
one product on the same report. Note numbers are dynamically
assigned on a report by report basis. The note number used to describe
a product's units on one processor's report might describe an error
condition experienced by a different product on another processor's
report.
|
| L Notes |
This section describes the meaning attributed to: - each special symbol: “*”, “#” and “N/A”
- numbered notes for specific products
- unnumbered notes, which are not product-specific
Error messages appearing on this report also appear on the
IFAURP Messages Report, which might include additional diagnostic
information.
Notes appear
on only the LAST page of multipage usage reports.
|
z/OS MVS Product Management
Copyright IBM Corporation 1990, 2014