z/OS MVS Product Management
z/OS MVS Product Management
Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Analysis of the software usage report generated by Example 5 without a BatchPipes exit z/OS MVS Product Management SA23-1391-00 |
|
The only aspect of this specific report that will be discussed concerns the fact that BatchPipes® was not reported in the “Billing” section even though the customer supplied a valid PRODNAME control statement and BatchPipes data was processed by the usage report program. BatchPipes differs from the other IBM® measured usage products in several ways. Rather than measuring and reporting its usage in millions of CPU service units (MSUs), BatchPipes measures and reports its usage in ‘GigaBytes read’ as a better indication of BatchPipes usage. As a consequence, BatchPipes requires that a BatchPipes-specific vendor exit be installed and invoked by the usage report program. This BatchPipes exit modifies several registration fields of the BatchPipes usage section of the SMF type 89 record and provides directions to the usage report program for calculating and reporting BatchPipes usage. The exit also provides the definition of BatchPipes usage that will be placed in the “Note” section at the end of the report. Because these notes are assigned alphabetically by product name, BatchPipes was assigned note number (01). The other IBM measured usage products appearing on the report will continue to share the usage definition for MSUs, that will be assigned note number (02). Because BatchPipes required a vendor exit, but the customer did not install one in this example, the appropriate registration fields in the usage data were not properly modified, and the usage report program reported the BatchPipes data as some other product for which no START had been issued. As a result, this data appears in the “Collection” section with the product name BATCHPIPES/MVS but with unusual values for the version and function fields. However, based on special fields in the SMF type 89 records, the usage report program was able to determine that this usage data did require an IBM product exit that minimally was required to provide directions for the calculation and reporting of the data. Because no exit was provided, the usage report program printed XXXX for this product's usage values and used note (01) to describe the error condition encountered for the product. Other IBM products that also require product-specific vendor exits cause the usage report program to react in much the same way when those product-specific exits are not installed or not accessible during the execution of IFAURP. The general result is that the usage report program seems to ignore the START keyword for the product, that then appears in the “Collection” section of the report, usually with unusual version and function values. Note, however, that the usage report program can not always determine that a product-specific vendor exit is required and thus will not always print XXXXs in place of the product's usage values nor print a specific exit-related error message for a product that is missing its required product-specific vendor exit. If the customer were to install the proper BatchPipes vendor exit as documented in the BatchPipes' PTF cover letter and rerun the usage report program, the following Software Usage Report would be generated. Figure 1. Software usage report generated for Example 5 with a BatchPipes exit installed
|
 Copyright IBM Corporation 1990, 2014 |
