To report on registered products, you use the usage report program, IFAURP, to process all the SMF type 89 records collected for the measurement period. There is no requirement, however, to run IFAURP on the processor on which the type 89 records were collected.

Once IFAURP processes these records, you may discard them, because IFAURP saves the usage information contained on these records in a relatively small history file. Even so, IBM® recommends that the installation retain these records, perhaps on tape, for up to a year and a half to be able to process the records if necessary. A single tape/cartridge should easily accommodate all the type 89 records generated by all the MVS/ESA images in a large installation over the course of a year, when the records have a BLKSIZE of 32,760.

IFAURP has been designed to accommodate the data collected from any mix of processor configurations. A single execution of IFAURP can handle any combination of processor configurations. A “processor configuration” can be a single MVS/ESA LPAR or all the MVS/ESA images for all the processors in the installation's data center, including those processors that are a part of parallel sysplexes, whenever they all share a common IBM customer number. IFAURP can also accommodate a wide variety of processing and scheduling requirements, which are often highly installation dependent. For instance, you can run IFAURP to process SMF data sets daily, weekly, monthly, or more or less often.

IFAURP recognizes duplicate SMF records, which often occur as the result of procedural errors. IFAURP bypasses all duplicate records, regardless of whether they are recognized as duplicates during a single execution of IFAURP or across multiple executions of IFAURP. The latter case might occur when unique type 89 records are processed on one execution of IFAURP, during which the appropriate usage data is placed in the history file, followed by another execution of IFAURP with the same SMF input data set. In this case, IFAURP recognizes the records on the input data set as duplicates of the data already stored in the history file.

Running IFAURP to report on registered products is very similar to running IFAURP to report on measured usage. If you need more information about running IFAURP, see Step 3. Process type 89 records by the usage report program. Figure 2 shows sample JCL, available in SYS1.SAMPLIB member IFAUJCL.

Note: If you use the sample JCL to report on registered products, add a PARM value to the EXEC statement for IFAURP; see IFAURP parameter.